$translate on ConceptMap
Translate code from one value set to another, based on the existing value set and concept maps resources, and/or other additional knowledge available to the server.
Last updated
Translate code from one value set to another, based on the existing value set and concept maps resources, and/or other additional knowledge available to the server.
Last updated
All the examples can be found at the "FHIR ConceptMap Resource and translation"
community notebook which is accessible via your Aidbox Notebooks UI Tab
Parameter | Type | Description |
---|---|---|
ConceptMaps are ungrouped on create to have an opportunity to use Search API instead of $tranalate operation. ConceptMaps are transformed into ConceptMapRule resources.
element
as in ConceptMap
source
: source system where concepts to be mapped are defined
target
: target system that the concepts are to be mapped to
sourceValueSet
: the source value set that contains the concepts that are being mapped
targetValueSet
: the target value set which provides context for the mappings
conceptMapId
: id of the original ConceptMap
conceptmapUrl
: url of the original ConceptMap
unmapped
: as in ConceptMap
Created ConceptMap does not have group
property as it is just a meta header resource.
In order to convert a huge ConceptMap to ndjson bundle use this FHIR converter.
The output bundle consists of ConceptMap meta resource and the set of ConceptMapRule resources.
Use Bulk API to upload output bundle.
Aidbox doesn't store ConceptMap groups in ConceptMap resource as mentioned above.
To get full ConceptMap resource make a request using /fhir
prefix.
Example:
code
required
The code that is to be translated
system
required
The system for the code that is to be translated
url
optional
A canonical URL for a concept map.
Ignored when ConceptMap id is provided
reverse
optional
If true, the translate
should return all the codes that might be mapped to the given code