Page Comparison

 Mary Jo Kochendorfer (Deactivated) (5 min)

What will be in 3.5 (Living Product Roadmap)? 

• Reporting workstream
  • Single Sign on
  • Metrics defined (goal is to get X metrics created) <insert links to scope>
• Integrations
  • mCSD for facility information <insert line>
  • DHIS2 integration - current high-level plan, here. Detailed plan and specification is still in development.
• Features (still under discussion because many of the features still have outstanding open questions and information)
  • May have part of Splitting of products list for supply Partners completed
• Architecture
  • Improvements in integrated testing so we can release faster (reduce manual testing). We will have the pattern established and potentially integrated tests for the Requisition Service.

Update on OpenSRP mobile integration work

Brief Demo (if possible)

NFR Performance Update

NFR page: Non-Functional Requirements - performance

Requested New Feature

• Current requests: 

  Jira Legacy
  server System JIRA jqlQuery filter=20548 count true serverId 448ba138-230b-3f91-a83e-16e7db1deed1

• Potentially discuss: Non full supply product options to improve performance around requesting NFS when there is a very large list.

Suggestions on how to get input from the rest of the community on the new feature requests? Voting? Comments?

I'd like to make sure each release is including one to two new features requested by the community (if funding allows for it).

2019 Roadmap

A full list of potential features is here. I've pulled out the following four for 2019. Thoughts?

• Support for distributions and reallocating stock between facilities (user stories). The OpenLMIS community wants to enhance the local fulfillment workflows to support an end user in planning a distribution to multiple facilities at once and identify excess stock in nearby facilities. If a facility is running low on stock they will have visibility to nearby facilities. These features support a high-value supply chain workflow requested by many current and prospective country users.
• Offline support for stock management features (user stories). There is a need to integrate with third party mobile applications and support offline web browser features. Some facilities will have a desktop computer while others can leverage a tablet device. At the moment OpenLMIS supports online stock management features in the web application and integration with two mobile applications (OpenSRP and SIGLUS). Benin, Malawi, and Mozambique have all expressed the need for offline stock management features so that they can leverage the current desktop computers in facilities with intermittent connectivity. OpenLMIS would like to support both integrations with third-party mobile/tablet applications and offline features within the web application to reach the last mile.
• Collect program data alongside supply chain processes (user stories) to support user-friendly customization of data collection forms by implementers. This work allows collection of health metrics and indicators during supply chain reporting workflows. We propose to build this feature via an integration with a third-party open source application (our specifications to date focus on ODK and/or DHIS2). This featureset allows implementers to collect programmatic data alongside of supply information. The community sees a need for this in HIV and within immunization programs.
• Request, order, receive/unpack and ship “kits”, or bundles of products (user stories). Kits are common within HIV and essential medicines. This feature is a high priority for Mozambique (where implementation work is underway) and requested by other countries because bundling products together is key to supporting reordering for patient regimens and other related products.

Mary Jo reached out the community to weigh in on desired features for 2019. No specific comments from the community came in. At the moment, I've identified some key features we'd like to address are listed.

Discussion:

<insert notes>

Prior to 2019, I would like the community to weigh in further on priorities.  I welcome thoughts and ideas on the best way to do that given time/resource constraints by community members. 

Idea: if attending the GHSCS or GDHF, we could hold a listening session or prioritization meeting.

Update UI Changes for 3.5

Next PC meeting: Ideas??

???