Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaging vs http://hl7.org/fhir/us/vitals/StructureDefinition/average-blood-pressure

Left:US Core Observation Imaging Result Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaging)
Right:Average Blood Pressure (http://hl7.org/fhir/us/vitals/StructureDefinition/average-blood-pressure)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaging' vs 'http://hl7.org/fhir/us/vitals/StructureDefinition/average-blood-pressure'
ErrorStructureDefinition.versionValues for version differ: '5.0.1' vs '1.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationImagingResultProfile' vs 'AverageBloodPressure'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Imaging Result Profile' vs 'Average Blood Pressure'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2022-09-12T00:45:08+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Clinical Information Modeling Initiative'
InformationStructureDefinition.copyrightValues for copyright differ: 'Used by permission of HL7 International, all rights reserved Creative Commons License' vs 'Logica Health, all rights reserved Creative Commons License'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/StructureDefinition/vitalsigns'
WarningObservationElements differ in short: 'Measurements and simple assertions' vs 'FHIR Vital Signs Profile'
WarningObservationElements differ in definition: '\-' vs 'The FHIR Vitals Signs profile sets minimum expectations for the Observation Resource to record, search and fetch the vital signs associated with a patient.'
WarningObservationElements differ in comments: '\-' vs '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.'
WarningObservation.extensionElements differ in short: 'Additional content defined by implementations' vs 'Extension'
WarningObservation.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
WarningObservation.codeElements differ in short: 'Imaging Name' vs 'Blood pressure panel unspecified time mean'
WarningObservation.codeElements differ in definition: 'The name of the imaging test performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Coded Responses from C-CDA Vital Sign Results.'
WarningObservation.codeElements differ in comments: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' 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.'
WarningObservation.codeElements differ in requirements: 'Knowing what kind of observation is being made is essential to understanding the observation.' vs '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).'
WarningObservation.effective[x]Elements differ in short: 'Clinically relevant time/time-period for observation' vs 'Often just a dateTime for Vital Signs'
WarningObservation.effective[x]Elements differ in definition: '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.' vs 'Often just a dateTime for Vital Signs.'
InformationObservation.effective[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.value[x]Elements differ in short: 'Result Value' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
WarningObservation.value[x]Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
WarningObservation.value[x]Elements differ in requirements: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).'
InformationObservation.value[x]Element maximum cardinalities differ: '1' vs '0'
WarningObservation.bodySiteElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.bodySiteElements differ in binding.description: 'Codes describing anatomical locations. May include laterality.' vs 'A set of codes that describe where on/in the body an observation or procedure took place'
WarningObservation.methodElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.methodElements differ in binding.description: 'Methods for simple observations.' vs 'A set of codes that describe the method used to measure a blood pressure'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
WarningObservation.deviceElements differ in short: '(Measurement) Device' vs 'Blood Pressure Device'
WarningObservation.deviceElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.hasMemberElements differ in short: 'Related resource that belongs to the Observation group' vs 'Used when reporting vital signs panel components'
WarningObservation.hasMemberElements differ in definition: '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.' vs 'Used when reporting vital signs panel components.'
ErrorObservation.hasMemberType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])
WarningObservation.componentElements differ in short: 'Component results' vs 'Blood pressure components'
WarningObservation.componentElements differ in definition: '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.' vs 'Used when reporting systolic and diastolic blood pressure.'
WarningObservation.componentElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.componentElement minimum cardinalities differ: '0' vs '1'
WarningObservation.component.codeElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.component.codeElements differ in binding.description: 'Codes identifying names of simple observations.' vs 'This identifies the vital sign result type.'
WarningObservation.component.value[x]Elements differ in short: 'Actual component result' vs 'Vital Sign Value recorded with UCUM'
WarningObservation.component.value[x]Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'Vital Sign Value recorded with UCUM.'
WarningObservation.component.value[x]Elements differ in requirements: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type='PQ' (CONF:7305).'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://hl7.org/fhir/StructureDefinition/vitalsigns
    • Values Differ
    .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons LicenseLogica Health, all rights reserved Creative Commons License
    • Values Differ
    .date2022-04-202022-09-12T00:45:08+00:00
    • Values Differ
    .descriptionThe US Core Observation Imaging Result Profile is based upon the core FHIR Observation Resource, and, along with the US Core DiagnosticReport Profile for Report and Note exchange, meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Diagnostic Imaging’ requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch retrieve structured and unstructured (narrative) components of diagnostic imaging test results for a patient. These observations include reasons, findings, and impressions. It provides the floor for standards development for specific uses cases.A calculated average of two or more blood pressure readings in a specified time period or according to a specified algorithm or protocol. The average blood pressure has a systolic and a diastolic component.
    • Values Differ
    .experimental
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreObservationImagingResultProfileAverageBloodPressure
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 International - Clinical Information Modeling Initiative
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Observation Imaging Result ProfileAverage Blood Pressure
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaginghttp://hl7.org/fhir/us/vitals/StructureDefinition/average-blood-pressure
                    • Values Differ
                    .version5.0.11.0.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. Observation C0..*ObservationMeasurements and simple assertions
                    us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                    C0..*observation-vitalsignsFHIR Vital Signs Profile
                    • Elements differ in short: 'Measurements and simple assertions' vs 'FHIR Vital Signs Profile'
                    • Elements differ in definition: '\-' vs 'The FHIR Vitals Signs profile sets minimum expectations for the Observation Resource to record, search and fetch the vital signs associated with a patient.'
                    • Elements differ in comments: '\-' vs '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.'
                    ... id Σ0..1stringLogical 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..*ExtensionExtension
                                Slice: Unordered, Open by value:url
                                • Elements differ in short: 'Additional content defined by implementations' vs 'Extension'
                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
                                ... 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): Codes providing the status of an observation.

                                        ?!SΣ1..1coderegistered | preliminary | final | amended +
                                        Binding: ObservationStatus (required)
                                          ... Slices for category S1..*CodeableConceptClassification of type of observation
                                          Slice: Unordered, Open by pattern:$this
                                          Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


                                          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.


                                            ... code SΣ1..1CodeableConceptImaging Name
                                            Binding: US Core Diagnosticreport Report And Note Codes (extensible)
                                            SΣ1..1CodeableConceptBlood pressure panel unspecified time mean
                                            Binding: VitalSigns (extensible): This identifies the vital sign result type.


                                            Required Pattern: {"coding":[{"system":"http://loinc.org","code":"96607-7"}]}
                                            • Elements differ in short: 'Imaging Name' vs 'Blood pressure panel unspecified time mean'
                                            • Elements differ in definition: 'The name of the imaging test performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Coded Responses from C-CDA Vital Sign Results.'
                                            • Elements differ in comments: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a "local" code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' 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.'
                                            • Elements differ in requirements: 'Knowing what kind of observation is being made is essential to understanding the observation.' vs '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).'
                                            ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(US Core Patient Profile)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ΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                                  us-core-1: Datetime must be at least to day.
                                                  SΣC1..1dateTime, PeriodOften just a dateTime for Vital Signs
                                                  • Elements differ in short: 'Clinically relevant time/time-period for observation' vs 'Often just a dateTime for Vital Signs'
                                                  • Elements differ in definition: '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.' vs 'Often just a dateTime for Vital Signs.'
                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                  ... 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
                                                    Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                      ... value[x] SΣC0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodResult Value
                                                      us-core-3: SHALL use UCUM for coded quantity units.
                                                      SΣC0..0
                                                      • Elements differ in short: 'Result Value' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
                                                      • Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
                                                      • Elements differ in requirements: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).'
                                                      • Element maximum cardinalities differ: '1' vs '0'
                                                      ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                      Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                      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.


                                                        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.

                                                            S0..1CodeableConceptObserved body part
                                                            Binding: Blood Pressure Measurement Body Location Precoordinated value set (extensible): A set of codes that describe where on/in the body an observation or procedure took place

                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                            • Elements differ in binding.description: 'Codes describing anatomical locations. May include laterality.' vs 'A set of codes that describe where on/in the body an observation or procedure took place'
                                                            ... method 0..1CodeableConceptHow it was done
                                                            Binding: ObservationMethods (example): Methods for simple observations.

                                                            S0..1CodeableConceptHow it was done
                                                            Binding: Blood Pressure Measurement Method value set (extensible): A set of codes that describe the method used to measure a blood pressure

                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                            • Elements differ in binding.description: 'Methods for simple observations.' vs 'A set of codes that describe the method used to measure a blood pressure'
                                                            ... specimen 0..1Reference(Specimen)Specimen used for this observation0..0
                                                            • Element maximum cardinalities differ: '1' vs '0'
                                                            ... device 0..1Reference(Device | DeviceMetric)(Measurement) DeviceS0..1Reference(Blood Pressure Device)Blood Pressure Device
                                                            • Elements differ in short: '(Measurement) Device' vs 'Blood Pressure Device'
                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                            ... 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(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                                Σ0..*Reference(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Used when reporting vital signs panel components
                                                                                • Elements differ in short: 'Related resource that belongs to the Observation group' vs 'Used when reporting vital signs panel components'
                                                                                • Elements differ in definition: '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.' vs 'Used when reporting vital signs panel components.'
                                                                                • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])
                                                                                ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile)Related measurements the observation is made from
                                                                                  ... component Σ0..*BackboneElementComponent results
                                                                                  SΣC1..*BackboneElementBlood pressure components
                                                                                  Slice: Unordered, Open by pattern:code
                                                                                  • Elements differ in short: 'Component results' vs 'Blood pressure components'
                                                                                  • Elements differ in definition: '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.' vs 'Used when reporting systolic and diastolic blood pressure.'
                                                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                                                  .... 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 Σ1..1CodeableConceptType of component observation (code / type)
                                                                                        Binding: LOINCCodes (example): Codes identifying names of simple observations.

                                                                                        SΣ1..1CodeableConceptType of component observation (code / type)
                                                                                        Binding: VitalSigns (extensible): This identifies the vital sign result type.

                                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                        • Elements differ in binding.description: 'Codes identifying names of simple observations.' vs 'This identifies the vital sign result type.'
                                                                                        .... value[x] Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component resultSΣC0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodVital Sign Value recorded with UCUM
                                                                                        Binding: VitalSignsUnits (required): Common UCUM units for recording Vital Signs.

                                                                                        • Elements differ in short: 'Actual component result' vs 'Vital Sign Value recorded with UCUM'
                                                                                        • Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'Vital Sign Value recorded with UCUM.'
                                                                                        • Elements differ in requirements: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).'
                                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                        .... dataAbsentReason C0..1CodeableConceptWhy the component result is missing
                                                                                        Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                                        SC0..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: 'false' vs 'true'
                                                                                        .... 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