FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

Orders and Observations icon Work Group  Maturity Level: 4 Trial Use Use Context: Any

The canonical URL for this profile is:

http://hl7.org/fhir/StructureDefinition/vitalsigns

FHIR Vital Signs Base Profile

This profile was published on Sat, Aug 11, 2018 00:00+0000 as a draft by HL7 International / Orders and Observations.

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Observation.

Summary

  1. One status in Observation.status which has a required binding to:

  2. A category in Observation.category which must have:

    • a fixed Observation.category.coding.system="http://terminology.hl7.org/CodeSystem/observation-category"
    • a fixed Observation.category.coding.code= "vital-signs"
  3. A code in Observation.code

    • a fixed Observation.code.coding.system= "http://loinc.org""
    • a LOINC code in Observation.code.coding.code which has an extensible binding to:
  4. One patient in Observation.subject

  5. A date and time in effectiveDateTime or effectivePeriod

  6. Either one Observation.value[x] or a populated component (with component.code and either component.value[x] or component.dataAbsentReason) or hasMember relationship. If there are none of those, then one code in Observation.DataAbsentReason

    • if a vital sign measure then:
      • One numeric value in Observation.valueQuantity.value
      • a fixed Observation.valueQuantity.system="http://unitsofmeasure.org"
      • a UCUM unit code in Observation.valueQuantity.code which has a required binding to the Vital Signs Units value set.
    • Observation.DataAbsentReason is bound to Observation Value Absent Reason value set.
  7. When using a panel code to group component observations (Note: See the comments regarding blood pressure in the table above), one or more Observation.component.code each of which must have:

    • a fixed Observation.component.code.coding.system =""http://loinc.org""
  8. Either one Observation.component.valueQuantity or, if there is no value, one code in Observation.component.DataAbsentReason

  9. When using a panel code to group observations, one or more reference to Vitals Signs Observations in Observation.related.target

    • a fixed Observation.related.type= "has-member""

Mandatory: 5 elements
Must-Support: 6 elements

Slices

This structure defines the following Slices:

  • The element Observation.category is sliced based on the value of pattern:$this

 

Alternate definitions: Master Definition (XML, JSON), Schematron

Path Name Conformance ValueSet
Observation.language All Languages required All Languages
Observation.triggeredBy.type triggered Bytype required triggered Bytype
Observation.status Observation Status required Observation Status
Observation.category Observation Category Codes preferred Observation Category Codes
Observation.category Observation Category Codes preferred Observation Category Codes
Observation.code Vital Signs Measurement preferred Vital Signs Measurement
Observation.value[x] Vital Signs Units preferred Vital Signs Units
Observation.dataAbsentReason Data Absent Reason extensible Data Absent Reason
Observation.interpretation Observation Interpretation Codes extensible Observation Interpretation Codes
Observation.bodySite SNOMED CT Body Structures example SNOMED CT Body Structures
Observation.method Observation Methods example Observation Methods
Observation.referenceRange.normalValue Observation Reference Range Normal Value Codes extensible Observation Reference Range Normal Value Codes
Observation.referenceRange.type Observation Reference Range Meaning Codes preferred Observation Reference Range Meaning Codes
Observation.referenceRange.appliesTo Observation Reference Range Applies To Codes example Observation Reference Range Applies To Codes
Observation.component.code LOINC Codes example LOINC Codes
Observation.component.value[x] ?ext preferred http://unitsofmeasure.org/vs icon
Observation.component.dataAbsentReason Data Absent Reason extensible Data Absent Reason
Observation.component.interpretation Observation Interpretation Codes extensible Observation Interpretation Codes
RuleRule
Id Path Details Requirements
vsp-1 Observation if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
Expression icon: (effective as dateTime).toString().length() >= 8
vsp-2 Observation If there is no component or hasMember element then either a value[x] or a data absent reason must be present.
Expression icon: (component.empty() and hasMember.empty()) implies (dataAbsentReason.exists() or value.exists())
. .