DiagnosticsThis page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions
. Page versions: R5 R4B R4 R3
| Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Device, Encounter, Patient, Practitioner, RelatedPerson |
Raw Turtle (+ also see Turtle/RDF Format Specification)
Simple Weight Example
@prefix fhir: <http://hl7.org/fhir/> .
@prefix loinc: <https://loinc.org/rdf/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sct: <http://snomed.info/id/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# - resource -------------------------------------------------------------------
[a fhir:Observation ;
fhir:nodeRole fhir:treeRoot ;
fhir:id [ fhir:v "example"] ; #
fhir:text [
fhir:status [ fhir:v "generated" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p><b>Generated Narrative: Observation</b><a name=\"example\"> </a></p><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Resource Observation "example" </p></div><p><b>status</b>: <span title=\" the mandatory quality flags: \">final</span></p><p><b>category</b>: <span title=\" category code is A code that classifies the general type of observation being made. This is used for searching, sorting and display purposes. \">Vital Signs <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"http://terminology.hl7.org/5.1.0/CodeSystem-observation-category.html\">Observation Category Codes</a>#vital-signs)</span></span></p><p><b>code</b>: <span title=\" \n Observations are often coded in multiple code systems.\n - LOINC provides codes of varying granularity (though not usefully more specific in this particular case) and more generic LOINCs can be mapped to more specific codes as shown here\n - snomed provides a clinically relevant code that is usually less granular than LOINC\n - the source system provides its own code, which may be less or more granular than LOINC\n \">Body Weight <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"https://loinc.org/\">LOINC</a>#29463-7; <a href=\"https://loinc.org/\">LOINC</a>#3141-9 "Body weight Measured"; <a href=\"https://browser.ihtsdotools.org/\">SNOMED CT</a>#27113001 "Body weight"; clinical-codes#body-weight)</span></span></p><p><b>subject</b>: <a href=\"patient-example.html\">Patient/example</a> "Peter CHALMERS"</p><p><b>encounter</b>: <a href=\"encounter-example.html\">Encounter/example</a></p><p><b>effective</b>: 2016-03-28</p><p><b>value</b>: <span title=\" In FHIR, units may be represented twice. Once in the\n agreed human representation, and once in a coded form.\n Both is best, since it's not always possible to infer\n one from the other in code.\n\n When a computable unit is provided, UCUM (http://unitsofmeasure.org)\n is always preferred, but it doesn't provide notional units (such as\n "tablet"), etc. For these, something else is required (e.g. SNOMED CT)\n \">185 lbs<span style=\"background: LightGoldenRodYellow\"> (Details: UCUM code [lb_av] = 'lb_av')</span></span></p></div>"
] ; # the mandatory quality flags:
fhir:status [ fhir:v "final"] ; #
fhir:category ( [
fhir:coding ( [
fhir:system [ fhir:v "http://terminology.hl7.org/CodeSystem/observation-category"^^xsd:anyURI ] ;
fhir:code [ fhir:v "vital-signs" ] ;
fhir:display [ fhir:v "Vital Signs" ]
] )
] ) ; # category code is A code that classifies the general type of observation being made. This is used for searching, sorting and display purposes.
fhir:code [
fhir:coding ( [
a loinc:29463-7 ;
fhir:system [ fhir:v "http://loinc.org"^^xsd:anyURI ] ;
fhir:code [ fhir:v "29463-7" ] ;
fhir:display [ fhir:v "Body Weight" ] # more generic methodless LOINC
] [
a loinc:3141-9 ;
fhir:system [ fhir:v "http://loinc.org"^^xsd:anyURI ] ;
fhir:code [ fhir:v "3141-9" ] ;
fhir:display [ fhir:v "Body weight Measured" ] # translation is more specific method = measured LOINC
] [
a sct:27113001 ;
fhir:system [ fhir:v "http://snomed.info/sct"^^xsd:anyURI ] ;
fhir:code [ fhir:v "27113001" ] ;
fhir:display [ fhir:v "Body weight" ]
] [
fhir:system [ fhir:v "http://acme.org/devices/clinical-codes"^^xsd:anyURI ] ;
fhir:code [ fhir:v "body-weight" ] ;
fhir:display [ fhir:v "Body Weight" ]
] ) # LOINC - always recommended to have a LOINC code
] ; #
# Observations are often coded in multiple code systems.
# - LOINC provides codes of varying granularity (though not usefully more specific in this particular case) and more generic LOINCs can be mapped to more specific codes as shown here
# - snomed provides a clinically relevant code that is usually less granular than LOINC
# - the source system provides its own code, which may be less or more granular than LOINC
#
fhir:subject [
fhir:reference [ fhir:v "Patient/example" ]
] ; #
fhir:encounter [
fhir:reference [ fhir:v "Encounter/example" ]
] ; #
fhir:effective [ fhir:v "2016-03-28"^^xsd:date] ; #
fhir:value [
a fhir:Quantity ;
fhir:value [ fhir:v "185"^^xsd:decimal ] ;
fhir:unit [ fhir:v "lbs" ] ;
fhir:system [ fhir:v "http://unitsofmeasure.org"^^xsd:anyURI ] ;
fhir:code [ fhir:v "[lb_av]" ]
]] . # In FHIR, units may be represented twice. Once in the
# agreed human representation, and once in a coded form.
# Both is best, since it's not always possible to infer
# one from the other in code.
#
# When a computable unit is provided, UCUM (http://unitsofmeasure.org)
# is always preferred, but it doesn't provide notional units (such as
# "tablet"), etc. For these, something else is required (e.g. SNOMED CT)
#
# -------------------------------------------------------------------------------------
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
FHIR ®© HL7.org 2011+. FHIR R5 hl7.fhir.core#5.0.0 generated on Sun, Mar 26, 2023 15:25+1100.
Links: Search |
Version History |
Contents |
Glossary |
QA |
Compare to R4 |
Compare to R4B |
|
Propose a change