Aller au contenu principal

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​

NameTypeRequiredDescription
source_codetextNoSource code to map (for map operation)
source_systemtextNoSource terminology system (overrides config)
target_systemtextNoTarget terminology system (overrides config)
codetextNoCode to look up, validate, or get relationships for
systemtextNoTerminology system (overrides config)
search_texttextNoFree-text search query (for search operation)

Output ports​

NameTypeRequiredDescription
resultjsonNoDemo terminology data (mapped codes, concepts, search results, validation, relationships), labelled demo
demobooleanNoAlways true: the output is demo data
mappedbooleanNoWhether the mapping/lookup/validation succeeded
successbooleanNoWhether the operation completed successfully

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Demo Data (not for clinical use)demobooleanNofalseMust be true for the node to run: it returns built-in example data only, labelled demo
OperationoperationenumYesmapmap, lookup, search, validate, relationshipsTerminology operation to perform
Source Systemsource_systemenumNoicd-10, icd-9, snomed, loinc, rxnorm, cpt, umls-cui, ndcSource terminology system for mapping
Target Systemtarget_systemenumNoicd-10, icd-9, snomed, loinc, rxnorm, cpt, umls-cui, ndcTarget terminology system for mapping
SystemsystemenumNoicd-10, icd-9, snomed, loinc, rxnorm, cpt, umls-cui, ndc, allTerminology system for lookup, validate, search, and relationships

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Max Resultsmax_resultsnumberNo10min 1; max 100Maximum number of search results to return
Relationship Typerelationship_typeenumNoallall, parent, child, synonymType of relationships to retrieve

Errors​

CodeDescription
NO_BACKENDdemo is not true: the node has no terminology backend and refuses to return demo data
SOURCE_CODE_REQUIREDSource code is required for mapping
SYSTEMS_REQUIREDSource and target systems required for mapping
CODE_REQUIREDCode required for lookup/validate/relationships
SEARCH_TEXT_REQUIREDSearch text required for search operation
UNSUPPORTED_OPERATIONOperation 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.

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.