Mobile Aggregate Data Exchange
3.0.0 - trial-use
Mobile Aggregate Data Exchange, published by IHE QRPH Technical Committee. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/QRPH.mADX/ and changes regularly. See the Directory of published versions
The QRPH registry of OIDs is located at https://wiki.ihe.net/index.php/QRPH_Registry
Additions to the QRPH OID Registry are:
codeSystem | codeSystemName | Description |
---|---|---|
NA | NA | NA |
NA
Profile | Format Code | Media Type | Template ID |
---|---|---|---|
NA | NA | NA | NA |
Code | Description |
---|---|
NA | NA |
Code | Description |
---|---|
NA | NA |
NA
NA
This section defines Content Modules for the mobile Aggregate Data Exchange (mADX) Profile.
A Content Data Structure Creator creates mADX-conformant Measure and schema streams. Typically, the mADX Content Data Structure Creator will be an implementing jurisdiction such as a ministry of health, a global non-government organization (NGO), or a donor.
Content Creators and Content Consumers exchange a data payload that conforms to the mADX compliant resources. A sample mADX compliant data payload is provided in the informative Appendix 8C.
Additional (informative) message constraints for interoperability of mADX data exchange which are outside of the scope of this profile are described in Section 3:8.4.
The purpose of profiling the base Measure, through the CRMIShareableMeasure profile, is to provide guidance regarding which parts of an mADX Measure are fixed by the profile and which parts may be extended to support implementation-specific requirements.
An mADX FHIR Measure Report shall be compliant with the additional constraints defined in Section 3:8.3 of this profile.
There are implicit assumptions regarding the sharing of additional metadata between Content Creators and Content Consumers which are not covered within the scope of the mADX Profile. To ensure semantic validity of the exchanged data, the constraints described below shall be specified using processes not defined by this profile:
The Value type (real or integer) expected for individual data elements.
The preceding is not an exhaustive list. Other business rules that may affect interoperability may need to be established such as bounds on data values, bounds on date ranges, relationships between different data elements (e.g., the sum of these data elements cannot be greater than the sum of those data elements, etc.).