Terminology Mapper
Category: Healthcare Standards
Node id: terminology-mapper
Maturity: simulated
Risk tier: C
Standards: HIPAA, GDPR, SOC2
DEMO ONLY — returns built-in example mappings, never terminology data. Refuses to run unless demo: true, and then labels every output demo. For real code mapping use code-mapper (crosswalk table or UMLS service) or the umls_*/snomed_*/cie10_* tool nodes.
What it does
- Cross-system terminology mapping (ICD-10, SNOMED, LOINC, RxNorm, CPT)
- Code lookup with descriptions and metadata
- Free-text terminology search with ranking
- Code validation against terminology standards
- Relationship queries (parent, child, synonym hierarchies)
- UMLS CUI and NDC code support
Use cases
- ICD-10 to SNOMED code translation for clinical data exchange
- Medication code mapping for cross-system interoperability
- Terminology validation during FHIR resource creation
- Code search for clinical documentation
- Hierarchical code navigation for coding assistance
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
source_code | text | No | Source code to map (for map operation) |
source_system | text | No | Source terminology system (overrides config) |
target_system | text | No | Target terminology system (overrides config) |
code | text | No | Code to look up, validate, or get relationships for |
system | text | No | Terminology system (overrides config) |
search_text | text | No | Free-text search query (for search operation) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Demo terminology data (mapped codes, concepts, search results, validation, relationships), labelled demo |
demo | boolean | No | Always true: the output is demo data |
mapped | boolean | No | Whether the mapping/lookup/validation succeeded |
success | boolean | No | Whether the operation completed successfully |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Demo Data (not for clinical use) | demo | boolean | No | false | Must be true for the node to run: it returns built-in example data only, labelled demo | |
| Operation | operation | enum | Yes | map | map, lookup, search, validate, relationships | Terminology operation to perform |
| Source System | source_system | enum | No | icd-10, icd-9, snomed, loinc, rxnorm, cpt, umls-cui, ndc | Source terminology system for mapping | |
| Target System | target_system | enum | No | icd-10, icd-9, snomed, loinc, rxnorm, cpt, umls-cui, ndc | Target terminology system for mapping | |
| System | system | enum | No | icd-10, icd-9, snomed, loinc, rxnorm, cpt, umls-cui, ndc, all | Terminology system for lookup, validate, search, and relationships |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Max Results | max_results | number | No | 10 | min 1; max 100 | Maximum number of search results to return |
| Relationship Type | relationship_type | enum | No | all | all, parent, child, synonym | Type of relationships to retrieve |
Errors
| Code | Description |
|---|---|
NO_BACKEND | demo is not true: the node has no terminology backend and refuses to return demo data |
SOURCE_CODE_REQUIRED | Source code is required for mapping |
SYSTEMS_REQUIRED | Source and target systems required for mapping |
CODE_REQUIRED | Code required for lookup/validate/relationships |
SEARCH_TEXT_REQUIRED | Search text required for search operation |
UNSUPPORTED_OPERATION | Operation not recognized |
Runtime notes
- Result shape varies by operation: map returns mapped_codes, lookup returns concept, search returns results array, validate returns is_valid, relationships returns relationships array
- Input ports are operation-specific: use source_code+source_system+target_system for map; code+system for lookup/validate/relationships; search_text for search
- Input ports for source_system/target_system/system override their config equivalents when connected
- Without demo: true the node fails: it has no terminology backend and never returns demo data in normal operation
- With demo: true every output carries demo=true, data_source=demo and a warning; mapping_source is "demo"
- For real mappings use code-mapper (backend crosswalk or umls) or the umls_search_by_code / snomed_search / cie10_* tool nodes
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..