5 Apr 2018 - Phase 2 Brainstorming Session

The team is brainstorming Phase 2 of the OpenSRP integration now that the proof of concept is complete.

Attendees:

@Mary Jo Kochendorfer (Deactivated)
@Brandon Bowersox-Johnson
@Craig Appl (Unlicensed)

Agenda/Notes:

Currently funded mobile implementations for OpenLMIS
- SIGLUS Mozambique - Funded to upgrade on the server side (Craig look at this to see the feature set)
- GAP project:
  - Mobile Proof of Delivery
  - Requisition: Mid Period stock status notification
  - Facility Edition - Completely offline and could be a mobile app instead of the web application that's offline
    - Runs on a server at a large facility with departments, allowing them to perform internal issues
  - BMGF Point of Care Vaccines: OpenSRP Integration
    - Tie between the dispense and consumption
    - Inventory management
    - Stock management
    - Ordering
    - Receiving
    - Cold Chain
Housekeeping
- Contract period of performance extension status update -
- Verification of invoice receipt - Not yet received
Overview of what was delivered in the proof of concept
- Generating an order based on current stock on hand
- Order pushed to OpenLMIS where it can be fulfilled
- Once fulfilled, Nifi queries for all SHIPPED orders, performs business logic and pushes the shipment to OpenSRP
- OpenSRP Android Client is able to apply those values to the current stock control module
Feedback from Mary Jo on the GAVI demo
- How did the demo go and what were some of the gaps?
  - Audience provided positive feedback on the integration
  - Concerns about country readiness for adoption
Known Gaps in Proof of Concept that need to be addressed
- OpenSRP only tracks by commodity Type, not track orderables, trade items or lots
- The facility list information is hardcoded
- User credentials are hardcoded
- Order processing period is hardcoded
- Program information was hardcoded
- Not Scalable:
  - Nifi queries OpenSRP for all orders
  - Nifi queries OpenLMIS for all orders with status Shipped at the hardcoded facility
Defining the scope of the app in alignment with Josh's OLMIS Mobile Strategy Document
- What is the highest priority?
  - Stock Management on Tablet (Highlighted as first priority in Josh's document)
    - Include VVM status
  - Linking patient care to trade item and lot
  - Support re-supply:
    - Requesting stock
    - Receiving stock in stock management module
    - Proof of Delivery - Sending a message to OpenLMIS (I received these things with sign off)
      - Include VVM status
  - Reporting on program requirements
- What other priorities add value?
  - Cold Chain reporting
  - Open Vial Wastage - this would have to be deduced
- Regardless of the priority, we need the following:
  - Introduce the idea of orderables to OpenSRP
    - Link orderables to commodity types in OpenSRP so we can maintain the recommended number of vials used
    - Add dynamic values for dose sizes in orderables
    - Add the ability to choose whether they want orderables or Commodity Types depending on the country's implementation plan.
  - Add the ability to view ISAs on the device
How does the mobile application know if we can create a requisition or if we can create an order?
- Does the order generated need to go through an approval chain?
Define next steps and schedule for delivery
- Craig: Consolidate the online wiki documentation to a succinct list of features to tackle
  - Mary Jo will review this list and we can prioritize ("What" we want to do, not the "how")
  - Group: Evaluate "how" we will do it with the dev forum community
  - Align streams of mobile with 3.4 development and Gap analysis work
- Craig: Review Reference App list of stories (excel document on the wiki)
- Craig: Review SIGLUS
- Craig will work with Matt and Mary Jo on a no cost contract extension - End Date of June 30th 2018
- Software Requirement Specification Development time frame Needs to be defined