Software Development Update Roadmap: Living Product Roadmap Current sprint: Backlog Grooming Sprint 106 Upcoming sprint: Backlog Grooming Sprint 107 Release: Plan for 3.5 is still under discussion Integrations (working on the mCSD for facility information, DHIS2 integration) Reporting metrics Features: still under discussion because many of the features still have outstanding open questions and information Architecture: improve demo data for performance testing, demoing and much more. Improvements in integrated testing so we can release faster
Team stats: https://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504 | (5 min) | |
Update on OpenSRP mobile integration work | @Craig Appl (Unlicensed) (5 min) | First prototype of OpenSRP mobile stock management application 6 weeks of core development Primary feature set Today looking at Android client Landing page Stock card view Receipt transaction
Landing page Provides list of all commodity types and trade items by program VVM status Ledger at the bottom Users can act on a trade item using some buttons Receive from populate automatically based on logged in user and supply line in OpenLMIS Reasons come from OpenLMIS Specify a lot based on data from OpenLMIS
Bringing in some more resources to finish work Next PC meeting will have OpenSRP and OpenLMIS servers connected so we can show the transactions across systems OpenSRP is an Android application that provides core workflows at facilities It has the ability to track child health and maternal health Prior to this integration, it had a light stock management module It will integrate with OpenLMIS system Can be run independently → can use stock management without other OpenSRP modules
|
Request: Ideas for 2019 OpenLMIS Roadmap If you would like to influence the roadmap, please follow these instructions and suggest a new feature in JIRA. You only need to create the ticket, but not email the Product Committee. | @Mary Jo Kochendorfer (Deactivated) | Working on a proposal for NSC funding for 2019 that covers new features If you have ideas about what OpenLMIS should include in its feature set in future, please write tickets We had a call yesterday to hear people verbally → please submit ideas ASAP so they can be included in SOW for proposal Proposal link: https://proposals.digitalsquare.io/85 Some features
|
Lab Management Software (OpenELIS) Discussion For places that do have lab management software, I’d presume it was donor driven. Is there still donor support? Are ministries taking over that support? For places that don’t have lab management software, and that want it, how do they start? What do they need? People, financial, institutional, software, etc
Background From Jen, "About lab equipment, I took a look at the notes. We received requests for similar functionality since it affects testing protocols and algorithms – and other features have taken priority. We should probably explore how the two systems use lab equipment data in more detail. Related to this, in 2014 and 2016, CDC CI asked us to gather requirements for and identify a system for managing lab equipment. We had a hard time finding a good fit until we came across OpenMaint. I’m happy to share the requirements drafted by the MOH and answer any questions about our experience and what we learned." | Jen Antilla (starting 30min into the meeting) | Summary of PC call where this initially came up (July 31) Dercio led a conversation around need for lab eqpt integration / feature set within OpenLMIS Asset management. 2 buckets We had some open questions about how lab eqpt systems were used in-country
Intro to Jen Antilla - works with OpenELIS (link to left) Every lab needs to go through accreditation process → having an LIS is a part of that → pushing demand for tool like OpenELIS CDC and APHL are significant players OpenELIS main focus is specimens / tests they go through and resulting process, incl validation back to physician CDC Cote D'Ivoire asked for system for managing lab eqpt → came across OpenMaint Seeing a shift toward larger RFPs looking to strengthen entire lab system, incl LIS component OpenMaint is more about asset tracking and OpenELIS is more around tests themselves Are they installed together? Usually looking for LIS first Most implementations are largely still supported by donors, relatively small scale. Kenya been going since 2014 Heavily reliant on donors for funding, dev, support Still relatively young area Different set of partners looking in it CI getting funding to support in next few weeks
OpenELIS has greenlight to write proposal to explore integration between OpenELIS and OpenLMIS for Digital Square Parambir: Want to understand commodities and assets within labs Want to understand how to support this Specific machines in labs require specific tests which require specific reagents Goes beyond typical tracking of statistics about supply chain → want to see usage of machines etc Machines and reagents are interdependent Efficiency triangulation → are they consuming the right amount fo reagents for the number and type of tests they're doing, and does consumption correlate to the services provided
Plan to do more in-depth review as Notice C goes forward
Summary of overlap/interdepence: Getting the tests done rely on Analyzers being functional and reagents being available. This dependency is where we are seeing requests either from LIS or LMIS world to track into the other space. Improve efficiency of the machines/analyzers Improve ordering of reagents and quantification Analysis of test run versus reagents used by analyzer
LIS lab service statistics LMIS can give you quantification, ordering and inventory management |