...
Resource element (CodeableConcept) | FHIR ValueSet | SNOMED CT attribute | SNOMED CT range | Comments | ||||||
---|---|---|---|---|---|---|---|---|---|---|
Observation.category | https://www.hl7.org/fhir/valueset-observation-category.html#expansion | Use case for providing SNOMED mappings? | ||||||||
Observation.code | https://www.hl7.org/fhir/valueset-observation-codes.html#expansion | <<363787002|Observable entity| | ||||||||
Observation.Value.valueCodeableConcept | <<362981000|Qualifier value| MINUS <valueset for Observation.Interpretation> ? | LB: why not also members from <<441742003 Evaluation finding JC: Because they decompose (in theory) into an Observable+Qualifier pair | ||||||||
Observation.Interpretation<<442705008|Reference range interpretation value| |
| HL7 valueset (n=48) is extensible, so could add new expressivity as SNOMED codes if there were any gaps in existing list ... but that existing list is already relatively matured and 'metalled' by use, so that seem an unlikely requirement. Many of the existing members of the HL7 valuelist have obvious SNOMED equivalents, so there is scope for a mapping rather than a completely separate SNOMED-only valuelist. Mapping exercise may also reveal some holes in existing SNOMED expressivity. |