OpenHIE Architecture Specification
5.2-en
5.2-en
  • Specification Overview
    • GitBook Version Change Control Process
    • How to use the Specification
    • Version Change Log
    • How to Provide Feedback and Input
  • 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
  • Data 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
    • OpenHIE Finance and Insurance Services Workflows
      • HFW-001: Enroll Beneficiary
      • HFW-002: Query Beneficiary
      • HFW-003: Check Coverage Eligibility
      • HFW-004: Claiming
      • HFW-005: Claim Tracking
Powered by GitBook
On this page
  • Interaction Description
  1. Data Exchange Specification
  2. Laboratory Work Flows

Order Laboratory Test

PreviousLaboratory Work FlowsNextReport Lab Results

Last updated 1 year ago

Electronic Medical Records (EMRs) systems can send an electronic lab order to a laboratory information system (LIS).

Workflow Maturity

Newly Defined

  • Workflow is defined and ARB approved

  • Initial implementations are being implemented

Standards

  • FHIR R4 search on Task, DiagnosticReport, ServiceRequest or Patient resources

  • FHIR R4 bundle search response

  • FHIR R4 Workflow

Assumptions and Prerequisites

  • The EMR and LIS are trusted applications known by the IOL

  • The IOL supports node authentication, audit tracking, and rerunning of failed transactions

  • The SHR adheres to OHIE specification

Actors

  • EMR - The electronic medical record system that captures the patient and order information and sends the electronic order to the LIS

  • LIS - The laboratory information system that pulls order information, processes orders, updating statuses and generating results sets

  • IOL - The interoperability layer that secures and orchestrates the exchange of information (see OHIE Interoperability layer)

  • SHR - The shared health record that serves as a centralized data store for patients’ longitudinal health record

Interaction Description

#

Interaction

Data

Transaction Options

1

Create Lab Order

Alternatively, the order save could generate a FHIR R4 ServiceRequest Resource for direct transmission.

2

Send New Lab Order

Alternatively a FHIR R4 ServiceRequest and Patient Resource bundle could be sent

3,4

Send New Lab Order

Bundled order is routed through the IOL to both the SHR and the LIS

5

Save Order and Update Order Status

Alternatively, a ServiceRequest with a link to the referenced ServiceRequest could be populated.

6

Send Order Update

Update Task Resource Status from [5] is sent to the IOL

Alternatively, this could be an update to a FHIR R4 ServiceRequest resource.

7,8

Send Order Update

IOL routes the updated FHIR R4 Tasks to the SHR and the EMR

See transaction options [6]

9

Update FHIR Task Status

FHIR task status updated locally

See transaction options [6]

The order save generates a FHIR R4 Task Resource ()

FHIR Task bundled order is sent to the IOL and consists of a FHIR R4 Task Resource and a referenced FHIR R4 Patient Resource (). Task status is aligned with the FHIR workflow communication pattern found ​.

FHIR R4 bundle ()

FHIR R4 bundle ()

FHIR R4 Task Resource Status is updated locally to either rejected or accepted. A FHIR R4 ServiceRequest Resource () is created for order processing with a reference to the associated task. EMR test requests and LIS orders are matched based on LOINC codes.

see example here
example
here
example
example
example