vrMIS Inception

1. vrMIS Inception

2. Understand the scope for push based replenishment system from vrMIS which is currently being run in Mozambique • Prepare a development plan for implementing the identified prioritized functionality in OpenLMIS Objective

3. Integrate the push based allocation functionalities of existing vrMIS system into OpenLMIS • Use a incremental approach to add functionality into OpenLMIS Product Goals

4. Admin Identified User Personas Field Coordinator

5. Data setup of the system : • Provinces • Health Centers • Delivery Zones • Warehouses • Products • Define/Manage ‘Ideal Stock Amount’ formula • Define ISA Exceptions • Define Rights to users • Other responsibilities (future requirements) • Define and manage new regimens to collect coverage data • Ability to custom define ISA formula based on past consumption patterns Admin Responsibilities • * Note : Admin will be the same as in OpenLMIS and will not require an Offline Mode.

6. Prepare for the trip • Determines the amount of different products to be taken. • Can view ISAs for all districts and all facilities in them. • May choose to use the ISA amounts or may request a different quantity • Visit Health Center • Records cold chain equipment's data, EPI inventory , EPI use, Fully vaccinated child data, coverage data according to regimens. • Certifies (signs) the recorded data. • Enter recorded data. Field Coordinator Responsibilities

7. Other responsibilities (future requirements) • Capture check out amounts at warehouse • Capture check in amounts at warehouse Field Coordinator Responsibilities

8. Minimum Viable Product Stories from Reports to be picked up after MVP till budget availability Feature Tree Enhancements and Future direction

9. Edit / Overwrite ISA Manage User rights Set up System data Delivery Zones and Members ,Push Programs, Define ISA formula Admin Prioritized Reports and Dashboard Elements Multi Lingual Support Record Trip Visit Details in an Offline Mode Determine Delivery Zone View Delivery Amounts Based on ISA Sync Recorded Data back to the OpenLMIS Server Phase 1 Scope Field Coordinator

10. Mapping Between VrMIS and OpenLMIS

11. Priority I • Existing functionality of vrMIS without which deployment cannot proceed • Prioritized based on discussions with Ron and Leah • Priority II • Existing functionality of vrMIS of lower business value • Functionality (other than reports) which are not actively used • Minor enhancements to existing vrMIS functionality • Priority III • New features • Nice to have features; • enhancements to make the product customizable Prioritization Criteria

12. Feature List and Priorities

13. First phase of development target: • Priority I Features + prioritized reports and dashboard elements • Later phase of development: • Priority II features and remaining reports • Priority III or enhancements to be targeted post field deployment Feature List and Priorities

14. The Initial Story List from the Inception : Initial Story List

15. WireFrames

16. WireFrames * Wireframe will be available in individual stories and consolidated in the drop box

17. Team Composition

18. Master Story List • Estimation • Prioritization • Release Plan • Wire Framing 05/27/13 Start of Iteration 1: Dev Start End of Development for vrMIS : MVP Inception for VRMIS 06/03/13 vrMIS Phase 1 Schedule 05/20/13 09/02/13 2013 2013 May Jun Jul Aug Sep

19. Available budget is not sufficient to cover functionalities such as • Pre-trip and post-trip data capture • All Reports • Implementing vrMIS specific Admin Configuration functionality in OpenLMIS will present newer technical complexity. • Offline data capture using ODK tools / Paper forms / tablets – has not been discussed and out of scope as of now • Architecture tradeoffs expected due to configurable and generic solution for multiple countries. Risks

20. Multi Lingual support for messages and labels only and not on data. • In phase 1, offline solution will be web based • Browsers to be supported: IE10+ , Firefox 12+ , Chrome 23+ • For Phase 1, only prioritized reports for vrMIS are in scope • Performance and scalability testing is out of scope • UAT, usability testing, deployment, training and data migration of existing vrMIS data is out of scope • The scope of estimated stories and functionality may change and impact velocity Assumptions

21. Retro fitting VrMIS into OpenLMIS is requires changes in existing functionality and adding technical complexity • Example • Program Type : Introduction of Push and Pull Type program • Master Template modification: Fields such as “Total” and “Expiration date” • Introduction of Product Group: Has no use in Requisition flow • ISA for Program Product • Population , Lat , Long in Geo Zones …. Issues

22. On VillageReach to Admin training, system set up and upkeep • On VillageReach for Field Coordinator training and system roll • On VillageReach for language conversion of data labels and messages to other languages and its testing Dependency

23. Provinces : • Population at a province may not be a direct summation of the health centers in the delivery zone due to the non addition of facilities which do not support vaccines program. • Internet connectivity is generally not good. • District : • A district office is visited first by the field coordinator on his trip. • Each district has multiple health centers under it. • Deliveries to district office are not to be recorded • Delivery Zones: • A delivery zone Includes multiple health centers. • Each delivery zone will be served by 1 field coordinator Appendix 1 : Notes from workshop

24. Health Centre : • Each health center is visited once in a period. • A district has approximately 40-45 health center under it. • Each health center has a catchment population recorded and updated yearly. • Each health center provides its status, stock amounts and coverage of vaccines provided • Product: • ISA values are per product- program. However this calculation will be same for products in the same group where same group implies that it is the same product in different pack sizes. • Admin gets to define default ISA calculation formulae which depends on population at a facility and WHO ratios. Appendix 2 : Notes from workshop

25. Product: • Admin gets to override ISA values at a Health facility level for products supported by that facility. This is a hard coded number overriding the default calculated value. • A product can exist in multiple pack sizes with same ISA across all pack sizes. • The ISA calculation is done based on catchment population as the demand for vaccines is usually steady and does not vary much based on consumption patterns. Appendix 3 : Notes from workshop

26. General: • Time zone is not relevant for the user • Product track able field does not need to be stored. • RDT inventory, Equipment data (other than refrigerators) & RDT use is not required to be recorded • Stock cards need not to be managed in OpenLMIS • A VRMIS user is an OpenLMIS user with a role in OpenLMIS. • The coverage rate is calculated on the basis of ideal age to administer the vaccine, which is 0-11 here. However, vaccine can also be given after 11 months if it wasn’t given previously, but it wont be used in calculating coverage rates. • Field coordinators have options to charge their mobile devices during their trip. Appendix 4 : Notes from workshop

27. Thank You