230 likes | 468 Views
Standards based interoperability with SDMX-HD. 6 April 2011 Hoi An, Vietnam. What problems are we trying to solve?. WHO Indicator and Measurement Registry (IMR). Varying definitions from multiple guidelines documents. Interoperability in an heterogeneous environment. SDMX-HD.
E N D
Standards based interoperability with SDMX-HD 6 April 2011 Hoi An, Vietnam
What problems are we trying to solve? WHO Indicator and Measurement Registry (IMR) Varying definitions from multiple guidelines documents. Interoperability in an heterogeneous environment. SDMX-HD
SDMX-HD • SDMX-HD: Statisitical Data and Metadata eXchange format • – for the Health Domain • Developed by WHO and partners to facilitate exchange of • indicator definitions and data in aggregate data systems.
SDMX-HD Use • WHO Indicator and Measurement Registry (IMR) • Monitoring and Evaluation • District Health Information System (DHIS2) • Country Response Information System (CRIS PEPFAR proposed) • Clinical • OpenMRS • EpiS3 (OpenEHR) • OSHIP • Human Resources - iHRIS • Logistics - OpenLMIS • Lab - OpenELIS
Example of SDMX-HD use for integration Vision for HIS Interoperability AE
PHU6 Report (Sample) • # Of health workers disaggregated by facility, cadre, • and whether or not they are on salary • Not intended for human consumption
iHRIS and SDMX-HD • iHRIS imports codelists from SDMX-HD DSD files, mapped to • SimpleList using the SDMX-HD form storage mechanism: • <configurationGroup name="cl_facility" path=”/modules/forms/forms/cl_facility”> <displayName>SDMX-HD Code List: cl_facility</displayName> <description>The SDMX-HD Code List: Facility</description> <configuration name="class" values="single"> <value>I2CE_SimpleList</value> </configuration> <configuration name="display" values="single" locale="en_US"> <value>Facility</value> </configuration> <configuration name="storage" values="single"> <value>SDMXHD</value> </configuration> <configurationGroup name="storage_options" path="storage_options/SDMXHD"> <configuration name="file" values="single"> <value>DSD_2010_05_07.xml</value> </configuration> <configuration name="CodeListID" values="single"> <value>CL_FACILITY</value> </configuration> </configurationGroup> </configurationGroup>
Mapping Codelists • Codelists should be mapped to existing data • <configurationGroup name="SL-Facility-Link" path="/I2CE/formsData/forms/list_linkto_list_magicdata"> <configurationGroup name="facility_1043__cl_facility_1069"> <configurationGroup name="fields"> <configuration name="list"> <value>facility|1043</value> </configuration> <configuration name="links_to"> <value>cl_facility|1069</value> </configuration> </configurationGroup> </configurationGroup> …. </configuraitonGroup>
Cross Section Data Export • iHRIS has a built-in (though meaningless) XML export format. • Any view of a report can be associated with one or more XSLT. • You can choose to export XML after applying XSLT. • In particular, XSLT to transform into SDMX Cross-Sectional Data.
Enterprise architecture: 3 Levels Patient records Institutional use of information DHIS Data warehouse Aggregate data iHRIS Open MRS Applications supporting use of information Data & indicator standards SDMX-HD Facility list SDMX-HD Data Standards and infrastructure supporting the applications
Links • WHO Indicator and Measurement Registry • Public: www.who.int/gho/indicatorregistry • Global Health Observatory: http://apps.who.int/ghodata/ • SDMX: www.sdmx.org , www.sdmx-hd.org • www.openmrs.org • www.dhis2.org • www.capacityproject.org/hris • http://open.intrahealth.org/mediawiki/Sierra_Leone_Sample_Installation • http://www.healthunbound.org/content/his-west-africa-sis-afrique-de-louest
Thanks! Special thanks for valuable input: Patrick Whitaker, Chris Seebregts, Carl Leitner