Consortium Team
Expand |
---|
VillageReachVillageReach was established in 2000 to address the challenges of delivering quality healthcare at the last mile to the most underserved communities. In addition to focusing on a particular segment of the healthcare delivery challenge at the last mile, VillageReach’s focus is to improve the effectiveness and efficiency of the health system services that support the delivery of healthcare and services. Support from the Bill and Melinda Gates Foundation (BMGF) helped VillageReach establish a dedicated OpenLMIS Global Core (Core) team. The Core team has served as the backbone support organization for the continued development of OpenLMISv3 and the OpenLMIS Governance, Product and Technical communities. OpenLMISv3 was released February 2017, and new features have been released on a monthly and quarterly basis since then. In addition to the maintaining the core source code, the Core team’s dedicated Community Manager has helped formalize the committees and practices that guide the management and direction of OpenLMIS. JSIIn business for more than 35 years, John Snow, Inc. (JSI) is a public health management consulting and research organization dedicated to improving the health and wellbeing of individuals and communities throughout the world. With a portfolio of over 150 health supply chain projects in over 100 countries over three decades, JSI has deep experience optimizing supply chains that are more responsive to public health needs while contributing to global best practices in data visibility and use, system design, human resources for supply chain management, and commodity security. In recent years, JSI enhanced an earlier code branch of OpenLMIS for Tanzania, Zambia, Côte d’Ivoire and, most recently, Guinea ("eLMIS"). In both Tanzania and Zambia, the applications were deployed at national scale and are fully institutionalized within the health sector, exchanging data routinely with warehouse management systems in the medical stores of each country. As such, JSI’s subject matter expertise and ongoing operational engagement are crucial for bridging the existing gaps between the TZM code base and the OpenLMIS 3.x architecture. OnaOna is a Nairobi-based software and consulting company that offers technical consulting, design, and software-related services for organizations and projects of all sizes. The company’s consulting clients include WHO, UNDP, HNEC - Libya, The World Bank, UNICEF, and DFID. The Ona team has nearly a decade of experience designing, developing and implementing ICT enabled solutions for humanitarian, development and global health contexts. This includes developing one of the first national-level SMS facility-based reporting tools. When possible, the company tries to build on top of supported platforms and tools like Ona, RapidPro, DHIS2, and OpenMapKit, allowing them to build reliable, scalable solutions for lower cost. Ona follows an agile methodology to ensure projects are delivered on time and on budget. The team has extensive experience developing in Django, Clojure, Javascript, and Android. |
In-person Meetings
Pre Award: Initial Project Discussion on at JSI office in DC.
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
Recap of the meeting and key outcomes:
Meeting Agenda and Presentation: Only made it to slide 33.
|
Phase 1: Estimation Meeting on - at JSI office in DC
.Expand | ||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||
GoalsTo understand the scope, estimate and create a roadmap of the work (which includes an order based on priority), and begin to assign work to teams. We will need to get the schedule approved by the Governance committee. Once that is done, we can submit deliverables to PATH and begin the second phase of the project, feature development. We will go deeper into the specific work areas than we did during our meeting in DC. We will have attendees from each organization so we can conduct estimation activities and so we can assign initial work items to different teams. Attendees
ScheduleThe person leading the conversation is identified in BLUE.
PRESENTATION: https://docs.google.com/presentation/d/1TWIpRNIG21nTGO_sTDjRXkirFb3HlV3-HeYTPK17Ttg/edit?usp=sharing Detailed Agenda and Meeting NotesDay 1
Day 2
Reporting by Muhammad Ahmed (Unlicensed), Ashraf Presentation: https://docs.google.com/presentation/d/1ZJjvb8hoUC_k3RK06Bw0eeQz4c1yepBgFTA7hGuNufc/edit?usp=sharing
OpenLMIS Reporting Strategy
Discussion Notes:
Interfaces Unfortunately it was challenging to take notes during this conversation and it was very circular.
What we have today?
What we need to do?
Locations
Day 3
| Open Source Community | Strong transparency actions (open documentation and guidance), community engagement, mentoring developers on working in the open. | Running OpenSRP and partnering with other communities (OpenMRS, DHIS2, RapidPro, ODK), Strong code review, constructive criticism, architecture review, always-be-commiting, and knowledge sharing culture | Build tooling and developer practices | Jenkins, Trunk based development | Travis-CI, Drone, Github Flow, Git Flow | ||||||||||||||||||||||||||||||||||||||
Needs | VR | Ona | JSI | |||||||||||||||||||||||||||||||||||||||||
Java developers (Java 8, Springboot) | Java 8, Springboot 1.4+ | Java 8 | Java 8, Swing, Spring, Spring boot | Knows v3 codebase (back and front) | Back and front built most of the existing 7+ feature services | Minimal Understanding | Microservices architecture | Design, Consul and domain splitting (right sizing) | Understanding of Components | |||||||||||||||||||||||||||||||||||
RESTful API Design | Yes and evolving | Knowledgeable in API Design for other projects | Yes | |||||||||||||||||||||||||||||||||||||||||
SCRUM knowledge methods | Scrum of scrums, LeSS | Agile teams, but minimal understanding of OpenLMIS | Yes (moderate level) | |||||||||||||||||||||||||||||||||||||||||
DevOps (dockerization, AWS, Ansible, monitoring) | Basic AWS, strong on Docker, not on Ansible ours is outdated in Chef, good log centralization and search, need to get better on tracing and internal service monitoring for use | AWS, Ansible, Docker, Monitoring, Automation, Security, Terraform, Packer, Basic Kubernetes and ECS experience, RabbitMQ, MQTT | Docker, AWS, Jenkin | |||||||||||||||||||||||||||||||||||||||||
Frontend framework (Angular, React, etc.) | Angular | React, Om | Angular, vue.js | Mobile | No | Android Native, React Native, Syncing | ||||||||||||||||||||||||||||||||||||||
Reporting stack (Druid, Superset, NiFi, Kafka, HDFS, Jasper, Metabase) | Jasper, Tableu, "data pumps" | Druid, Superset, NiFi, Kafka, HDFS | Jasper, Metabase, Talend, learning about NiFI and cloud computing | |||||||||||||||||||||||||||||||||||||||||
Integrations (list out the systems which are potential for OpenLMIS to integrate with) | RapidPro, Nexleaf Coldtrace | DHIS2, RapidPro, Chatbots, OpenMRS, ODK | Integration with EPICOR, MACS, mSupply, DHIS2 | |||||||||||||||||||||||||||||||||||||||||
Domain (supply chain and logistics) Experience and knowledge of end users | Strong LMIS history | Deep Health Domain experience | Supply chain, logistics, forecasting, quantification | |||||||||||||||||||||||||||||||||||||||||
Business analysis skillset | Supply chain | Health domain, scalable solutions, defining requirements, end user design | Supply chain, user requirements, landscape analysis | UI/UX Design | Drop shadows, design workshop | Deep understanding of web service and mobile, HCI process, running design workshops | Enterprise architecture | Vision for domain boundaries and standards based teams... Interop standards of building one-offs. | Understanding of best practices in developing national health infrastructure in partnership with MOH. Robust experience in developing multiple national and global scale products. | Standards (FHIR, mCSD, GS1, OAUTH2) | mCSD, GS1, Oauth2 | CSD, HL7 v2, IHE PIX/PDQ, XForms, OAUTH | ||||||||||||||||||||||||||||||||
Database skills | Postgres, MySQL, SQL Server | PostgreSQL, MySQL, CouchDB, MongoDB, ElastiCache, Redis, InfluxDB, ActiveMQ | Oracle, MySQL, PostgreSQL, SQL Server |
Needs | VR | Ona | JSI |
---|---|---|---|
Java developers (Java 8, Springboot) | Java 8, Springboot 1.4+ | Java 8 | Java 8, Swing, Spring, Spring boot |
Knows v3 codebase (back and front) | Back and front built most of the existing 7+ feature services | Minimal Understanding | |
Microservices architecture | Design, Consul and domain splitting (right sizing) | Understanding of Components | |
RESTful API Design | Yes and evolving | Knowledgeable in API Design for other projects | Yes |
SCRUM knowledge methods | Scrum of scrums, LeSS | Agile teams, but minimal understanding of OpenLMIS | Yes (moderate level) |
DevOps (dockerization, AWS, Ansible, monitoring) | Basic AWS, strong on Docker, not on Ansible ours is outdated in Chef, good log centralization and search, need to get better on tracing and internal service monitoring for use | AWS, Ansible, Docker, Monitoring, Automation, Security, Terraform, Packer, Basic Kubernetes and ECS experience, RabbitMQ, MQTT | Docker, AWS, Jenkin |
Frontend framework (Angular, React, etc.) | Angular | React, Om | Angular, vue.js |
Mobile | No | Android Native, React Native, Syncing | |
Reporting stack (Druid, Superset, NiFi, Kafka, HDFS, Jasper, Metabase) | Jasper, Tableu, "data pumps" | Druid, Superset, NiFi, Kafka, HDFS | Jasper, Metabase, Talend, learning about NiFI and cloud computing |
Integrations (list out the systems which are potential for OpenLMIS to integrate with) | RapidPro, Nexleaf Coldtrace | DHIS2, RapidPro, Chatbots, OpenMRS, ODK | Integration with EPICOR, MACS, mSupply, DHIS2 |
Domain (supply chain and logistics) Experience and knowledge of end users | Strong LMIS history | Deep Health Domain experience | Supply chain, logistics, forecasting, quantification |
Business analysis skillset | Supply chain | Health domain, scalable solutions, defining requirements, end user design | Supply chain, user requirements, landscape analysis |
UI/UX Design | Drop shadows, design workshop | Deep understanding of web service and mobile, HCI process, running design workshops | |
Enterprise architecture | Vision for domain boundaries and standards based teams... Interop standards of building one-offs. | Understanding of best practices in developing national health infrastructure in partnership with MOH. Robust experience in developing multiple national and global scale products. | |
Standards (FHIR, mCSD, GS1, OAUTH2) | mCSD, GS1, Oauth2 | CSD, HL7 v2, IHE PIX/PDQ, XForms, OAUTH | |
Database skills | Postgres, MySQL, SQL Server | PostgreSQL, MySQL, CouchDB, MongoDB, ElastiCache, Redis, InfluxDB, ActiveMQ | Oracle, MySQL, PostgreSQL, SQL Server |
Open Source Community | Strong transparency actions (open documentation and guidance), community engagement, mentoring developers on working in the open. | Running OpenSRP and partnering with other communities (OpenMRS, DHIS2, RapidPro, ODK), Strong code review, constructive criticism, architecture review, always-be-commiting, and knowledge sharing culture | |
Build tooling and developer practices | Jenkins, Trunk based development | Travis-CI, Drone, Github Flow, Git Flow |
Team started to discuss what each team wants to work on:
- Area where we want to catch up on and learn about (micro services and whatever UI framework we move forward with, the reporting stack - DRUID)
- We bring experiences in everything else
- Desire to focus on the weaker areas (interfaces, micro services, reporting)
- Bring a lot of knowledge and experience on what was implemented in TZ and Zambia
- JSI would like to support lead on the designing and application of the reporting
- Experience on Docker and would like to share that knowledge
- Elias: not so interested in reports. Interest in React. Everything else from reports
- M: reports and analytics and cloud computing, containers, etc.
- Would like to lead on the infrastructure and devops of reporting
- Devops on microservices
- Mobile, when possible
- Interfaces (DHIS2, sms)
- Would like to avoid using Angular
- Strategic areas we’d like to learn/gain
- Transparency approach
- Governance process
- SCRUM approach
- Standards based interoperability and knowledgeable about FHIR and standards
- Can work across the full stack (strong docker experience)
- Weaker on AWS and other devops since we aren’t implementing
- Leading arch and micro services (REST, web architecture, extensibility)
- Strong transparency on everything and working in the open (continuous delivery/integration)
- Next Steps (Lead: MJ)
- Plan June or July development kick off meeting in East Africa (Kenya/Zambia/?)
- Read-out and approvals to Product Committee, PATH/DS or Governance Committee
Team Structure
Tentative team structure based on Dec. 7, 2017 meeting:
source: https://boardthing.com/board/5a2f5126b2d40b061d0c0e19
Follow up from the Estimation Meeting
Expand |
---|
ToDo:
Items which need to be discussed for the Gap Project:
Additional Conversations which are wider than the Gap Project
Team StructureTentative team structure based on Dec. 7, 2017 meeting: source: https://boardthing.com/board/5a2f5126b2d40b061d0c0e19 |
Phase 2: Development Kick off - TBD
Location: TBD
Attendees: TBD
Call Meeting Notes
Coordination Call on
Expand | ||
---|---|---|
| ||
Participants: Edward, Jake, Mary Jo, Matt Agenda 1.) Agree on funding mechanism
2.) Schedule in-person (JSI-Ona-VR+USAID/PATH) for week of GDHF week? Perhaps Thursday, Dec 7th or Friday, December 8th? For the in-person in DC (which should probably include Lindabeth, Carl and maybe Kaleb), we’d like to discuss the following:
Next Steps:
|