Versions Compared

Old Version 12

changes.mady.by.user Mary Jo Kochendorfer (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Mary Jo Kochendorfer (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ItemTimeLead

Review status of the roadmap and development progress.

Upcoming prioritization exercise in Dar Es Salaam, OpenLMIS Stakeholder Meeting

5 min

Mary Jo Kochendorfer (Deactivated)

Continued from last meeting...

  • Product donations
  • Facility transfers
  • Adjustment reasons

Pre-read: Mozambique stock management features.pdf

15 min

Danni Yu (Unlicensed)

Upcoming opportunities for in person meetings:

  • GHSC 2016: ideas were shared via email. Let's discuss what we think is best given the time/people.
  • Kyle: suggested discussing Budgeting within Stock Management or building a maturity matrix (maturity of existing supply chain and request for complex functionality)
  • Kevin: gathering stock management workflows or gathering personas
  • Any other people going?

Mary Jo Kochendorfer (Deactivated)

Discussion:

Documenting use stories/cases and community knowledge management across countries. What about new features and 3.0 prioritization? How does the PC want to be involved and participate?

  • New Features and Functionality (as compared to 2.0): Desire to create two orders from one requisition. For instance, health center A creates one requisition for Essential Meds. 1/3 of those products are fulfilled by a private supplier. 2/3 of the products are fulfilled by the Medical Store. Desire to have OpenLMIS create two orders, one for each. May even need separate approval processes.
  • When viewing stock on hand or conducting physical stock counts, a feature for storeroom managers to "favorite" and "unfavor" products (a sub set of the master product list. Users can create a 'custom' view for stock overview.
  • Archiving products at a facility level (not at the central level).
  • Logic and configuration around alerts for SoH.
  • Adjustment reasons and configuration.
  • Configurable requisition form headers.

Comic credit: Requirements 101


Mary Jo Kochendorfer (Deactivated)

Questions for the PC

Extension points, any comments from the example shared over the listserv?

  • Context: List of variance which we saw in designing the requisition template is in the Additional Reading section.

Defining scope for 3.0 release:

  • What are must have system management UI screens (currently found under "manage")? See the Epic for details.

Update from the TC

Technical Committee is discussing how the architecture can support the development of a new feature without forking the code. You can follow that discussion here.



Not addressed: Updating the Community road-map.



...

...