The official version of the OHIE workflows can be found in the OpenHIE Architecture Specification.


Description: 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.

Sponsor:  Jack Bowie

Status:  This operation has been extensively tested in FHIR Connectathons. 

Referenced Standards and APIs

Assumptions and Prerequisites


title Translate Code
participant PoS
participant TS

PoS->+TS: [1] Translate code request
TS->PoS: [2] Translate code response

Technical details

Below enter each interaction that makes up the described workflow above.

RefInteractionEndpointDataTransaction Specification
1ConceptMap translate requestTS

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
2ConceptMap translate responsePoS

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