OpenHIE Architecture Specification
4.0
4.0
  • Specification Overview
  • How to use the Specification
  • Architecture Specification
    • Architecture
    • Architectural Principles
    • Standards and Profiles
  • OpenHIE Component Specifications
    • Non-Functional Requirements
    • Client Registry (CR)
    • OpenHIE Facility Registry (FR)
    • OpenHIE Finance and Insurance Service (FIS)
    • OpenHIE Health Management Information System (HMIS)
    • OpenHIE Health Worker Registry (HWR)
    • OpenHIE Interoperability Layer (IOL)
    • OpenHIE Logistics Management Information System (LMIS)
    • OpenHIE Product Catalogue (PC)
    • OpenHIE Shared Health Record (SHR)
    • OpenHIE Terminology Service (TS)
    • Point-Of-Care Systems
  • Workflow (Exchange) Specification
    • Aggregate Reporting Workflows
      • Export Aggregate Data
      • Validate and Save Aggregate Data
    • Alerting / Sending Reminders or Information
      • Send Client Alert Workflow
      • Send Health Worker Alert Workflow
    • Care Services Discovery
      • Query Health Worker and/or Facility Records Workflow
      • Query Care Services Records Workflow
      • Search Care Services Workflow
      • Request Care Services Updates Workflow
    • Laboratory Work Flows
      • Order Laboratory Test
      • Report Lab Results
    • Patient Identity Management Workflows
      • Create Patient Demographic Record Workflow
      • Update Patient Demographic Record Workflow
      • Query Patient Demographic Records by Identifier Workflow
      • Query Patient Demographic Records by Demographics Workflow
    • Shared Health Record
      • Save Patient-level Clinical Data Workflow
      • Query Patient-level Clinical Data Workflow
    • Terminology Service Workflows
      • Expand Value Set
      • Translate Code
      • Verify Code Existence
      • Verify Code Membership
      • Query Value Set
      • Query Code Systems
      • Query Concept Maps
      • Lookup Code
    • Vaccine Workflows
  • How to Provide Feedback and Input
  • Change Log and Versioning
Powered by GitBook
On this page
  1. Workflow (Exchange) Specification
  2. Aggregate Reporting Workflows

Validate and Save Aggregate Data

PreviousExport Aggregate DataNextAlerting / Sending Reminders or Information

Last updated 3 years ago

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

  • Workflow is defined and ARB approved

  • Workflow is supported by emerging IHE ADX standard

Standards*

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

  • The system sending the ADX message. The system may be a Health Information Exchange with patient-level abilities to aggregate data and/or a system that contains aggregate level data. The system may also be a point-of-service system that contains or produces aggregate data.

Receiving HIE

  • IL -The 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 external system and coordinates interaction between components of the HIE and provides common core functions to simplify the interoperability between systems.

  • HMIS - Health Management Information System that is processing and storing the aggregate data (ADX message) received.

Interaction Description

#

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

ADX for structuring aggregate data -

ADX -

http://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_ADX.pdf
http://www.ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_ADX.pdf