Aggregate Data Exchange
Summary
The Aggregate Data Exchange (ADX) Profile supports interoperable public health reporting of aggregate health data. These most typically take the form of routine reports (weekly, monthly, quarterly etc.) from a health facility to some administrative jurisdiction such as a health district, though there are numerous other use cases such as international reporting and community health worker reporting.
The motivating context for this profile originates in health systems management in developing countries though its potential use is not restricted to these environments. What are collectively called developing countries are very diverse environments. Information systems need to be able to scale and adapt across diverse and changing conditions. Electronic medical record systems (EMR) penetration is often limited (but also often growing) leading to varied and mixed modes of data collection and transmission. ADX Profile provides a formal specification to guide the generation and exchange of aggregate data from these systems.
Benefits
The primary benefit of ADX is that it allows jurisdictions to formally define and publish routine report definitions. Users of ADX are then able to produce and consume ADX messages which can be validated according to the published definitions. The ADX data format is relatively simple, unemcumbered and extensible making it easy to implement in a range of different systems.
Details
The Aggregate Data Exchange (ADX) Profile enables reporting of aggregate health data tuples. ADX will typically be used to represent these data tuples for numerators and denominators which can be used in the construction of public health indicators. These tuples are sets of values which are keyed according to a data element subject, a temporal dimension, and a spatial dimension.
An example of a data tuple is the number of live births recorded in January 2017 at Nyamandhlovu Clinic.
| Data Tuple | Example |
|---|---|
| Data element subject | the number of live births |
| Temporal dimension | January 2017 |
| Spatial dimension | Nyamandhlovu Clinic |
ADX defines:
- A Content Data Structure Creator that creates a data structure definition (DSD) and validation schemas that enable an implementing jurisdiction to formally define the aggregate health data to be exchanged.
- A Content Data Structure Consumer that consumes a DSD to produce or consume aggregate health data.
- The DSD and schema describe lightweight, formal XML messages containing aggregate health data that meet the requirements of the use cases in the implementing jurisdiction.
- Content Creator and Consumer Actors use the ADX DSD and schema to construct and validate ADX/XML messages containing aggregate health data in their jurisdiction.
The ADX specification does not define the semantic content of the routine reports. Rather it provides a mechanism by which jurisdictions can define reports using SDMX data structure definitions. Producers and consumers of ADX data messages make use of these definitions to validate and constrain the content. This relationship is illustrated in the diagram below:
Systems Affected
- National Health Management Information Systems would make use of ADX to receive routine reports from health facilities and other national systems.
- EMR systems at health facilities might use ADX to create their monthly reports.
- National logistics and human resource systems might use ADX to produce summary data.
- International organizations might use ADX to harmonize reporting between regions and countries.
Actors & Transactions:
<Insert an actor-transaction diagram, and or list of Content Definitions>
Specification
Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>
Documents:
<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>
IHE Radiology Technical Framework:
Underlying Standards:
<list all the standards on which the profile is based; if possible with links to sources>
See Also
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
Related Profiles
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
- Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
- Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
- Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
- Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
- Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.
Consumer Information
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
Implementer Information
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
Reference Articles
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >
This page is based on the Profile Overview Template <Delete this Category Templates line since your Profile page is no longer a template.>