Validate and Save Aggregate Data
Last updated
Last updated
This workflow specifies the interactions for validating and saving an aggregate data message that has been transmitted from an external system to the HIE.
Workflow Maturity | Maturing |
|
Standards* | ADX for structuring aggregate data - http://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_ADX.pdf | |
Assumptions and Prerequisites | The sender and receiver have the same metadata (indicator, disaggregators and facilities). If not, the metadata will need to be translated. | |
Actors | Sender - External System Actor
Receiving HIE
|
# | Interaction | Data / Notes | Transaction Options |
1 | Receive Aggregate Data Message (The process is initiated by the receipt of an Aggregate Data Message.) | ADX data | |
2 | Ensure sender is authenticated and log a copy of the message | ||
3 | Route message to the HMIS | Implementation choice: Implementers may select to validate the aggregate data message with a DSD before routing it to the HMIS. | |
4 | Process the ADX Message | Implementation requirements: Each implementation may have specified rules or data checks that are performed on the message as it is imported into the system. These checks may include data/metadata checks, numerator and denominator checks and checks to be sure that reporting entities reported on the desired indicators. | |
5 | (Optional) Generate processing response | The current ADX standard does not specify a processing response. | |
6 | (Optional) Log the processing response and return it to the ADX |