Export Aggregate Data
This workflow enables aggregate data to be generated and exported to another system. This is useful for exporting routine reporting data to an upstream HMIS system for high-level reporting.
Workflow Maturity
Maturing
  • Workflow is defined and ARB approved
  • Workflow is supported by the IHE ADX profile or the mADX profile
Assumptions and Prerequisites
The sender and the receiver must use the same metadata or there must be a translation step
Actors
Sender
The system that produces the aggregate data to be exported. This could be a point-of-service system like an EMR or an HMIS that is sending to another HMIS. It could also be a mediator or other service that produces an aggregate message.
Interoperability Layer (IL)
Interoperability Layer (IL) is the component that enables easier interoperability between disparate information systems by connecting the infrastructure services and client applications together. An interoperability layer receives transactions from the point of service systems and coordinates interaction between components of the HIE and provides common core functions to simplify the interoperability between systems.
Receiver The system that will be receiving aggregate data. Examples of this system could be an external HMIS system or an HIE.

Interaction Description

#
Interaction
Data / Note
Transaction Standards
1
Initiate the transaction, aggregate months into quarters as necessary and create the aggregate data message.
ADX - Aggregate Data generated by the HMIS.
ADX or mADX
2
Export the Aggregate Data Message to the IL
ADX - Aggregate Data generated by the HMIS.
ADX or mADX
3
Map site codes or other metadata as needed (optional if site / facility codes are aligned between the two systems)
CSD for site codes and other standards as applicable
4
Update the aggregate message with the receiver's site codes
Update the aggregate message with receiver's site codes or other metadata.
5
Return processing response
The External system will process the aggregate data message and respond with information about the records processed and/or provide a description of errors.
May contain error messages and/or confirmation of successful processing.
6
Log the processing response
7
Forward aggregate data processing response
8
Process the response
This step can be different for different implementations. The response will contain error messages or provide information about the successful processing of the message.

Copy link