/
PC: January 16 2018

PC: January 16 2018

Owned by Mary Jo Kochendorfer (Deactivated)
Last updated: Jan 16, 2018

Call Information

  • 09:00 PDT - Seattle
  • 12:00 EDT - New York, DC
  • 19:00 CAT - Zambia
  • 20:00 EAT - Tanzania



Last Meeting Notes: PC: January 2 2018

AGENDA

Item

Lead (Time)

Notes

Software Development Update

Mary Jo Kochendorfer (Deactivated)

The roadmap has recently been updated and will continue to be tweaked this week. The Reporting DSC indicators are especially worth reviewing.

Please feel welcome to attend the showcases or review their recordings. It would be great to receive feedback about reporting and visualizations. The two indicators we have so far are closed vial wastage and full stock availability. If folks would like other metrics (eg: stock on hand) please let us know. We have the potential to add visualizations beyond just the DISC indicators and would like to know what folks believe would be most useful.

Nuran Idris (Unlicensed) please let us know if you have suggestions on other reports we should be prioritizing using the current data model in SuperSet Reporting and Analytics#DataModel

Overall updates and topics under discussion:

  • Upcoming dates:
    • Feb (NOT CONFIRMED week of Feb 12th or 19th): demoing stock management and features supporting vaccines (CCE, F&E, local fulfillment, reporting) to GAVI, Global Fund and others to spark interest in using OpenLMIS to manage vaccines.
    • March: release 3.3 with the minimal set of features to support managing vaccines sub-nationally


Reminder about filters and navigation

OLMIS-3876 - Getting issue details... STATUS


This will have ramifications within the UI and potentially be introduced in the 3.3 release.
Please let us know if you have any questions or concerns. It would especially be helpful to hear from the Malawi team.

Remaining pieces on pull request proposals. See http://docs.openlmis.org/en/latest/contribute/contributionGuide.html#contributing-code for instructions on how to coordinate with the PC on approval of code contributions (aka new features). 

According to Ben Leibert the following are what the Malawi team plans to complete and contribute back to core as a pull request. Below is the current status of the PC review.

  • OLMIS-3793 - Getting issue details... STATUS : Has been approved as globally applicable. Needs further details on the design and AC. Brandon Bowersox-Johnson and PC provided feedback and awaits follow up from Malawi.
  • OLMIS-3794 - Getting issue details... STATUS : Unclear on approach or suggestion so no final approval yet. Unclear on if Malawi plans to still implement this given the revert button on batch. Needs input from Nuran Idris (Unlicensed) or Christine Lenihan on what the next steps are if any.
  • OLMIS-3796 - Getting issue details... STATUS : Awaiting definition from Malawi before PC can review. From a high-level it seems globally applicable and we would want it in core. From Ben Leibert "The scope is still under discussion. It’ll potentially be limited, though, and something Malawi can take on."
  • OLMIS-3702 - Getting issue details... STATUS : Approved by the PC as globally applicable. Currently in technical discussion. 

Process Improvement Needed

Question: It is difficult to know if an implementer is suggesting a new feature or rather suggesting a pull request. A proposal is to include a "label" should be added that says "PullRequest" if the implementer plans to implement the feature.  Any other thoughts?

Answer: Folks seem amenable to the above idea.


The Malawi team isn't asking the Core team to implement the first three tickets listed to the left. Instead they hope to refine the requirements internally and then with the PC. Afterward, the Malawi team will aim to implement them.

OLMIS-3702 is a little different. It involves technical nuance and may thus be nice for the Core team to address. Nevertheless, it's now a low priority for the Core as well as Malawi teams and neither currently plans to schedule it for work.

Upcoming gap analysis estimation meeting. Objective is to have an updated Roadmap for the features outlined on under the parent page → Gap Analysis: eLMIS Tanzania & Zambia and OpenLMIS 3.x



We're starting an implementation phase in which Ona and JSI development teams will be involved.

High level plans will be determined at a meeting on the 29 - 31. Ona and JSI representatives will attend it  along with subsequent PC meetings.

OpenHIE meeting on Friday
We'll be talking about product registries. 
Please let Mary Jo know if you need help signing up.

Upcoming conferences and potentially opportunities to showcase OpenLMIS or meet up.


Chris Opit (Unlicensed) is going to the ICT4D conference.

ICT4D OpenLMIS Abstract : https://docs.google.com/document/d/1zej9eXAf2bB2_XDGiLb1t1_3N-TdhMyhSPnhJlNM2pA/edit

Martin plans to offer an overview of NexLeaf at the PC meeting following the next one.

ATTENDANCE:   

RECORDING:

Video:  or URL: https://zoom.us/recording/play/FbcmUUJPkBdGk2bPCrHemMM0HzjvyTpjPyad3mJM0pWoFMraZ8e_MN0X9GFEorEC

ADDITIONAL READING:


Related content

OpenLMIS: the global initiative for powerful LMIS software