October 6th 2020

Software Development Update

Roadmap: Living Product Roadmap 

Current sprint: Backlog Grooming Sprint 156

Upcoming sprint: Backlog Grooming Sprint 157

Version 3.10: 

• What to see what is being worked on in this release, please see: https://openlmis.atlassian.net/projects/OLMIS/versions/12817/tab/release-report-all-issues

Team stats: https://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504

Velocity: 

Open

@Wesley Brown, @Klaudia Pałkowska (Deactivated) (5 min)

Development Update:

RC1 has been created and will be shared with countries

Testers will be testing while the rest of the dev team is working on the extension points. Bug triage meetings will start early next week and be held every other day.

Change PC Meeting Schedule

@Wesley Brown (5 min)

Switch from having two calls each month to just one at the Global time

OpenLMIS COVID Edition Webinar

@Rebecca Alban (Unlicensed) (5 min)

Digital Square webinar showcasing OpenLMIS COVID Edition

COVID-19 Adaptations Follow up Webinar Part 3 featuring country deployments of OpenLMIS and OpenELIS.

Wednesday, October 28 10am EDT. Register here.

Archive Product Feature Review

@Dércio Duvane (15 min)

SIGLUS Feature discussed here: https://forum.openlmis.org/t/new-feature-review-request-archive-product/5727/3

• Moses: Interesting feature that might be useful in Cameroon. Notes say that the product must have zero stock. How do you deal with products that have multiple lots?

  • Dianna: SIGLUS doesn't manage products by lots (this is implementation change), at least not via the UI. However, all the lots must be zero, ie all of the facility product quantity must be zero

• Josh: What about products that are shared between programs?

  • Dianna: This isn't an issue in the implementation because stock is not managed (from the perspective of the user) by program. So, in practice, the quantity must be zero for that product in all programs

  • Dercio: This interacts with the Multiple Programs feature of the SIGLUS implementation so that the type of complexity is hidden

  • Josh: For other implementations, how should we deal with different quantities per program be managed?

Tanzania Budget Feature Review

@Alfred Mchau (Deactivated) (15 min)

Technical Committee Discussion: https://forum.openlmis.org/t/request-for-feedback-on-budget-feature-implementation-in-openlmis/5724/4

Questions:

• Dercio: What frequency is the allocated budget refreshed?

  • Alfred: In TZ it is quarterly

• Dercio: Is there a limitation to which facility gets the allocation?

  • Alfred: Right now it is going primarily to the MSD

Rebecca: Let's give teams a chance to review.

Distributed Lot Management

@Sebastian Brudziński (15 min)

This is a feature that the SIGLUS (PSM-Mozambique, ThoughtWorks) team has worked on as part of their implementation

In core this is currently centralized, lots cannot be added by facilities. Is this a feature that the community would like to add? If so, we will need to research exactly what is required and if/how we can incorporate the work that has already been done by the ThoughtWorks team as part of the SIGLUS implementation.

• Moses: Cameroon would be very interested in this!

• Dianna: This has been implemented in SIGLUS, perhaps this can be shared?

Product Catalogs and FHIR Standards

@Wesley Brown (if time)

Next PC meeting: Topic ideas??

1. Get feedback on the possibility of incorporating the TZ Budget and Distributed Lot Mgmt features into the ref-distro.

2. Product Catalogs and FHIR Standards

3. ? @Sachin Jagtap (Unlicensed) to give an update on GAVI/WHO work regarding COVID Vaccine Distribution (in the future)

4. ? Updates to the SIGLUS Mobile App, what are the goals for this?

Additional Requests and Information: