Diagnostics
This
page
is
part
of
the
Continuous
Integration
Build
of
FHIR
Specification
(v5.0.0:
R5
-
STU
).
This
is
the
current
published
version
in
it's
permanent
home
(it
will
always
(will
be
available
incorrect/inconsistent
at
this
URL).
For
a
full
list
of
available
versions,
see
times).
See
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
| Responsible Owner: Orders and Observations Work Group | Standards Status : Informative | Compartments : Device , Encounter , Group , Patient , Practitioner , RelatedPerson |
Raw XML ( canonical form + also see XML Format Specification )
Blood Pressure Measurement (id = "blood-pressure")
<?xml version="1.0" encoding="UTF-8"?> <Observation xmlns="http://hl7.org/fhir"> <id value="blood-pressure"/> <meta> <profile value="http://hl7.org/fhir/StructureDefinition/vitalsigns"/> </meta>display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60% an interpretation offered to the combination observation generally, it would only be appropriate to offer an interpretation of an observation that has no value if it has "COMP" (component) observations The BodySite can be captured in a LOINC code but am showing it here to demonstrate populating the element Observations are often coded in multiple code systems. - LOINC provides a very specific code (though not more specific in this particular case) - 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 this is shown here to demonstrate the concept of translations within the codeableConcept datatype. The diastolic code below only has a LOINC code<identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:uuid:187e0c12-8dd2-67e2-99b2-bf273c878281"/></identifier> <!-- demonstrating the use of the baseOn element with a fictive identifier --> <basedOn> <identifier> <system value="https://acme.org/identifiers"/> <value value="1234"/> </identifier> </basedOn> <status value="final"/> <category> <coding> <system value="http://terminology.hl7.org/CodeSystem/observation-category"/> <code value="vital-signs"/> <display value="Vital Signs"/> </coding> </category><!-- replaced by 85354-9<code> <!-- replaced by 85354-9 <coding> <system value="http://loinc.org"/> <code value="85354-9"/> <display value="Blood pressure systolic & diastolic"/> </coding>-->--> <coding> <system value="http://loinc.org"/> <code value="85354-9"/> <display value="Blood pressure panel with all children optional"/> </coding> <text value="Blood pressure systolic & diastolic"/> </code> <subject> <reference value="Patient/example"/> </subject> <effectiveDateTime value="2012-09-17"/> <performer> <reference value="Practitioner/example"/><!-- an interpretation offered to the combination observation</performer> <!-- an interpretation offered to the combination observation generally, it would only be appropriate to offer an interpretation of an observation that has no value if it has "COMP" (component)observations -->observations --> <interpretation> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation"/> <code value="L"/> <display value="low"/> </coding> <text value="Below low normal"/><!-- The BodySite can be captured in a LOINC code but am showing it here to demonstrate populating the element --></interpretation> <!-- The BodySite can be captured in a LOINC code but am showing it here to demonstrate populating the element --> <bodySite> <coding> <system value="http://snomed.info/sct"/> <code value="368209003"/> <display value="Right arm"/> </coding> </bodySite><!--<!-- Should have a refrange as well --> <component> <!-- Observations are often coded in multiple code systems. - LOINC provides a very specific code (though not more specific in this particular case) - 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 this is shown here to demonstrate the concept of translations within the codeableConcept datatype. The diastolic code below only has a LOINC code-->--> <code> <!-- LOINC -code --> <coding> <system value="http://loinc.org"/> <code value="8480-6"/> <display value="Systolic blood pressure"/></coding> <!-- SNOMED CT Codes --> <coding> <system value="http://snomed.info/sct"/> <code value="271649006"/> <display value="Systolic blood pressure"/></coding> <!-- Also, a local code specific to the source system --> <coding> <system value="http://acme.org/devices/clinical-codes"/> <code value="bp-s"/> <display value="Systolic Blood pressure"/> </coding> </code> <valueQuantity> <value value="107"/> <unit value="mmHg"/> <system value="http://unitsofmeasure.org"/> <code value="mm[Hg]"/></valueQuantity> <!-- an interpretation for the individual composite observation --> <interpretation> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation"/> <code value="N"/> <display value="normal"/> </coding> <text value="Normal"/></interpretation> </component> <!-- Should have a refrange as well --> <component> <!-- this codes only has a LOINC code --> <code> <coding> <system value="http://loinc.org"/> <code value="8462-4"/> <display value="Diastolic blood pressure"/> </coding> </code> <valueQuantity> <value value="60"/> <unit value="mmHg"/> <system value="http://unitsofmeasure.org"/> <code value="mm[Hg]"/></valueQuantity> <!-- an interpretation for the individual composite observation --> <interpretation> <coding> <system value="http://terminology.hl7.org/CodeSystem/v3-ObservationInterpretation"/> <code value="L"/> <display value="low"/> </coding> <text value="Below low normal"/> </interpretation> </component> </interpretation > <!-- Should have a refrange as well --> </ component > </Observation >
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
R6
hl7.fhir.core#6.0.0-ballot3
generated
on
Sun,
Mar
26,
2023
15:25+1100.
Sat,
Nov
8,
2025
03:18+0000.
Links:
Search
|
Version
History
|
Contents
|
Glossary
|
QA
|
Compare
to
R4
|
Compare
to
R4B
R5
|
Compare
to
Last
Ballot
|
|
Propose
a
change