Aggregate Data Exchange - HIV

Summary

The ADX (Aggregate Data Exchange) profile affords data exchange partners a way to define a Data Structure Definition and the associated normative schema of the data message for a particular indicator report. To foster further adoption, the Aggregate Data Exchange-HIV (ADX-HIV) profile leverages the ADX profile to develop a content specification specifically for HIV. ADX-HIV Profile leverages on the ADX Profile version 2.1, which is currently published for trial implementation. It aims to set down a concrete example of how to leverage ADX profile for interoperability in health information systems used for managing and reporting on HIV.

Benefits

ADX-HIV will help govern and enforce interoperability between HIV point of care (source) systems and HMIS (receiver) systems. This will reduce the burden within jurisdictions for developing HIV core indicators schema. It will also foster harmonization of HIV core indicators across jurisdictions and increase the ability to compare results between health facilities, subnational levels and even countries.

Details

This ADX-HIV profile defines a common DSD for HIV core indicators with data elements and associated disaggregations along with instructions regarding how to leverage these to generate and exchange conformant XML messages. Interoperable message exchange will be valuable to jurisdictions such as Ministries of Health, and WHO, and to health initiatives such as the U.S. President’s Emergency Plan for AIDS Relief (PEPFAR), the Global Fund, UNAIDS, and others (see figure below).

A jurisdiction can extend the ADX-HIV DSD and validation schemas to meet additional HIV reporting requirements specific to their context.

Systems Affected

• National Health Management Information Systems would make use of ADX to receive HIV routine reports from health facilities and other national systems.
• EMR systems at health facilities might use ADX to create HIV monthly reports.
• International organizations might use ADX to harmonize HIV reporting between regions and countries.

Specification

Profile Status: Public Comments

Documents:

Underlying Standards:

• ADX Profile ADX Supplement
• ISO 8601
• SNOMED-CT
• HL7

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