Query Concept Maps
This transaction allows a PoS, or any OHIE component, to access terminological information in the terminology service to query for Concept Maps. A typical example would be to request the set of Concept Maps whose target Code System is SNOMED CT. 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.
Query Concept Maps: What Concept Maps have a map target of 'SNOMED CT''?
Workflow Maturity | Mature |
|
Standards* |
| |
Assumptions and Prerequisites | The required Concept Maps have been preloaded into the Terminology Service. | |
Actors |
|
Interaction Description
The following is a description of the interaction steps.
# | Interaction | Data | Transaction Options |
1 | Query Concept Map request | The Concept Map search request is triggered by a PoS or other HIE component. Input: A set of FHIR search parameters. | FHIR ConceptMap Resource |
2 | Query Concept Map response | The response is sent back to the requesting system. Output: a Bundle of ConceptMap Resources that satisfy the search parameters. | FHIR ConceptMap Resource |
Last updated