Want to join the call?
Dial Toll Free Number: - US: 800-220-9875
- Norway: 800-142-85
- Ireland: 800-625-002
- Canada: 800-221-8656
- South Africa 0-800-982-555
- International (Not Toll-free) 1-302-709-8332
- For additional toll free country numbers click here.
Access Code 69593570# **We can dial in any participants who are not able to connect through Skype or one of the above numbers, please email Angad.Dhindsa@icfi.com 24 hours in advance to be dialed in. |
Notes
Attendees:
Berny Agala (MEASURE EValuation)
Vlad Shioshvili (MEASURE Evaluation)
Dana Juthe (OGAC CIT - PwC)
Rachel Lucas (USAID)
Jacob Buehler (USAID)
Mark DeZalia (SGAC CIT)
Steven Verner (Northrop Grumman)
Annie Yu (OGAC CIT - PwC)
Jim Grace (HISP US)
Saron Worku
Saad Khan
Krissy Celentano (USAID)
Anja Buschur (USAID)
Josephine Mungurere-Baker (BAO)
Annah Ngaruro(MEASURE Evaluation)
Vilma Thomas (CDC)
James Kariuki (CDC)
Michael Mwebaze (MEASURE EValuation/JSI)
Elizabeth Meacham (I-TECH)
Jason Knueppel (CDC)
Manish Kumar (MEASURE Evaluation)
Xen Santas
Materials:
- Overview: Focus was on aggregate data on indicator data. ADX is content prfile is used to format the data from one system to another. Working with IHE were able to work through and specify what type of data is needed within the message in order for the exchange to happen between systems.
- Technical solution using ADX, recognizes that different countries and districts have specifications of what needs to be reported at a certain frequency. ADX enables the jurisdiction to take the meta data and apply the ADX to create an ADX conformant schema. Takes metadata and applies the DSD spec that validates the ADX message. This can be applied to message created by content creator. Once message is formed it can validate whether it has conformed and sent to the Content Consumer (DATIM for this case)
- Next step is to test through IHE Connectations, connection is based on the use cases that have been used. When looking at different newscases that ex. Looks at individual system into aggregate system, through this process the validators that validate the process exchange from one process to another. It is an administration where you show where one data has been created.
- Shows the data exchange between the two systems. Went through the process of the profile. What is happening is there three systems that are represented in ADX, ONEHIE shared health record (OpenMRS), OpenHIE HMIS (DHIS 2) and PROMIS system. Test conducted using sample dataset with 8 HIV indicator data elements. Tested against gazel scanatrom tester, allows you test artifacts that you are preparing for connecter testing
- Data Content Creators: Open MRS, DHIS2 and PROMIS, data content consumer, DHIS2. Initially was to test PROMIS as a consumer, but were unable to do so. Working on getting PROMIS to be a content consumer.
- Proposal to define ADX transactions for data exchange, which protocol do we use and how to specify. First to see how ADX is working given resources and what makes more sense in terms o transaction protocol.
- Further adoption and implementation: patient level to aggregate level exchange.
- Questions: What is the process of the change proposal, is outlined?
- >>As implementation of ADX begins and you encounter an issue, there is process that you can input the issues that you experience. If there is content issue within the community, you can send an email to so it can be addressed as a change proposal. During the connector, encountered two issues, will submit those change proposals, those will be shared once addressed.
- Comment: Include contacts of who is implanting:
- Question: Why not use native SDMX, is ADX on its own path of standardization?
- Answer: Did start with WHO to use SDMX to develop messages based on SDMX-HD, data exchange did not work. Came up with ADX, fit the profile of SDMX, not diverging from it but using it in this context.
- Question: Any commercial interest for IHE Connectathon.
- Answer: There was an initial interest, expected to return as project gets further. It is an ongoing questions, will see more connectathons that look for more information.
- Question: Integration of electronic medical records, what is the ADX interaction like?
- Did a field test of this a couple of years that looked at testing the effect of it and showed dramatic improvement in how much time it took to generate message and significant improvement is quality of the data. As working on how to compile this further
- Are there any metrics on data quality. Will share slides show how data quality is done, biggest impact was reducing the air that was associated with manual entry. Speculating there was data entry errors that was dramatic ranging from 70 to 20 %.
- DATIM and country systems, the data elements are released and published in both system, can be done independently, by including additional datat that has been added or included.
- Protocol that describess what happens if there are changes to know what system has actually changed and how to update it. This is being worked on fro the near future. Want experience first on how specifications are working, to decide best transport protocol to use for that message.
- Step 1 ad 2 are perquisites. Recommend creating mapping files. Second step to perform business validation checks, system will only file format, data formats and types example, if system going up to 5, DATIM will not check if you put in 100
- Step 3: Data element can be reported as either code or UID, code is recommended for readablitiy, time is reported yyyyMM. Some changes are still being made, Date to day level is initial requirement. Documenatation will be updated.
- Which enviornment are we doing the excercise?