September 20th 2016

Call Information

8:15AM PST - Seattle
11:15AM EST - New York, DC
5:15PM CEST - CEST, Geneva, Copenhagen, Joburg
6:15PM EAT - Dar

Webex Link: https://meetings.webex.com/collabs/#/meetings/detail?uuid=M299H1X42RL8F1ABXL3LOKN9TN-3O29&rnd=371900.06805

Meeting Number: 192 173 465

Host Key: 352864

Audio Connection: +1-415-655-0001

AGENDA:

Item	Time	Lead
Review status of the roadmap and development progress. Sprint 8 Finished Shorter than normal Goals mainly on process and separation of services, RBAC, Product Model Sprint 9 (another shorter sprint) More infustructure pieces Test environment update Stitching the UI together with requisitions Continue on Requisition template Continue on Export to Order and UI. Showcase Information is located here, under Project Management	15 min	Mary Jo Kochendorfer (Deactivated)
Coordinating product committee in-person around GHSC 2016	5 min	Kevin Cussen (Deactivated)
Update on new product model. Questions?	10 min	Mary Jo Kochendorfer (Deactivated)
New opportunities and projects	5 min
TBD
Risks: Risk #7. OpenLMIS community stays dependent on centralized funding from 1-2 primary sources and fails to diversify and encompass open source development principles Risk #6. OpenLMIS community fails to grow. Stays small and driven by self-interest Risk #5. Perception of code review as an acceptance of the story. The role of code review. New risk identified by Lakshmi: Countries do not migrate to 3.0.	10 min	All

ACTION ITEMS:

@all Members: please respond to the Doodle poll on your availability to meet in person during/around the GHSC Conference in November.
Mary Jo Kochendorfer (Deactivated)to provide more details on 3.0 Beta scope during the next call
Mary Jo Kochendorfer (Deactivated) to share initial process flows and details around a few stock management stories for 3.0 during the next call. Stock management work isn't starting till later, but the hope is to start seeking input from the group.
Danni Yu (Unlicensed) to share what ESMS is doing around stock/lot mgmt during the next call
Mary Jo Kochendorfer (Deactivated) to share a presentation or demo on the new product model

ATTENDANCE:

NOTES:

Item	Time	Lead
Review status of the roadmap and development progress. Sprint 8 Finished Shorter than normal Goals mainly on process and separation of services, RBAC, Product Model Sprint 9 (another shorter sprint) More infustructure pieces Test environment update Stitching the UI together with requisitions Continue on Requisition template Continue on Export to Order and UI. Showcase Information is located here, under Project Management Ashraf Islam (Unlicensed): can you provide us with more deatils on what features will be released in the beta scope? Eventually we would also like to see release notes. Dominic Jones (Unlicensed): It would be good to add the dates of the releases in the agenda for reference. I would also like more detail on the scope for beta. Mary Jo Kochendorfer (Deactivated): will report back to the committee with more details during the next calls. Additionally I will add the dates for the releases to the call. I appreciate the suggestions. Mary Jo Kochendorfer (Deactivated): 3.0 Beta release on October 28th 3.0 release on Feb 28th Also, I created a calendar of the sprints cycles, here.	15 min	Mary Jo Kochendorfer (Deactivated)
Coordinating product committee in-person around GHSC 2016 Kevin Cussen (Deactivated) will send out a doodle (here it is) to coordinate arranging an in-person meeting. Please respond with your availability. Kyle Duarte (Unlicensed)mentioned there will be PSM team members there, Lakshmi Balachandran will be there with Gaurav Bhattacharya (Unlicensed)	5 min	Kevin Cussen (Deactivated)
Update on new product model. Please see the domain model and notes below. Ashraf Islam (Unlicensed) requested a demo and more details around the use cases. Mary Jo Kochendorfer (Deactivated)will work on pulling together a presentation to provide a more comprehensive explanation and demonstration of the impact.	10 min	Mary Jo Kochendorfer (Deactivated)
New opportunities and projects Ashraf Islam (Unlicensed) still proceeding, no contract yet - should happen. Lakshmi Balachandran Mozambique approved ESMS/OpenLMIS nationally 100 facilities Kyle Duarte (Unlicensed) indicated they are still awaiting news on Malawi's response on the budget/work plan submitted	5 min
Open Question to the Product Committee: Kevin Cussen (Deactivated) Does anyone know about Global Fund's requirements around ARV tracking? "Installing and using RxSolution in 11 hospitals and health centers in Swaziland met the Global Fund’s requirements for a reliable ARV tracking system. These facilities use the system to produce regular stock, patient, and prescribing reports for national level managers. As a result of the successful installation and use of RxSolution, the Global Fund has authorized funds for Swaziland to purchase ARVs" Link to the technical brief funded by USAID/SIAPS No one was aware of the requirements.	10 min
Risk Discussion: New risk identified by Lakshmi: Countries do not migrate to 3.0. Lakshmi Balachandran: Do we think this a risk? Kevin Cussen (Deactivated): don't think we can make a blanket statements. need to make it clear what the benefits are for 3.0 and moving over. Danni Yu (Unlicensed): interested in knowing how we can upgrade. takes a lot of coordination. Lakshmi Balachandran: if countries are on 2.0 Ashraf Islam (Unlicensed): implementors provided the support directly, and perhaps would reach out to the community Lakshmi Balachandran: do we expect future support needs on 2.0 Danni Yu (Unlicensed): didn't bring it to the community because there wasn't a process in place Mary Jo Kochendorfer (Deactivated) we will continue exploring what we think the expectations will be around support for 2.0/1.0 from the broader community. We do need to make it clear what the advantages are to migrating and clarify what the process is around support. Risk #7. OpenLMIS community stays dependent on centralized funding from 1-2 primary sources and fails to diversify and encompass open source development principles Kevin Cussen (Deactivated): mitigation strategy. OpenMRS, DHIS2, etc. Scaling the team back to 1/2 person and scaling up the volunteer community. Will bring a consultant to do an assessment to provide suggestions.	15 min	All

RECORDING

ADDITIONAL READING:

The following is a draft excerpt of the technical documentation we are working on to explain the new product model.

Modeling of medical commodities, aka Products, is central to OpenLMIS. Correctly modeling products enables administrators to:

setup forms for requisitioning and re-supply of new supplies
managing their stock in inventory
assess what their budget may support
provide full visibility into a working supply chain
enable trace-ability from production to consumption

In OpenLIMS we represent medical commodities with the OrderableProduct domain object. This represents the abstract notion of any product that may be ordered. An OrderableProduct is identified uniquely within an implementation by its Product Code. A Product Code assists people filling out paper forms as well as external systems all reference the same commodity that may be ordered. OrderableProduct's may also answer a number of questions that typically arise when one needs to order them:

how many patients may I dispense to if I order one pack of an OrderableProduct
what Programs may I order this OrderableProduct through - and what does that Program stipulate about ordering this particular product
what other commodities may also be used to fulfill the given OrderableProduct should it not be available at the store

Every OrderableProduct in the system has one of two types:

GlobalProduct - the sub-type of OrderableProduct that is used to represent a generic product that may be ordered and/or fulfilled, without indicating a specific manufacturer. An example would be a Syringe. A GlobalProduct could be setup to be ordered through the system, however many manufacturers make syringes with their own unique identity that may be used when fulfilling an order for a syringe. A GlobalProduct has a default packaging size (# of patients that may be treated within one primary pack), that is useful when placing an order, but depending upon the actual stocking of the supplying store might vary when the order is fulfilled.
TradeItem - the sub-type of OrderableProduct that represents a real branded product, from a specific manufacturer. TradeItem's are typically identified by the manufacturer or brand owner as opposed to an implementation; if GTINs are being used a TradeItem is where that identifier would be stored. A TradeItem also is specific where a GlobalProduct is generic, so a TradeItem would also be used to represent specific packaging arrangements. Where a GlobalProduct might be used in an order to indicate that most supplying stores have the GlobalProduct in bottles of 50 pills, TradeItems might be used in fulfillment at that store that will supply in bottles of 25 pills, 50 pills or 100 pills allowing specific fulfillment activities to be recorded. Additionally Batch/Lots may be associated with TradeItems and their manufacturers.

Changes from v1/v2 product model

Product is split into 2: Global Products and Trade Items. An abstract base class, OrderableProduct, ties the two together to provide a unified Product Code and UUID space.
- A Global Product is for reasoning about the product from the perspective of how it's used: 5ml Syringe, 500mg Ibuprofen Capsule.
- A Trade Item is for reasoning about the product from the perspective of who makes it, how they package it, and how they identify it: MedLine 5ml Syringes, Advil 500mg Extra Strength Capsules.
Trade Items may be associated with 0 or 1 Global Products.
1 Dispensing Unit of a Global Product must be the same as 1 dispensing unit of all the Trade Item's associated to it for purposes of ordering and fulfillment of orders.
Product Groups go away - their functionality is replaced by Global Products and Trade Items.
Lots and GTINs may only be associated with Trade Items.
Packaging is built using Trade Items, however Global Product's have a "default pack size" to help inform the person placing the order understand how many packs and the likely cost per pack they will be invoiced when the order is fulfilled.