Termini

CodeSystemsConceptSystemsStructureDefinitionsValueSetsPackagesConflicts
StructureDefinitionsobservation-vitalsigns

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

FHIR Vital Signs Profile
StructureJSONDependenciesFHIRSchemaOther VersionsDependant (0)ElementsSummary
NameFlagsCardTypeDescription & Constraints
Observation
0..*FHIR Vital Signs Profile
 
status *
s
1..1code Status (required)
 
category *
s
1..*CodeableConcept
 
category *
s
1..1CodeableConcept
 
 
coding *
s
1..*Coding
 
 
 
system *
s
1..1uri
 
 
 
code *
s
1..1code
 
code *
s
1..1CodeableConceptCoded Responses from C-CDA Vital Sign Results VitalSigns (extensible)
 
subject *
s
1..1Reference
 
effective[x] *
s
1..1Often just a dateTime for Vital Signs
 
 
effectiveDateTime *
s
1..1dateTime
 
 
effectivePeriod *
s
1..1Period
 
value[x]
s
0..1Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
 
dataAbsentReason
s
0..1CodeableConcept
 
hasMember
?..?ReferenceUsed when reporting vital signs panel components
 
derivedFrom
?..?Reference
 
component
s
?..?Used when reporting systolic and diastolic blood pressure.
 
 
code *
s
1..1CodeableConcept VitalSigns (extensible)
 
 
value[x]
s
0..1Vital Sign Value recorded with UCUM VitalSignsUnits (required)
 
 
dataAbsentReason
s
0..1CodeableConcept