AGENDA
Item | Lead (Time) | Notes | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Software Development Update
| Brandon Bowersox-Johnson (5 min) | Software development moving forward quickly Product roadmap → main work focusing on vaccine functionality. Enhancements to stock management for vaccines, based on Copenhagen priorities, and new screens, etc., to manage CCE. Work is happening on requisition enhancements for vaccines as well. Have not yet started forecasting and estimation or resupply. Workshop in Senegal covered the resupply features. Next release: End of August, 3.2.0 - beta version of some new features like CCE screens. Implementations that upgrade to the latest version don't necessarily have to use those new features. End of year, goal is to release 3.3 that will have the entire vaccine scope completed. 3.2 is a beta version of some parts of the final release. Product roadmap → can click into boxes for further information. Click into the sprint report and see a specific list of what tickets each team completed. Coordinating on 3.2.0 release on bug fixes and additional functionality. Batch approval feature - finished by the Malawi implementation and being used there in their rollout. Further conversations have been held so the code can be refactored and pulled into the core product. Has taken collaboration and time to get there. After go-live, programmers will finish the refactoring and contribution work. Maintenance of that feature will be supported by the core team. Glad that this feature will be contributed back in. Ashraf: Question on requisitions enhancements for vaccines. Do you have any kind of UI mockup already developed? Brandon: Changes to Requisitions will be mostly invisible to the user. Change that's being done is under the hood, connecting the Requisition forms to the Stock Management service where the history of SOH values is stored. Every month when someone submits their requisition form, the SOH value from that form, will get sent over to Stock Management service so that the stock service keeps a running history of the historical number. So, if people use the Stock Management feature to use transactional or daily data entry (record adjustments, receipts, transfers, etc.) in real time, they will be able to see a history of some data for previous months' SOH numbers that came off of requisition forms. Won't change the UX for the person filling out the requisition, but will store the data in Stock Management to get a better history of stock data. Note: Here is all the background about Connecting Stock Management and Requisitions work. This is the part of the Requisition Enhancements that I was referring to. VIMS - When the facility submit their monthly report, they had vaccine usage, wastage, open vials, etc., when those reports were converted to a requisition, demographic targets and max/min were used to calculate resupply. Ashraf is interested to see how this is being handled? | ||||||||||
Senegal Design Workshop Update | Tenly Snow (Deactivated) (15 min) | Tenly: Presented Slide Deck:
Q&A:
| ||||||||||
Member updates? Upcoming travel or opportunities? | ||||||||||||
Questions on upcoming work/features: View Requisitions page enhancements:
| Sam Im (Deactivated) (10 min) | |||||||||||
Malawi Update |
ACTION ITEMS:
- Mary Jo Kochendorfer (Deactivated) to update the roadmap with a link for the requisition enhancements to clarify the scope of that work
- Sam Im (Deactivated) to send out an email soliciting inputs on the view requisition page
ATTENDANCE:
Tenly Snow (Deactivated), Brandon Bowersox-Johnson, Carl Leitner, Ashley Canchola (Unlicensed), Ashraf Islam (Unlicensed), Parambir S Gill (Unlicensed), Sam Im (Deactivated)
RECORDING:
Video: OpenLMIS Product Committee Meeting-20170801 1543-1.arf (download the WebEx video player here)
ADDITIONAL READING: