Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry vs http://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-apgar-score

Left:US Core Pulse Oximetry Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry)
Right:Observation - APGAR Score (http://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-apgar-score)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry' vs 'http://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-apgar-score'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCorePulseOximetryProfile' vs 'ObservationApgarScore'
InformationStructureDefinition.titleValues for title differ: 'US Core Pulse Oximetry Profile' vs 'Observation - APGAR Score'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-10-15T15:43:14+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Public Health'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey'
InformationStructureDefinition.shortValues for short differ: 'US Core Pulse Oximetry Profile' vs 'Survey Observation'
InformationStructureDefinition.definitionValues for definition differ: 'The FHIR Vitals Signs profile sets minimum expectations for the Observation Resource to record, search and fetch the vital signs associated with a patient.' vs '\-'
InformationStructureDefinition.commentValues for comment differ: 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.' vs '\-'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.commentValues for comment differ: 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below for guidance on referencing another Observation.' vs 'To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below for guidance on referencing another Observation.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that observation is derived from a questionnaire.'
InformationStructureDefinition.shortValues for short differ: 'Oxygen Saturation by Pulse Oximetry' vs 'Standard timings for APGAR assessments. Birth certificates only require 5 and 10 minute timings. Other use cases may require/accept other timings.'
InformationStructureDefinition.definitionValues for definition differ: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
InformationStructureDefinition.commentValues for comment differ: 'The code (59408-5 Oxygen saturation in Arterial blood by Pulse oximetry) is included as an additional observation code to FHIR Core vital Oxygen Saturation code (2708-6 Oxygen saturation in Arterial blood).' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.'
InformationStructureDefinition.requirementsValues for requirements differ: '5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).' vs 'Knowing what kind of observation is being made is essential to understanding the observation.'
InformationStructureDefinition.commentValues for comment differ: 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/extension-observation-focuscode.html).' vs 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., 'Blood Glucose') and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode](http://hl7.org/fhir/R4/extension-observation-focuscode.html).'
InformationStructureDefinition.shortValues for short differ: 'Often just a dateTime for Vital Signs' vs 'Clinically relevant time/time-period for observation'
InformationStructureDefinition.definitionValues for definition differ: 'Often just a dateTime for Vital Signs.' vs 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the 'physiologically relevant time'.'
InformationStructureDefinition.commentValues for comment differ: 'At least a date should be present unless this observation is a historical report. For recording imprecise or 'fuzzy' times (For example, a blood glucose measurement taken 'after breakfast') use the [Timing](http://hl7.org/fhir/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.' vs 'At least a date should be present unless this observation is a historical report.'
InformationObservation.effective[x]Element minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.commentValues for comment differ: 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.' vs 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/R4/resource-definitions.html#Meta.lastUpdated) time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.'
WarningObservation.performerElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Vital Signs Value' vs 'Actual result'
InformationStructureDefinition.definitionValues for definition differ: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
InformationStructureDefinition.commentValues for comment differ: 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.' vs 'An observation may have a value if it represents an individual survey question and answer pair. An observation should not have a value if it represents a multi-question survey or multi-select “check all that apply” question. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.'
InformationStructureDefinition.requirementsValues for requirements differ: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
InformationObservation.value[x]Element minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.commentValues for comment differ: 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be 'detected', 'not detected', 'inconclusive', or 'specimen unsatisfactory'. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code 'error' could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' vs ''Null' or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.'
InformationStructureDefinition.commentValues for comment differ: 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/extension-bodysite.html).' vs 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component. If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite](http://hl7.org/fhir/R4/extension-bodysite.html).'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Used when reporting vital signs panel components' vs 'Reference to panel or multi-select responses'
InformationStructureDefinition.definitionValues for definition differ: 'Used when reporting vital signs panel components.' vs 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.'
InformationStructureDefinition.commentValues for comment differ: 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/questionnaireresponse.html) into a final score and represent the score as an Observation.' vs 'This grouping element is used to represent surveys that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the 'panel' observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. In a survey that has a heirarchical grouping of questions, the observation 'panels' can be nested. Because surveys can be arbitrarily complex structurally, not all survey structures can be represented using this Observation grouping pattern.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'false' vs 'true'
ErrorObservation.hasMemberType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
InformationStructureDefinition.shortValues for short differ: 'Related measurements the observation is made from' vs 'Related Observations or QuestionnaireResponses that the observation is made from'
InformationStructureDefinition.definitionValues for definition differ: 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.' vs 'Observations or QuestionnaireResponses from which this observation value is derived.'
InformationStructureDefinition.commentValues for comment differ: 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/observation.html#obsgrouping) below.' vs 'All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'false' vs 'true'
ErrorObservation.derivedFromType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
InformationStructureDefinition.shortValues for short differ: 'Used when reporting flow rates or oxygen concentration.' vs 'Component results'
InformationStructureDefinition.definitionValues for definition differ: 'Used when reporting flow rates or oxygen concentration.' vs 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.'
InformationStructureDefinition.commentValues for comment differ: 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/observation.html#notes) below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/R4/observation.html#notes) below.'
WarningObservation.componentElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.requirementsValues for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).'
InformationStructureDefinition.shortValues for short differ: 'Coded vital sign result type' vs 'Type of component observation (code / type)'
WarningObservation.component.codeElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: 'Vital Sign Component Value' vs 'Actual component result'
InformationStructureDefinition.definitionValues for definition differ: 'Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
InformationStructureDefinition.commentValues for comment differ: 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/observation.html#notes) below.' vs 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/R4/observation.html#notes) below.'
InformationStructureDefinition.requirementsValues for requirements differ: '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signshttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey
    • Values Differ
    .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
    • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
    .date2023-10-172024-10-15T15:43:14+00:00
    • Values Differ
    .descriptionThe US Core Pulse Oximetry Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and pulse oximetry and inspired oxygen observations with standard LOINC codes and UCUM units of measure. It specifies which *additional* core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.APGAR score post-birth.
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
          .kindresource
            .nameUSCorePulseOximetryProfileObservationApgarScore
            • Values Differ
            .publisherHL7 International / Cross-Group ProjectsHL7 International / Public Health
            • Values Differ
            .purpose
              .statusactive
                .titleUS Core Pulse Oximetry ProfileObservation - APGAR Score
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetryhttp://hl7.org/fhir/us/bfdr/StructureDefinition/Observation-apgar-score
                  • Values Differ
                  .version7.0.02.0.0
                  • Values Differ

                  Structure

                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                  .. Observation C0..*USCoreVitalSignsProfileUS Core Pulse Oximetry 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.
                  C0..*USCoreObservationSurveyProfileSurvey Observation
                  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
                  us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                  us-core-3: SHALL use UCUM for coded quantity units.
                    ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                      ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                        ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                          ... language 0..1codeLanguage of the resource content
                          Binding: ?? (preferred): A human language.

                          Additional BindingsPurpose
                          ??Max Binding
                          0..1codeLanguage of the resource content
                          Binding: ?? (preferred): A human language.

                          Additional BindingsPurpose
                          ??Max Binding
                            ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                              ... contained 0..*ResourceContained, inline Resources
                              0..*ResourceContained, inline Resources
                                ... extension 0..*ExtensionAdditional content defined by implementations
                                0..*ExtensionAdditional content defined by implementations
                                  ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                  ?!0..*ExtensionExtensions that cannot be ignored
                                    ... identifier Σ0..*IdentifierBusiness Identifier for observation
                                    Σ0..*IdentifierBusiness Identifier for observation
                                      ... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                      Σ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
                                        Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                          ... status ?!SΣ1..1coderegistered | preliminary | final | amended +
                                          Binding: ?? (required)
                                          ?!SΣ1..1coderegistered | preliminary | final | amended +
                                          Binding: ?? (required): Codes providing the status of an observation.

                                            ... Slices for category S1..*CodeableConceptClassification of type of observation
                                            Slice: Unordered, Open by value:coding.code, value:coding.system
                                            Binding: ?? (preferred): Codes for high level observation categories.


                                            S1..*CodeableConceptClassification of type of observation
                                            Slice: Unordered, Open by pattern:$this
                                            Binding: ?? (preferred): Codes for high level observation categories.


                                              ... code SΣ1..1CodeableConceptOxygen Saturation by Pulse Oximetry
                                              Binding: ?? (extensible): Vital sign result types

                                              SΣ1..1CodeableConceptStandard timings for APGAR assessments. Birth certificates only require 5 and 10 minute timings. Other use cases may require/accept other timings.
                                              Binding: ?? (required): ApgarTiming

                                                .... id 0..1stringUnique id for inter-element referencing
                                                • Removed this element
                                                .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                Slice: Unordered, Open by value:url
                                                • Removed this element
                                                .... Slices for coding SΣ2..*CodingCode defined by a terminology system
                                                Slice: Unordered, Open by pattern:$this
                                                • Removed this element
                                                .... text Σ0..1stringPlain text representation of the concept
                                                • Removed this element
                                                ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(Patient - Child Vital Records)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
                                                  Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                                    ... encounter Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                                      ... effective[x] SΣC1..1dateTime S, PeriodOften 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
                                                      SΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                                      us-core-1: Datetime must be at least to day.
                                                      • Element minimum cardinalities differ: '1' vs '0'
                                                      ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                                        ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                        SΣ0..*Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core RelatedPerson Profile)Who is responsible for the observation
                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                        ... Slices for value[x] SΣC0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Signs Value
                                                        Slice: Unordered, Open by type:$this
                                                        Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                                        SΣC1..1integerActual result
                                                        • Element minimum cardinalities differ: '0' vs '1'
                                                        ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                        Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                        SC0..1CodeableConceptWhy the result is missing
                                                        Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

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


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


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

                                                              0..1CodeableConceptObserved body part
                                                              Binding: ?? (example): Codes describing anatomical locations. May include laterality.

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

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

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

                                                                                  0..1CodeableConceptReference range qualifier
                                                                                  Binding: ?? (preferred): Code for the meaning of a reference range.

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


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


                                                                                      .... age 0..1RangeApplicable age range, if relevant0..1RangeApplicable age range, if relevant
                                                                                        .... text 0..1stringText based reference range in an observation0..1stringText based reference range in an observation
                                                                                          ... hasMember Σ0..*Reference(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Used when reporting vital signs panel components
                                                                                          SΣ0..*Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile | MolecularSequence)Reference to panel or multi-select responses
                                                                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                          • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
                                                                                          ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Related measurements the observation is made from
                                                                                          SΣ0..*Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile S | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence)Related Observations or QuestionnaireResponses that the observation is made from
                                                                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                          • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
                                                                                          ... Slices for component SΣC0..*BackboneElementUsed when reporting flow rates or oxygen concentration.
                                                                                          Slice: Unordered, Open by pattern:code
                                                                                          vs-3: If there is no a value a data absent reason must be present
                                                                                          Σ0..*BackboneElementComponent results
                                                                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                            .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                            0..*ExtensionAdditional content defined by implementations
                                                                                              .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                              ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                .... code SΣ1..1CodeableConceptCoded vital sign result type
                                                                                                Binding: ?? (extensible): Vital sign result types

                                                                                                Σ1..1CodeableConceptType of component observation (code / type)
                                                                                                Binding: ?? (example): Codes identifying names of simple observations.

                                                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                                .... value[x] SΣC0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Sign Component Value
                                                                                                Binding: ?? (extensible): Common UCUM units for recording Vital Signs.

                                                                                                Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                                .... dataAbsentReason SC0..1CodeableConceptWhy the component result is missing
                                                                                                Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                                                C0..1CodeableConceptWhy the component result is missing
                                                                                                Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                                .... interpretation 0..*CodeableConceptHigh, low, normal, etc.
                                                                                                Binding: ?? (extensible): Codes identifying interpretations of observations.


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


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

                                                                                                    doco Documentation for this format