FHIRPath Specification
3.0.0-ballot - R2 STU1 International flag

FHIRPath Specification, published by Implementable Technology Specifications WG. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/FHIRPath/ and changes regularly. See the Directory of published versions

: Example Observation - TTL Representation

Raw ttl | Download


@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 class=\"res-header-id\"><b>Generated Narrative: Observation example</b></p><a name=\"example\"> </a><a name=\"hcexample\"> </a><a name=\"example-en-US\"> </a><p><b>status</b>: Final</p><p><b>category</b>: <span title=\"Codes:{http://terminology.hl7.org/CodeSystem/observation-category vital-signs}\">Vital Signs</span></p><p><b>code</b>: <span title=\"Codes:{http://loinc.org 29463-7}, {http://loinc.org 3141-9}, {http://snomed.info/sct 27113001}, {http://acme.org/devices/clinical-codes body-weight}\">Body Weight</span></p><p><b>subject</b>: <a href=\"Patient-example.html\">Jim  Male, DoB: 1974-12-25 ( Medical record number (use: usual, period: 2001-05-06 --&gt; (ongoing)))</a></p><p><b>effective</b>: 2016-03-28</p><p><b>value</b>: 185 lbs<span style=\"background: LightGoldenRodYellow\"> (Details: UCUM  code[lb_av] = '[lb_av]')</span></p></div>"
  ] ; # 
  fhir:status [ fhir:v "final"] ; #     the mandatory quality flags:    
  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:effective [ fhir:v "2016-03-28"^^xsd:date] ; # encounter>
#		<reference value="Encounter/example"/>
#	</encounter
  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)
#