OpenLMIS Private Health Feature Scoping

29 Oct 2019

Attendees

Josh: What type of app or service is this?

Kim: Web-based

Feature	Comments	MVP?	Size (S/M/L/XL)
Cashier/POS			L
Integration with Payment Service	Likely integrate with an aggregator		M
On-Demand Support	Josh: Usually outsourced, dev costs pretty low.		S
Cashier Offline Support	Basic offline just store and forward, more advanced would have to deal with patient syncing between local devices		M/XL
Prescriptions/Dispensing	Would be import prescription information from an EMR but still have to map prescription to product. There are standards for this, but these will not be consistent between clinic networks in the areas we are working.	No?
Prescription Safety Check	Josh: Can be very simple to just check the expiration based on a barcode (or similar) then add more later		S
Product Availability	Wes: We already have this data, just need to search for it and display it somewhere Josh: Exclude the "Reserve" functionality for the MVP, otherwise the size is larger		S
Alternate Products	Kim: Could tie into multi-facility stock levels Mostly UI and data gathering work		M
Populated Requisitions	Lots of ways to initially populate the data. Large because we would want to		L
Dashboards			XL

Update	Comments	Size (S/M/L/XL)
Patient Information to support POS and Prescriptions	Maybe exclude MVP?
Multi-tenancy to support SaaS model	Josh: Reviewed this many times: Lowest operating to do both multi-tenant and Saas, but capital high cost Multi-single-tenant - Lots of individual instances (with tooling to support it). Higher operating cost but lower initial cost	XXL L
Significant Performance Improvements	Wes: The current performance issues are not deemed as critical because the system is not a consumer system. Moving to be a paid, private sector product will make this a much higher priority.
PCMT Integration	May already be done for the core work in 3.9-ish timeframe
UI/UX Update		L