MediRecords FHIR Implementation Guide
1.4.1 - release


Resource Profile: MR Observation Vital Sign Heart Rate

Defining URL:https://fhir.medirecords.com/StructureDefinition/mr-observation-vitalsign-heartrate
Version:1.4.1
Name:MRObservationVitalSignHeartRate
Title:MR Observation Vital Sign Heart Rate
Status:Active as of 2024-10-28 02:34:31+0000
Definition:

MediRecords Vital Sign profile to record the heart rate of the patient in context

Source Resource:XML / JSON / Turtle

The official URL for this profile is: 

https://fhir.medirecords.com/StructureDefinition/mr-observation-vitalsign-heartrate

Formal Views of Profile Content

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

This structure is derived from MRObservationVitalSigns

Summary

Mandatory: 13 elements (6 nested mandatory elements)
Must-Support: 11 elements
Fixed Value: 9 elements

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element Observation.code.coding is sliced based on the values of value:code, value:system
  • The element Observation.value[x] is sliced based on the value of type:$this
  • The element Observation.component.code.coding is sliced based on the values of value:code, value:system
  • The element Observation.component.value[x] is sliced based on the value of type:$this

This structure is derived from MRObservationVitalSigns

NameFlagsCard.TypeDescription & Constraintsdoco
​.. Observation 0..*MRObservationVitalSignsFHIR Heart Rate Profile
​... meta
​.... lastUpdated S0..1instantWhen the resource version last changed
​.... profile 1..*canonical(StructureDefinition)Profiles this resource claims to conform to
​... status C1..1codeMediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
inv-mr-obs-vitalsign-status-01: MediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
​... code 1..1CodeableConceptHeart Rate
​.... Slices for coding S2..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
​..... coding:HeartRateCode 1..1CodingCode defined by a terminology system
​...... system 1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
​...... code 1..1codeSymbol in syntax defined by the system
Fixed Value: 8867-4
​..... coding:heartRateSNOMED-CT S1..1CodingCode defined by a terminology system
​...... system 1..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct
​...... code 1..1codeSymbol in syntax defined by the system
Fixed Value: 364075005
​... encounter S0..1Reference(MR Encounter)Healthcare event during which this observation is made
​... effectiveDateTime S1..1dateTimeOften just a dateTime for Vital Signs
​... performer S0..1Reference(MR Practitioner)Who is responsible for the observation
​... value[x] 1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
Slice: Unordered, Open by type:$this
​... valueQuantity 1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
​.... value SC1..1decimalNumerical value (with implicit precision)
inv-mr-obs-vitalsign-valueQuantity-value-03: Value must conform to format: nnn - maximum 3 digits and no decimal
​.... unit S1..1stringUnit representation
Fixed Value: /min
​.... system S1..1uriSystem that defines coded unit form
Fixed Value: http://unitsofmeasure.org
​.... code S1..1codeCoded responses from the common UCUM units for vital signs value set.
Fixed Value: /min
​... component 0..1BackboneElementUsed when reporting heart rate rhythm.
​.... code
​..... Slices for coding 1..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
​...... coding:heartRateRhythm-CT S1..1CodingCode defined by a terminology system
​....... code 1..1codeSymbol in syntax defined by the system
Fixed Value: 301112006
​.... value[x] 1..1CodeableConceptVital Sign Value recorded with UCUM
Slice: Unordered, Open by type:$this
​.... valueCodeableConcept 1..1CodeableConceptVital Sign Value recorded with UCUM
Binding: MediRecords Heart Rate Rhythm ValueSet (required)
​..... coding
​...... system 0..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation C0..*MRObservationVitalSignsFHIR Heart Rate Profile
obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
vs-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present.
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... versionId Σ0..1idVersion specific identifier
.... lastUpdated SΣ0..1instantWhen the resource version last changed
.... source Σ0..1uriIdentifies where the resource comes from
.... profile Σ1..*canonical(StructureDefinition)Profiles this resource claims to conform to
.... security Σ0..*CodingSecurity Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


.... tag Σ0..*CodingTags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifier for observation
... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
... status ?!SΣC1..1codeMediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
Binding: ObservationStatus (required)
inv-mr-obs-vitalsign-status-01: MediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
... Slices for category S1..*CodeableConceptClassification of type of observation
Slice: Unordered, Open by value:coding.code, value:coding.system
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


.... category:VSCat S1..1CodeableConceptClassification of type of observation
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... coding SΣ1..*CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system SΣ1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/observation-category
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
Fixed Value: vital-signs
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
... code SΣ1..1CodeableConceptHeart Rate
Binding: VitalSigns (extensible): This identifies the vital sign result type.

.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... Slices for coding SΣ2..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
..... coding:HeartRateCode Σ1..1CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
...... version Σ0..1stringVersion of the system - if relevant
...... code Σ1..1codeSymbol in syntax defined by the system
Fixed Value: 8867-4
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... coding:heartRateSNOMED-CT SΣ1..1CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ1..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct
...... version Σ0..1stringVersion of the system - if relevant
...... code Σ1..1codeSymbol in syntax defined by the system
Fixed Value: 364075005
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... subject SΣ1..1Reference(MR Patient)Who and/or what the observation is about
... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
... encounter SΣ0..1Reference(MR Encounter)Healthcare event during which this observation is made
... Slices for effective[x] SΣC1..1dateTimeOften just a dateTime for Vital Signs
Slice: Unordered, Closed by type:$this
vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
.... effective[x]:effectiveDateTime SΣC1..1dateTimeOften just a dateTime for Vital Signs
vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
... issued Σ0..1instantDate/Time this version was made available
... performer SΣ0..1Reference(MR Practitioner)Who is responsible for the observation
... Slices for value[x] SΣC1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
Slice: Unordered, Closed by type:$this
.... value[x]:valueQuantity SΣC1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... value SΣC1..1decimalNumerical value (with implicit precision)
inv-mr-obs-vitalsign-valueQuantity-value-03: Value must conform to format: nnn - maximum 3 digits and no decimal
..... comparator ?!Σ0..1code< | <= | >= | > - how to understand the value
Binding: QuantityComparator (required): How the Quantity should be understood and represented.

..... unit SΣ1..1stringUnit representation
Fixed Value: /min
..... system SΣC1..1uriSystem that defines coded unit form
Fixed Value: http://unitsofmeasure.org
..... code SΣ1..1codeCoded responses from the common UCUM units for vital signs value set.
Fixed Value: /min
... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

... interpretation 0..*CodeableConceptHigh, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


... note 0..*AnnotationComments about the observation
... bodySite 0..1CodeableConceptObserved body part
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

... method 0..1CodeableConceptHow it was done
Binding: ObservationMethods (example): Methods for simple observations.

... specimen 0..1Reference(Specimen)Specimen used for this observation
... device 0..1Reference(Device | DeviceMetric)(Measurement) Device
... referenceRange C0..*BackboneElementProvides guide for interpretation
obs-3: Must have at least a low or a high or text
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... low C0..1SimpleQuantityLow Range, if relevant
.... high C0..1SimpleQuantityHigh Range, if relevant
.... type 0..1CodeableConceptReference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

.... appliesTo 0..*CodeableConceptReference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.


.... age 0..1RangeApplicable age range, if relevant
.... text 0..1stringText based reference range in an observation
... hasMember Σ0..*Reference(QuestionnaireResponse | MolecularSequence | MR Observation Vital Signs)Used when reporting vital signs panel components
... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | MR Observation Vital Signs)Related measurements the observation is made from
... component SΣC0..1BackboneElementUsed when reporting heart rate rhythm.
vs-3: If there is no a value a data absent reason must be present
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code SΣ1..1CodeableConceptType of component observation (code / type)
Binding: VitalSigns (extensible): This identifies the vital sign result type.

..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... Slices for coding Σ1..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
...... coding:heartRateRhythm-CT SΣ1..1CodingCode defined by a terminology system
....... id 0..1stringUnique id for inter-element referencing
....... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
....... system Σ0..1uriIdentity of the terminology system
....... version Σ0..1stringVersion of the system - if relevant
....... code Σ1..1codeSymbol in syntax defined by the system
Fixed Value: 301112006
....... display Σ0..1stringRepresentation defined by the system
....... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
.... Slices for value[x] SΣC1..1CodeableConceptVital Sign Value recorded with UCUM
Slice: Unordered, Closed by type:$this
..... value[x]:valueCodeableConcept SΣC1..1CodeableConceptVital Sign Value recorded with UCUM
Binding: MediRecords Heart Rate Rhythm ValueSet (required)
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... coding Σ0..*CodingCode defined by a terminology system
....... id 0..1stringUnique id for inter-element referencing
....... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
....... system Σ0..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct
....... version Σ0..1stringVersion of the system - if relevant
....... code Σ0..1codeSymbol in syntax defined by the system
....... display Σ0..1stringRepresentation defined by the system
....... userSelected Σ0..1booleanIf this coding was chosen directly by the user
...... text Σ0..1stringPlain text representation of the concept
.... dataAbsentReason SC0..1CodeableConceptWhy the component result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

.... interpretation 0..*CodeableConceptHigh, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


.... referenceRange 0..*See referenceRange (Observation)Provides guide for interpretation of component result

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
​.. Observation 0..*MRObservationVitalSignsFHIR Heart Rate Profile
​... meta Σ0..1MetaMetadata about the resource
​.... lastUpdated Σ0..1instantWhen the resource version last changed
​... status ?!ΣC1..1codeMediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
Binding: ObservationStatus (required)
inv-mr-obs-vitalsign-status-01: MediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
​... Slices for category 1..*CodeableConceptClassification of type of observation
Slice: Unordered, Open by value:coding.code, value:coding.system
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


​.... category:VSCat 1..1CodeableConceptClassification of type of observation
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


​..... coding Σ1..*CodingCode defined by a terminology system
​...... system Σ1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/observation-category
​...... code Σ1..1codeSymbol in syntax defined by the system
Fixed Value: vital-signs
​.... Slices for coding Σ2..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
​..... coding:heartRateSNOMED-CT Σ1..1CodingCode defined by a terminology system
​... subject Σ1..1Reference(MR Patient)Who and/or what the observation is about
​... encounter Σ0..1Reference(MR Encounter)Healthcare event during which this observation is made
​... Slices for effective[x] ΣC1..1dateTimeOften just a dateTime for Vital Signs
Slice: Unordered, Closed by type:$this
vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
​.... effective[x]:effectiveDateTime ΣC1..1dateTimeOften just a dateTime for Vital Signs
vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
​... performer Σ0..1Reference(MR Practitioner)Who is responsible for the observation
​... Slices for value[x] ΣC1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
Slice: Unordered, Closed by type:$this
​.... value[x]:valueQuantity ΣC1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
​..... value ΣC1..1decimalNumerical value (with implicit precision)
inv-mr-obs-vitalsign-valueQuantity-value-03: Value must conform to format: nnn - maximum 3 digits and no decimal
​..... unit Σ1..1stringUnit representation
Fixed Value: /min
​..... system ΣC1..1uriSystem that defines coded unit form
Fixed Value: http://unitsofmeasure.org
​..... code Σ1..1codeCoded responses from the common UCUM units for vital signs value set.
Fixed Value: /min
​... dataAbsentReason C0..1CodeableConceptWhy the result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

​... component ΣC0..1BackboneElementUsed when reporting heart rate rhythm.
vs-3: If there is no a value a data absent reason must be present
​.... code Σ1..1CodeableConceptType of component observation (code / type)
Binding: VitalSigns (extensible): This identifies the vital sign result type.

​..... coding:heartRateRhythm-CT Σ1..1CodingCode defined by a terminology system
​.... Slices for value[x] ΣC1..1CodeableConceptVital Sign Value recorded with UCUM
Slice: Unordered, Closed by type:$this
​..... value[x]:valueCodeableConcept ΣC1..1CodeableConceptVital Sign Value recorded with UCUM
Binding: MediRecords Heart Rate Rhythm ValueSet (required)
​.... dataAbsentReason C0..1CodeableConceptWhy the component result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.


doco Documentation for this format

This structure is derived from MRObservationVitalSigns

Summary

Mandatory: 13 elements (6 nested mandatory elements)
Must-Support: 11 elements
Fixed Value: 9 elements

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element Observation.code.coding is sliced based on the values of value:code, value:system
  • The element Observation.value[x] is sliced based on the value of type:$this
  • The element Observation.component.code.coding is sliced based on the values of value:code, value:system
  • The element Observation.component.value[x] is sliced based on the value of type:$this

Differential View

This structure is derived from MRObservationVitalSigns

NameFlagsCard.TypeDescription & Constraintsdoco
​.. Observation 0..*MRObservationVitalSignsFHIR Heart Rate Profile
​... meta
​.... lastUpdated S0..1instantWhen the resource version last changed
​.... profile 1..*canonical(StructureDefinition)Profiles this resource claims to conform to
​... status C1..1codeMediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
inv-mr-obs-vitalsign-status-01: MediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
​... code 1..1CodeableConceptHeart Rate
​.... Slices for coding S2..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
​..... coding:HeartRateCode 1..1CodingCode defined by a terminology system
​...... system 1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
​...... code 1..1codeSymbol in syntax defined by the system
Fixed Value: 8867-4
​..... coding:heartRateSNOMED-CT S1..1CodingCode defined by a terminology system
​...... system 1..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct
​...... code 1..1codeSymbol in syntax defined by the system
Fixed Value: 364075005
​... encounter S0..1Reference(MR Encounter)Healthcare event during which this observation is made
​... effectiveDateTime S1..1dateTimeOften just a dateTime for Vital Signs
​... performer S0..1Reference(MR Practitioner)Who is responsible for the observation
​... value[x] 1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
Slice: Unordered, Open by type:$this
​... valueQuantity 1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
​.... value SC1..1decimalNumerical value (with implicit precision)
inv-mr-obs-vitalsign-valueQuantity-value-03: Value must conform to format: nnn - maximum 3 digits and no decimal
​.... unit S1..1stringUnit representation
Fixed Value: /min
​.... system S1..1uriSystem that defines coded unit form
Fixed Value: http://unitsofmeasure.org
​.... code S1..1codeCoded responses from the common UCUM units for vital signs value set.
Fixed Value: /min
​... component 0..1BackboneElementUsed when reporting heart rate rhythm.
​.... code
​..... Slices for coding 1..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
​...... coding:heartRateRhythm-CT S1..1CodingCode defined by a terminology system
​....... code 1..1codeSymbol in syntax defined by the system
Fixed Value: 301112006
​.... value[x] 1..1CodeableConceptVital Sign Value recorded with UCUM
Slice: Unordered, Open by type:$this
​.... valueCodeableConcept 1..1CodeableConceptVital Sign Value recorded with UCUM
Binding: MediRecords Heart Rate Rhythm ValueSet (required)
​..... coding
​...... system 0..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation C0..*MRObservationVitalSignsFHIR Heart Rate Profile
obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
vs-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present.
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... versionId Σ0..1idVersion specific identifier
.... lastUpdated SΣ0..1instantWhen the resource version last changed
.... source Σ0..1uriIdentifies where the resource comes from
.... profile Σ1..*canonical(StructureDefinition)Profiles this resource claims to conform to
.... security Σ0..*CodingSecurity Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


.... tag Σ0..*CodingTags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierBusiness Identifier for observation
... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
... status ?!SΣC1..1codeMediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
Binding: ObservationStatus (required)
inv-mr-obs-vitalsign-status-01: MediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
... Slices for category S1..*CodeableConceptClassification of type of observation
Slice: Unordered, Open by value:coding.code, value:coding.system
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


.... category:VSCat S1..1CodeableConceptClassification of type of observation
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... coding SΣ1..*CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system SΣ1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/observation-category
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeSymbol in syntax defined by the system
Fixed Value: vital-signs
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
... code SΣ1..1CodeableConceptHeart Rate
Binding: VitalSigns (extensible): This identifies the vital sign result type.

.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... Slices for coding SΣ2..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
..... coding:HeartRateCode Σ1..1CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ1..1uriIdentity of the terminology system
Fixed Value: http://loinc.org
...... version Σ0..1stringVersion of the system - if relevant
...... code Σ1..1codeSymbol in syntax defined by the system
Fixed Value: 8867-4
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... coding:heartRateSNOMED-CT SΣ1..1CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ1..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct
...... version Σ0..1stringVersion of the system - if relevant
...... code Σ1..1codeSymbol in syntax defined by the system
Fixed Value: 364075005
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... subject SΣ1..1Reference(MR Patient)Who and/or what the observation is about
... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
... encounter SΣ0..1Reference(MR Encounter)Healthcare event during which this observation is made
... Slices for effective[x] SΣC1..1dateTimeOften just a dateTime for Vital Signs
Slice: Unordered, Closed by type:$this
vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
.... effective[x]:effectiveDateTime SΣC1..1dateTimeOften just a dateTime for Vital Signs
vs-1: if Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
... issued Σ0..1instantDate/Time this version was made available
... performer SΣ0..1Reference(MR Practitioner)Who is responsible for the observation
... Slices for value[x] SΣC1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
Slice: Unordered, Closed by type:$this
.... value[x]:valueQuantity SΣC1..1QuantityVital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... value SΣC1..1decimalNumerical value (with implicit precision)
inv-mr-obs-vitalsign-valueQuantity-value-03: Value must conform to format: nnn - maximum 3 digits and no decimal
..... comparator ?!Σ0..1code< | <= | >= | > - how to understand the value
Binding: QuantityComparator (required): How the Quantity should be understood and represented.

..... unit SΣ1..1stringUnit representation
Fixed Value: /min
..... system SΣC1..1uriSystem that defines coded unit form
Fixed Value: http://unitsofmeasure.org
..... code SΣ1..1codeCoded responses from the common UCUM units for vital signs value set.
Fixed Value: /min
... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

... interpretation 0..*CodeableConceptHigh, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


... note 0..*AnnotationComments about the observation
... bodySite 0..1CodeableConceptObserved body part
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

... method 0..1CodeableConceptHow it was done
Binding: ObservationMethods (example): Methods for simple observations.

... specimen 0..1Reference(Specimen)Specimen used for this observation
... device 0..1Reference(Device | DeviceMetric)(Measurement) Device
... referenceRange C0..*BackboneElementProvides guide for interpretation
obs-3: Must have at least a low or a high or text
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... low C0..1SimpleQuantityLow Range, if relevant
.... high C0..1SimpleQuantityHigh Range, if relevant
.... type 0..1CodeableConceptReference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

.... appliesTo 0..*CodeableConceptReference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.


.... age 0..1RangeApplicable age range, if relevant
.... text 0..1stringText based reference range in an observation
... hasMember Σ0..*Reference(QuestionnaireResponse | MolecularSequence | MR Observation Vital Signs)Used when reporting vital signs panel components
... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | MR Observation Vital Signs)Related measurements the observation is made from
... component SΣC0..1BackboneElementUsed when reporting heart rate rhythm.
vs-3: If there is no a value a data absent reason must be present
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code SΣ1..1CodeableConceptType of component observation (code / type)
Binding: VitalSigns (extensible): This identifies the vital sign result type.

..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... Slices for coding Σ1..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:code, value:system
...... coding:heartRateRhythm-CT SΣ1..1CodingCode defined by a terminology system
....... id 0..1stringUnique id for inter-element referencing
....... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
....... system Σ0..1uriIdentity of the terminology system
....... version Σ0..1stringVersion of the system - if relevant
....... code Σ1..1codeSymbol in syntax defined by the system
Fixed Value: 301112006
....... display Σ0..1stringRepresentation defined by the system
....... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
.... Slices for value[x] SΣC1..1CodeableConceptVital Sign Value recorded with UCUM
Slice: Unordered, Closed by type:$this
..... value[x]:valueCodeableConcept SΣC1..1CodeableConceptVital Sign Value recorded with UCUM
Binding: MediRecords Heart Rate Rhythm ValueSet (required)
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... coding Σ0..*CodingCode defined by a terminology system
....... id 0..1stringUnique id for inter-element referencing
....... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
....... system Σ0..1uriIdentity of the terminology system
Fixed Value: http://snomed.info/sct
....... version Σ0..1stringVersion of the system - if relevant
....... code Σ0..1codeSymbol in syntax defined by the system
....... display Σ0..1stringRepresentation defined by the system
....... userSelected Σ0..1booleanIf this coding was chosen directly by the user
...... text Σ0..1stringPlain text representation of the concept
.... dataAbsentReason SC0..1CodeableConceptWhy the component result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

.... interpretation 0..*CodeableConceptHigh, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


.... referenceRange 0..*See referenceRange (Observation)Provides guide for interpretation of component result

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Terminology Bindings

PathConformanceValueSetURI
Observation.meta.securityextensibleAll Security Labels
http://hl7.org/fhir/ValueSet/security-labels
from the FHIR Standard
Observation.meta.tagexampleCommonTags
http://hl7.org/fhir/ValueSet/common-tags
from the FHIR Standard
Observation.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
http://hl7.org/fhir/ValueSet/languages
from the FHIR Standard
Observation.statusrequiredObservationStatus
http://hl7.org/fhir/ValueSet/observation-status|4.0.1
from the FHIR Standard
Observation.categorypreferredObservationCategoryCodes
http://hl7.org/fhir/ValueSet/observation-category
from the FHIR Standard
Observation.category:VSCatpreferredObservationCategoryCodes
http://hl7.org/fhir/ValueSet/observation-category
from the FHIR Standard
Observation.codeextensibleVitalSigns
http://hl7.org/fhir/ValueSet/observation-vitalsignresult
from the FHIR Standard
Observation.value[x]:valueQuantity.comparatorrequiredQuantityComparator
http://hl7.org/fhir/ValueSet/quantity-comparator|4.0.1
from the FHIR Standard
Observation.dataAbsentReasonextensibleDataAbsentReason
http://hl7.org/fhir/ValueSet/data-absent-reason
from the FHIR Standard
Observation.interpretationextensibleObservationInterpretationCodes
http://hl7.org/fhir/ValueSet/observation-interpretation
from the FHIR Standard
Observation.bodySiteexampleSNOMEDCTBodyStructures
http://hl7.org/fhir/ValueSet/body-site
from the FHIR Standard
Observation.methodexampleObservationMethods
http://hl7.org/fhir/ValueSet/observation-methods
from the FHIR Standard
Observation.referenceRange.typepreferredObservationReferenceRangeMeaningCodes
http://hl7.org/fhir/ValueSet/referencerange-meaning
from the FHIR Standard
Observation.referenceRange.appliesToexampleObservationReferenceRangeAppliesToCodes
http://hl7.org/fhir/ValueSet/referencerange-appliesto
from the FHIR Standard
Observation.component.codeextensibleVitalSigns
http://hl7.org/fhir/ValueSet/observation-vitalsignresult
from the FHIR Standard
Observation.component.value[x]:valueCodeableConceptrequiredMRHearRateRhythmValueSet
https://fhir.medirecords.com/ValueSet/mr-heart-rate-rhythm-code
from this IG
Observation.component.dataAbsentReasonextensibleDataAbsentReason
http://hl7.org/fhir/ValueSet/data-absent-reason
from the FHIR Standard
Observation.component.interpretationextensibleObservationInterpretationCodes
http://hl7.org/fhir/ValueSet/observation-interpretation
from the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorObservationIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorObservationIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorObservationIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorObservationIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceObservationA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
inv-mr-obs-vitalsign-status-01errorObservation.statusMediRecords supports only "final - 'The observation is complete and there are no further actions needed'” or “entered-in-error - 'The observation has been withdrawn following previous final release'
: $this.exists() implies ($this = 'final' or $this = 'entered-in-error')
inv-mr-obs-vitalsign-valueQuantity-value-03errorObservation.value[x]:valueQuantity.valueValue must conform to format: nnn - maximum 3 digits and no decimal
: ($this as decimal).toString().matches('^(\\d{1,3}|\\d{0,3})$')
obs-3errorObservation.referenceRangeMust have at least a low or a high or text
: low.exists() or high.exists() or text.exists()
obs-6errorObservationdataAbsentReason SHALL only be present if Observation.value[x] is not present
: dataAbsentReason.empty() or value.empty()
obs-7errorObservationIf Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
: value.empty() or component.code.where(coding.intersect(%resource.code.coding).exists()).empty()
vs-1errorObservation.effective[x], Observation.effective[x]:effectiveDateTimeif Observation.effective[x] is dateTime and has a value then that value shall be precise to the day
: ($this as dateTime).toString().length() >= 8
vs-2errorObservationIf there is no component or hasMember element then either a value[x] or a data absent reason must be present.
: (component.empty() and hasMember.empty()) implies (dataAbsentReason.exists() or value.exists())
vs-3errorObservation.componentIf there is no a value a data absent reason must be present
: value.exists() or dataAbsentReason.exists()