Difference between revisions of "Mobile Aggregate Data Exchange (mADX)"
|Line 21:||Line 21:|
Revision as of 17:36, 17 June 2019
The Mobile Aggregate Data Exchange (mADX) 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. As the motivating context and use cases for this profile is the same as the Aggregate Data Exchange (ADX) profile, they are not repeated here. The mADX and ADX file are intended to be functionally equivalent.
The primary purpose of the mADX profile is to provide an alternative for the exchange and management of the metadata required for routine reporting by replacing the use of SDMX with HL7 FHIR. Metadata data in ADX, or ADX/DSD, is a profile of the SDMX Data Structure Definition (DSD). Challenges in working with it include: Scaling limitations as it requires ongoing maintenance of facility and location lists in the ADX/DSD. Bandwidth limitations when trying to transfer an ADX/DSD for validation of an ADX. Facility and location lists can be large which complicates deployments in resource constrained settings. Management and exchange of code lists for disaggregators.
mADX profiles HL7 FHIR Terminology Services and the HL7 FHIR Measure resource to produce a mADX/DSD. Additionally this profile makes use of the Mobile Care Services Discovery (mCSD) profile for facility and location data. The mADX profile will allow vendors and implementers to utilize the robust ecosystem of tools around HL7 FHIR and promote standards-based routine reporting.
The mADX profile describes the actors, transactions, messages, and steps for validation.