This is Snapshot #3 for FHIR R5, released to support Connectathon 32. For a full list of available versions, see the Directory of published versions.
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: <http://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:Resource.id [ fhir:value "example"]; # fhir:DomainResource.text [ fhir:Narrative.status [ fhir:value "generated" ]; fhir:Narrative.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/4.0.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:Observation.status [ fhir:value "final"]; # fhir:Observation.category [ fhir:index 0; fhir:CodeableConcept.coding [ fhir:index 0; fhir:Coding.system [ fhir:value "http://terminology.hl7.org/CodeSystem/observation-category" ]; fhir:Coding.code [ fhir:value "vital-signs" ]; fhir:Coding.display [ fhir:value "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:Observation.code [ fhir:CodeableConcept.coding [ fhir:index 0; a loinc:29463-7; fhir:Coding.system [ fhir:value "http://loinc.org" ]; fhir:Coding.code [ fhir:value "29463-7" ]; fhir:Coding.display [ fhir:value "Body Weight" ] # more generic methodless LOINC ], [ fhir:index 1; a loinc:3141-9; fhir:Coding.system [ fhir:value "http://loinc.org" ]; fhir:Coding.code [ fhir:value "3141-9" ]; fhir:Coding.display [ fhir:value "Body weight Measured" ] # translation is more specific method = measured LOINC ], [ fhir:index 2; a sct:27113001; fhir:Coding.system [ fhir:value "http://snomed.info/sct" ]; fhir:Coding.code [ fhir:value "27113001" ]; fhir:Coding.display [ fhir:value "Body weight" ] ], [ fhir:index 3; fhir:Coding.system [ fhir:value "http://acme.org/devices/clinical-codes" ]; fhir:Coding.code [ fhir:value "body-weight" ]; fhir:Coding.display [ fhir:value "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:Observation.subject [ fhir:Reference.reference [ fhir:value "Patient/example" ] ]; # fhir:Observation.encounter [ fhir:Reference.reference [ fhir:value "Encounter/example" ] ]; # fhir:Observation.effectiveDateTime [ fhir:value "2016-03-28"^^xsd:date]; # fhir:Observation.valueQuantity [ fhir:Quantity.value [ fhir:value "185"^^xsd:decimal ]; fhir:Quantity.unit [ fhir:value "lbs" ]; fhir:Quantity.system [ fhir:value "http://unitsofmeasure.org" ]; fhir:Quantity.code [ fhir:value "[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) # - ontology header ------------------------------------------------------------ [a owl:Ontology; owl:imports fhir:fhir.ttl] . # -------------------------------------------------------------------------------------
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 Ballot hl7.fhir.core#5.0.0-snapshot3 generated on Wed, Dec 14, 2022 07:17+1100.
Links: Search |
Version History |
Contents |
Glossary |
QA |
Compare to R4B |
Compare to R5 Draft |
|
Propose a change