Sorry I missed this. Had a parental health emergency I had to deal with. Any special take-aways for me? Was the item on DHIS2 COVID abstract about one that had been submitted, or a recommendation for us to submit? Anyone take point on that?
Hi Andy,
This was about submitting to present about our DHIS2 Connector work at the DHIS2 conference in June. I submitted our application for this last night. Now we wait to hear if we are accepted. If we are, the presentation could be anything from a poster-style presentation to a small breakout room to a panel etc. They’ll be in touch with us.
We will share a user-friendly, improved experience for setting up data exchange between OpenMRS and DHIS2. This approach can save implementer time at set up, adapts to changing reporting indicator needs, can run automatically, and can help scale mapping work across multiple sites.
Description
In our new pandemic world, reporting requirements are likely to increase, and clear operations data is more important than ever. Digital health teams around the world face pressure to quickly generate reports for their customers. But Reporting requirements and their formulas change frequently. To meet deadlines, teams sometimes write custom scripts to facilitate custom data extraction and sharing between their EMR system and DHIS2. But these need manual fixes every time there’s a change to reporting indicators, causing painful longer-term maintenance burdens and additional quality oversight needs. Often, this work has to be manually re-done to support new sites.
We will share how Implementers can change this experience. Using an improved OpenMRS module called the “DHIS2 Connector Module”, Implementers have a toolkit to post aggregate data from OpenMRS to DHIS2. Users gain a User Interface for an easier-to-set-up OMRS to DHIS2 pipeline, that doesn’t need manual code fixes every time there’s a change to reporting indicators. We’ll show OpenMRS & DHIS2 Implementers how to use the friendly Mapping Tool User Interface, how to automatically send data to DHIS2 right away or on a schedule, and how to map their exports so that they can re-use their mapping work across sites.
In addition to the DHIS2 Conference abstract, we talked about:
Community Board Member seat will open up and the S&O Team will need to prepare to fill it.
Tension between building a robust community solution v. what is needed to meet a deadline or deliverable
COVID-19 squad health. Decision was to re-direct COVID-19 squad work to other squads where similar work is already happening (ie: reporting to Analytics Squad, FHIR resources to FHIR squad, etc) and reduce support.
This latter led to a good discussion about what it means to be a squad, how we preserve the power of the squad model, what happens we have a topic where there’s interest but no implementation to inform actual work. Emerging questions: how do we onboard implementations to squads? how do we encourage countries to adopt community solutions?
Notes fleshed out and cleaned up, so please see them for details.
