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
  • Interaction Description
  1. Workflow (Exchange) Specification
  2. Terminology Service Workflows

Translate Code

PreviousExpand Value SetNextVerify Code Existence

Last updated 3 years ago

This transaction allows a PoS, or any OHIE component, to access terminological information in the terminology service and retrieve the translation, or "mapping" of a Concept in one Code System to a Concept in another Code System. Mapping is frequently required when patient data is collected using Concepts/Codes from one Code System but the data must be reported or aggregated, say for decision support, in a different Code System. The set of such associated Concepts, usually for a specific use-case, are stored in the Terminology Service in a FHIR Resource called a ConceptMap.

Both external systems and systems inside the HIE may perform this transaction directly with the TS. The sequence diagram below shows the steps that occur for a system using this transaction.

  1. Mapping: Using the ConceptMap 'ICD-10 to SNOMED CT Diseases', retrieve the SNOMED CT Concept Code(s) that is associated with '123XYZ' in ICD-10.

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*

This workflow implements the IHE IT Infrastructure Technical Framework Supplement - Sharing Valuesets, Codes, and Maps (SVCM) Transaction: Translate Code ITI-Y7.

Assumptions and Prerequisites

The required ConceptMap and associated CodeSystem(s) have been preloaded into the Terminology Service.

Actors

  • PoS - The point-of-service system or other HIE component that is requesting the translation.

  • TS - Stores the curated, official version of the ConceptMap for the health system.

Interaction Description

The following is a description of the interaction steps.

#

Interaction

Data

Transaction Options

1

ConceptMap translate request

The translate request is triggered by a PoS or other HIE component.

Input: The ConceptMap name and source Code and CodeSystem.

FHIR ConceptMap Resource, $translate operation

2

ConceptMap translate response

The response is sent back to the requesting system.

Output: a set of parameters including a Boolean 'result, and a list of, possibly qualified, Code matches.

FHIR ConceptMap Resource, $translate operation

The FHIR ConceptMap translate operation: . HL7 FHIR Specifications v3.0 or higher support translate. The response is a set of FHIR Parameter objects that include a 'result' (whether there is an acceptable match) and a list of possible matches. The list of matches may include notes of Codes for which mappings are specifically excluded, and qualifications on the applicability of matches.

http://build.fhir.org/conceptmap-operation-translate.html