Agenda

Goal of the proof of concept is to show integration:
- Requesting stock
  - We need to work around the feature flow for the demo
  - Key: If you collect information on the mobile device, this is a way to save time in the requisition process.
- Notification from OpenLMIS to OpenSRP
  - In the mobile app, I'm told what shipments are coming
    - I shipped stock in OpenLMIS, then I go to OpenSRP to show that it's on the way

Implications on meeting structure:
- What needs to be delivered for the demo vs what are the long term investments
The first iteration is about the GAVI demo that's scheduled the week of 26 Mar 2018
- What are the visual items we need to demo?
  - Track ins and outs, record wastage, set VVM status, lots with expiration dates
  - Stretch: Request stock from the mobile application to OpenLMIS ← Needs better definition
Review high level document OpenSRP and OpenLMIS Integration and discuss shared understanding
Talk about scope of the demo:
- If you
Discuss project management approach
- Wiki spaces
- Team members (Ephraim Muhia, Sam Githengi)
- Sprint Schedule:
  - Line up with Other Sprints - First Sprint Date?
Craig will walk the team through design approach (Technical document OpenSRP and OpenLMIS High Level Design Spec)
- Review and take notes on discussion points in the document

For Proof of Concept:

Requesting stock:

Background information: of the stuff you need to create an order

Facility where Carla works
Carla's authority to order stock
Map between antigen OPV and orderable
- CommodityType - This is the level where we store the ISA
- ISA is defined by facility, period and program
- Keep a list of active orderables mapped to CommodityType
Ideal Stock Amount
FTAP - Facility Type Approved Product
- Or API/facilities/{id}/supportedOrderables ← Look up this
Commodity Type Backed Orderable ← Lookup this
Not related for MVP, but we need to know about trade item backed orderable
Program information
Period Information

On the device, click a button

Stretch: Do we add visuals around "requisition status" that shows what's in the workflow?

Receiving Stock:

The moment OpenLMIS ships:
- There's a notification stating that the stock has shipped
- There is information on the device about what is coming in the shipment (Proof of Delivery)
When it arrives, I can confirm that what was shipped is what is physically available
View a screen that allows you to see what is in the POD
- You will just hit "Accept" and all stock will be populated
- Question: Can we show a screen where they input the amounts that were received and confirm it?
  - Can I say the amounts that were received
- Once accepted, it would update the stock on hand

How Realtime?

When you push the "order" button in app, you have to push it to OpenLMIS
We should depend on App syncs to make this happen. We don't necessarily need a third party messaging tool
There isn't an internal trigger mechanism in OpenLMIS

Other Notes/Ideas:

Rabbits:

In Reporting, we have a closed vial wastage report
- if we're only receiving stock on hand information, the report isn't actually getting wastage information.
How much are we doing Cold Chain Equipment in this app?
- Add a visual indicator that asks the status of the cold chain equipment
- Mid month there may be breakdowns in the CCE that need to provide notifications
  - What about on device integration between nextleaf and OpenSRP

Browser not supported