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. Shared Health Record

Query Patient-level Clinical Data Workflow

PreviousSave Patient-level Clinical Data WorkflowNextTerminology Service Workflows

Last updated 3 years ago

The transaction queries for previously stored clinical data for a specific patient. The following sequence diagram shows the steps involved in this transaction.

Workflow Maturity

Mature

  • One or more OpenHIE implementations of this workflow exist in one or more countries

  • Workflow is defined and ARB approved

  • Workflow is supported by mature standards

Standards*

  • XDS.b with the on-demand document option

  • CDA documents profiled by IHE PCC

  • CSD - Find matching services - ITI-73

  • PIX Query - ITI-9

  • Optionally, the MHD profile can be supported (in addition or instead of XDS.b) to enable PoC systems to query clinical content using a simpler and more modern FHIR-based approach. This option may be supported in two ways:

    • The SHR itself may support the required MHD transactions.

    • (recommended) The IL can provide an adapter to convert incoming MHD transactions to XDS.b transactions for the SHR to process as normal.

Assumptions and Prerequisites

Actors

  • PoS - The point of care system that captures a patient's clinical encounter, it is responsible for sending clinical data on to the HIE.

  • IL - Mediates the transactions between the PoS system and the infrastructure services to facilitate easier interoperability.

  • CR - The source of truth for patient demographic and identifier detail. It is able to be queried using an identifier to find the enterprise identifier for a particular person.

  • FR - The source of truth for facility information. It is able to be queried for details about a particular facility by ID.

  • SHR - Stored patients clinical information. It is able to receive and store patient clinical documents.

Interaction Description

The following is a description of the interaction steps.

#

Interaction

Data

Transaction Options

1

Query for clinical documents by patient ID and/or date

XDS.b/MHD metadata

Option 1 (must be supported): XDS.b Registry Stored Query (ITI-18) - Find Documents query

OR

Option 2 (may additionally choose to support): MHD Find document references (ITI-67) - RESTful query

Vol. 1 - Section 10, Appendix E, J, K

Vol. 2a - Sections 3.18

Vol. 2b - Sections 3.41, 3.42, 3.43

Vol. 2x - Appendix A, B, K, L, M, N, V, W

2

Resolve client identifier

HL7 QBP^Q23 message

Vol. 1 - Section 5

Vol. 2 - Sections 3.9

3

Return person record

HL7 RSP^K23 message

4

Extract ECID and enrich message with ECID

5

Query for clinical documents by ECID

XDS.b/MHDmetadata

XDS.b Registry Stored Query (ITI-18) - Find Documents query

and optionally (only if SHR support MHD directly)

MHD Find document references (ITI-67) - RESTful query

Vol. 1 - Section 10, Appendix E, J, K

Vol. 2a - Sections 3.18

Vol. 2b - Sections 3.41, 3.42, 3.43

Vol. 2x - Appendix A, B, K, L, M, N, V, W

6

Return list of document IDs

XDS.b Registry Stored Query response - list of document IDs

or optionally (only if SHR support MHD directly)

MHD Find document references response - list of document IDs

7

Return list of document IDs

XDS.b Registry Stored Query response - list of document IDs

or optionally

MHD Find document references response - list of document IDs

8

Request the content of the document by document ID

XDS.b/MHDmetadata

XDS.b Retrieve Document Set (ITI-43)

and optionally

MHD Retrieve document (ITI-68)

Vol. 1 - Section 10, Appendix E, J, K

Vol. 2a - Sections 3.18

Vol. 2b - Sections 3.41, 3.42, 3.43

Vol. 2x - Appendix A, B, K, L, M, N, V, W

9

Request the content of the document by document ID

XDS.b/MHDmetadata

XDS.b Retrieve Document Set (ITI-43)

and optionally (only if SHR support MHD directly)

MHD Retrieve document (ITI-68)

Vol. 1 - Section 10, Appendix E, J, K

Vol. 2a - Sections 3.18

Vol. 2b - Sections 3.41, 3.42, 3.43

Vol. 2x - Appendix A, B, K, L, M, N, V, W

10

If this document is a static document retrieve it

else if it is an on-demand document generate it

11

Return clinical document

XDS.b/MHDresponse - with CDA document content

12

Return clinical document

XDS.b/MHDresponse - with CDA document content

The PoS system must ensure the patient they are querying clinical information about already exists. It can do this by querying for the patient ().

The PoS system is a trusted application known by the HIE and it is registered with the interoperability layer to be able to send and receive data securely ().

The SHR MUST be able to generate on-demand documents in the format using the data it stored in the . Optionally, any other sections that have been discretely imported and are deemed useful may be added to the generated XDS-MS document.

Vol. 3 - Section 4.1, 4.2, 4.3If supporting the MHD Option:

PIX Query (ITI-9)

Vol. 3 - Section 4.1, 4.2, 4.3MHD:

Vol. 3 - Section 4.1, 4.2, 4.3MHD:

Vol. 3 - Section 4.1, 4.2, 4.3MHD:

For ODD:

References:

WHO DDCC Workflows
Query patients workflow
Common message security workflow
XDS-MS
save patient-level clinical data workflow
IHE IT Infrastructure
MHD profile supplement
IHE IT Infrastructure
IHE IT Infrastructure
MHD profile supplement
IHE IT Infrastructure
MHD profile supplement
IHE IT Infrastructure
MHD profile supplement
XDS-MS Specification