| Name | Flags | Card. | Type |
Description & Constraints
|
|---|---|---|---|---|
Observation
|
C | nl-core-observation |
FHIR Vital Signs Profile vs-2: If there is no component or related element then either a value[x] or a data absent reason must be present |
|
related
|
S | Used when reporting vital signs panel components | ||
target
|
S | Reference (VitalSigns Profile NL) | ||
type
|
S | 1.. | Fixed Value: has-member | |
|
status
|
S | |||
|
category
|
S C | 1.. | vs-4: Must have a category of 'vital-signs' and a code system 'http://hl7.org/fhir/observation-category' | |
|
code
|
S |
Coded Responses from Vital Signs Results Binding: Vital Signs ( extensible ): This identifies the vital sign result type. |
||
|
subject
|
S | Reference (nl-core-patient) | ||
|
effective[x]
|
S | 1.. | Often just a dateTime for Vital Signs | |
|
performer
|
S | |||
valueQuantity:valueQuantity
|
S C | Quantity |
Vital Sign Value recorded with UCUM Binding: Vital Signs Units ( required ): Common UCUM units for recording Vital Signs |
|
value
|
S | 1.. | ||
|
unit
|
S | 1.. | ||
|
system
|
S | 1.. | Fixed Value: http://unitsofmeasure.org | |
code
|
S | 1.. | Coded responses from the common UCUM units for vital signs value set. | |
|
dataAbsentReason
|
S C | |||
|
device
|
Reference (HCIM MedicalDevice Product) | |||
|
component
|
S C | vs-3: If there is no a value a data absent reason must be present | ||
code
|
S |
Binding:
Vital Signs
( extensible
): This identifies the vital sign result type. |
||
|
value[x]
|
S C | Vital Sign Value recorded with UCUM | ||
|
dataAbsentReason
|
S C | |||
|
Documentation for this format
|
||||