Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-height vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationAssessment

Left:US Core Body Height Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-height)
Right:SDOHCC Observation Assessment (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationAssessment)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-height' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationAssessment'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreBodyHeightProfile' vs 'SDOHCCObservationAssessment'
InformationStructureDefinition.titleValues for title differ: 'US Core Body Height Profile' vs 'SDOHCC Observation Assessment'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2022-11-21T18:34:14+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Patient Care WG'
WarningStructureDefinition.abstractValues for abstract differ: 'false' vs 'true'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs' vs 'http://hl7.org/fhir/StructureDefinition/Observation'
WarningObservationElements differ in short: 'US Core Body Height Profile' vs 'SDOH assessment observation'
WarningObservationElements differ in definition: '\-' vs 'For SDOH observations derived from assessment of the individual.'
WarningObservationElements differ in comments: '\-' vs 'For representation of SDOH observations that involve assessment (e.g., by a provider or payer) as opposed to being derived only from screening surveys (as is the case for the SDOHCC Screening Response Observation). Many of the SDOHCC profiles reference one another. One flow supported by this IG is that QuestionnaireResponses result in Observations that can be used as evidence for Conditions that can lead to Goals, ServiceRequests and Procedures. However, alternatives paths are also possible.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.codeElements differ in short: 'Body Height' vs 'Type of observation (code / type)'
WarningObservation.codeElements differ in definition: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
WarningObservation.codeElements differ in comments: '*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.' 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. As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set binding strength may change and may be refined to codes (including LOINC and SNOMED) that pertain to SDOH categories.'
WarningObservation.codeElements differ in requirements: '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.'
ErrorObservation.subjectType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Group], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]])
WarningObservation.effective[x]Elements differ in short: 'Often just a dateTime for Vital Signs' vs 'Clinically relevant time/time-period for observation'
WarningObservation.effective[x]Elements differ in definition: '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'. This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.'
WarningObservation.effective[x]Elements differ in comments: '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] 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. For recording imprecise or 'fuzzy' times (For example, a blood glucose measurement taken 'after breakfast') use the [Timing] datatype which allow the measurement to be tied to regular life events. NOTE: dateTime is Must Support, but currently tooling does not support this.'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.effective[x]Element minimum cardinalities differ: '1' vs '0'
WarningObservation.performerElements differ in definition for mustSupport: 'false' vs 'true'
ErrorObservation.performerType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam]])
WarningObservation.value[x]Elements differ in short: 'Vital Signs Value' vs 'Actual result'
WarningObservation.value[x]Elements differ in definition: '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.'
WarningObservation.value[x]Elements differ in requirements: '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.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.hasMemberElements differ in short: 'Used when reporting vital signs panel components' vs 'Related resource that belongs to the Observation group'
WarningObservation.hasMemberElements differ in definition: 'Used when reporting vital signs panel components.' vs 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.'
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/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
WarningObservation.componentElements differ in short: 'Component observations' vs 'Component results'
WarningObservation.componentElements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' 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.'
WarningObservation.componentElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.codeElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.codeElements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
WarningObservation.component.value[x]Elements differ in short: 'Vital Sign Component Value' vs 'Actual component result'
WarningObservation.component.value[x]Elements differ in definition: '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.'
WarningObservation.component.value[x]Elements differ in requirements: '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
.abstractfalsetrue
  • Values Differ
.baseDefinitionhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signshttp://hl7.org/fhir/StructureDefinition/Observation
  • 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'
.date2022-04-202022-11-21T18:34:14+00:00
  • Values Differ
.descriptionTo promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch body height observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets which **SHALL** be present in the Observation resource when using this profile. It provides the floor for standards development for specific use cases.Profile for Social Determinants of Health (SDOH) observations that involve assessment (e.g., by a provider, payer, etc.) as opposed to being derived only from screening surveys (as is the case for the SDOHCC Screening Response Observation). The Cross-Group Projects work group granted a variance to US Core on 06/10/2021 - Jira ticket FHIR-32892.
  • Values Differ
.experimentalfalse
  • Removed the item 'false'
.fhirVersion4.0.1
    .jurisdiction
      ..jurisdiction[0]urn:iso:std:iso:3166#US
        .kindresource
          .nameUSCoreBodyHeightProfileSDOHCCObservationAssessment
          • Values Differ
          .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
          • Values Differ
          .purpose
            .statusactivedraft
            • Values Differ
            .titleUS Core Body Height ProfileSDOHCC Observation Assessment
            • Values Differ
            .typeObservation
              .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-body-heighthttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationAssessment
              • Values Differ
              .version6.0.0-ballot2.0.0
              • Values Differ

              Structure

              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
              .. Observation C0..*USCoreVitalSignsProfileUS Core Body Height Profile
              C0..*ObservationThis is an abstract profile.
              SDOH assessment observation
              • Elements differ in short: 'US Core Body Height Profile' vs 'SDOH assessment observation'
              • Elements differ in definition: '\-' vs 'For SDOH observations derived from assessment of the individual.'
              • Elements differ in comments: '\-' vs 'For representation of SDOH observations that involve assessment (e.g., by a provider or payer) as opposed to being derived only from screening surveys (as is the case for the SDOHCC Screening Response Observation). Many of the SDOHCC profiles reference one another. One flow supported by this IG is that QuestionnaireResponses result in Observations that can be used as evidence for Conditions that can lead to Goals, ServiceRequests and Procedures. However, alternatives paths are also possible.'
              ... 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: CommonLanguages (preferred): A human language.

                    Additional BindingsPurpose
                    AllLanguagesMax Binding
                    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 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: ObservationStatus (required)
                                    ?!SΣ1..1coderegistered | preliminary | final | amended +
                                    Binding: ObservationStatus (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: ObservationCategoryCodes (preferred): Codes for high level observation categories.


                                      1..*CodeableConceptClassification of type of observation
                                      Slice: Unordered, Open by value:$this
                                      Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                      ... code SΣ1..1CodeableConceptBody Height
                                      Binding: US Core Vital Signs ValueSet (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.


                                      Required Pattern: {"coding":[{"system":"http://loinc.org","code":"8302-2"}]}
                                      SΣ1..1CodeableConceptType of observation (code / type)
                                      Binding: SDOHCC ValueSet LOINC SNOMEDCT (preferred)
                                      • Elements differ in short: 'Body Height' vs 'Type of observation (code / type)'
                                      • Elements differ in definition: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation "name".'
                                      • Elements differ in comments: '*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.' 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. As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set binding strength may change and may be refined to codes (including LOINC and SNOMED) that pertain to SDOH categories.'
                                      • Elements differ in requirements: '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.'
                                      ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(Group | US Core Patient Profile)Who and/or what the observation is about
                                      • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Group], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]])
                                      ... 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Σ0..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                          • Elements differ in short: 'Often just a dateTime for Vital Signs' vs 'Clinically relevant time/time-period for observation'
                                          • Elements differ in definition: '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". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.'
                                          • Elements differ in comments: '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] 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. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing] datatype which allow the measurement to be tied to regular life events. NOTE: dateTime is Must Support, but currently tooling does not support this.'
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          • 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(RelatedPerson | US Core Patient Profile | US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile | US Core CareTeam Profile)Who is responsible for the observation
                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                            • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Practitioner], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization], CanonicalType[http://hl7.org/fhir/StructureDefinition/CareTeam], CanonicalType[http://hl7.org/fhir/StructureDefinition/Patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam]])
                                            ... 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: VitalSignsUnits (extensible): Common UCUM units for recording Vital Signs.

                                            SΣC0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual result
                                            • Elements differ in short: 'Vital Signs Value' vs 'Actual result'
                                            • Elements differ in definition: '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.'
                                            • Elements differ in requirements: '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.'
                                            ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                            Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                            C0..1CodeableConceptWhy the result is missing
                                            Binding: DataAbsentReason (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: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


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


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

                                                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.

                                                  0..1CodeableConceptHow it was done
                                                  Binding: ObservationMethods (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
                                                        C0..*BackboneElementProvides guide for interpretation
                                                          .... 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..1SimpleQuantityLow Range, if relevantC0..1SimpleQuantityLow Range, if relevant
                                                                  .... high C0..1SimpleQuantityHigh Range, if relevantC0..1SimpleQuantityHigh Range, if relevant
                                                                    .... type 0..1CodeableConceptReference range qualifier
                                                                    Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

                                                                    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.


                                                                      0..*CodeableConceptReference range population
                                                                      Binding: ObservationReferenceRangeAppliesToCodes (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
                                                                            Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                            • Elements differ in short: 'Used when reporting vital signs panel components' vs 'Related resource that belongs to the Observation group'
                                                                            • Elements differ in definition: 'Used when reporting vital signs panel components.' vs 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.'
                                                                            • 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/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/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
                                                                            Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                              ... component SΣC0..*BackboneElementComponent observations
                                                                              Σ0..*BackboneElementComponent results
                                                                              • Elements differ in short: 'Component observations' vs 'Component results'
                                                                              • Elements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' 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.'
                                                                              • 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..1CodeableConceptType of component observation (code / type)
                                                                                    Binding: US Core Vital Signs ValueSet (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.

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

                                                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                    • Elements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
                                                                                    .... value[x] SΣC0..1Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Sign Component Value
                                                                                    Binding: VitalSignsUnits (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 short: 'Vital Sign Component Value' vs 'Actual component result'
                                                                                    • Elements differ in definition: '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.'
                                                                                    • Elements differ in requirements: '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.'
                                                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                    .... dataAbsentReason SC0..1CodeableConceptWhy the component result is missing
                                                                                    Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                                    C0..1CodeableConceptWhy the component result is missing
                                                                                    Binding: DataAbsentReason (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: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.


                                                                                    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
                                                                                      0..*See referenceRange (Observation)Provides guide for interpretation of component result

                                                                                        doco Documentation for this format