Mappings for SNOMED CT Concept Domain Binding (http://snomed.info/conceptdomain)
ObservationImagingResult
Observation
< 363787002 |Observable entity|
status
< 445584004 |Report by finality status|
code
< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
value[x]
< 441742003 |Evaluation finding|
interpretation
< 260245000 |Findings values|
bodySite
< 123037004 |Body structure|
specimen
< 123038009 |Specimen|
device
< 49062001 |Device|
referenceRange
type
< 260245000 |Findings values| OR
< 365860008 |General clinical state finding|
OR
< 250171008 |Clinical history or observation findings| OR
< 415229000 |Racial group| OR
< 365400002 |Finding of puberty stage| OR
< 443938003 |Procedure carried out on subject|
appliesTo
< 260245000 |Findings values| OR
< 365860008 |General clinical state finding|
OR
< 250171008 |Clinical history or observation findings| OR
< 415229000 |Racial group| OR
< 365400002 |Finding of puberty stage| OR
< 443938003 |Procedure carried out on subject|
component
code
< 363787002 |Observable entity| OR
< 386053000 |Evaluation procedure|
OBX.21 For OBX segments from systems without OBX-21 support a combination of ORC/OBR and OBX must be negotiated between trading partners to uniquely identify the OBX segment. Depending on how V2 has been implemented each of these may be an option: 1) OBR-3 + OBX-3 + OBX-4 or 2) OBR-3 + OBR-4 + OBX-3 + OBX-4 or 2) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.
basedOn
ORC
partOf
Varies by domain
status
OBX-11
code
OBX-3
subject
PID-3
focus
OBX-3
encounter
PV1
effective[x]
OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
issued
OBR.22 (or MSH.7), or perhaps OBX-19 (depends on who observation made)