Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation vs http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-activity-group

Left:US Core Observation Occupation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation)
Right:PA Observation Activity Group (http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-activity-group)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation' vs 'http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-activity-group'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '1.0.0-ballot'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationOccupationProfile' vs 'PAObservationActivityGroup'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Occupation Profile' vs 'PA Observation Activity Group'
InformationStructureDefinition.dateValues for date differ: '2022-08-24' vs '2023-03-28T18:30:00+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Patient Care WG'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-base'
WarningObservationElements differ in short: 'Past Or Present Occupation' vs 'Measurements and simple assertions'
WarningObservationElements differ in definition: 'Related data elements for a current or previous job.' vs 'A profile for observations that collects a set of activity-related measures that all pertain to the same physical activity instance.'
WarningObservationElements differ in comments: 'A person can have more than one job at the same time and multiple jobs over time' 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.'
InformationObservation.implicitRulesElement maximum cardinalities differ: '1' vs '0'
WarningObservation.modifierExtensionElements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
WarningObservation.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
InformationObservation.modifierExtensionElement maximum cardinalities differ: '2147483647' vs '0'
WarningObservation.statusElements differ in short: 'registered | preliminary | final | amended +' vs 'final | amended | corrected | entered-in-error'
WarningObservation.statusElements differ in comments: 'This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.' vs 'In the vast majority of cases, the status value will be 'final'. Systems are not expected to distinguish amended and corrected results.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.categoryElement minimum cardinalities differ: '0' vs '1'
WarningObservation.codeElements differ in short: 'Occupation history' vs 'Type of observation (code / type)'
WarningObservation.subjectElements differ in short: 'Who and/or what the observation is about' vs 'A reference from one resource to another'
WarningObservation.subjectElements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'A reference from one resource to another.'
WarningObservation.subjectElements differ in comments: 'One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
InformationObservation.focusElement maximum cardinalities differ: '2147483647' vs '0'
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. This will typically be a dateTime specific to the day. If the information is available, a Period can be used to indicate the specific start and end times. It **SHOULD** be the same as the effective[x] value for all member Observations.'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.effective[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.performerElements differ in short: 'Who is responsible for the observation' vs 'A reference from one resource to another'
WarningObservation.performerElements differ in definition: 'Who was responsible for asserting the observed value as 'true'.' vs 'A reference from one resource to another.'
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/us/physical-activity/StructureDefinition/reference-rest-or-logical]])([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/StructureDefinition/RelatedPerson]])
WarningObservation.value[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.value[x]Element minimum cardinalities differ: '1' vs '0'
InformationObservation.value[x]Element maximum cardinalities differ: '1' vs '0'
ErrorObservation.value[x]Element minimum cardinalities conflict: '1..1' vs '0..0': No instances can be valid against both profiles
WarningObservation.noteElements differ in comments: 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.' vs 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. Comments allows supporting and qualifying information'
WarningObservation.noteElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.note.author[x]Elements differ in short: 'Individual responsible for the annotation' vs 'A reference from one resource to another'
WarningObservation.note.author[x]Elements differ in definition: 'The individual responsible for making the annotation.' vs 'A reference from one resource to another.'
WarningObservation.note.author[x]Elements differ in comments: 'Organization is used when there's no need for specific attribution as to who made the comment.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
WarningObservation.note.author[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.note.author[x]Element minimum cardinalities differ: '0' vs '1'
WarningObservation.note.timeElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.note.timeElement minimum cardinalities differ: '0' vs '1'
WarningObservation.note.textElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.bodySiteElement maximum cardinalities differ: '1' vs '0'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
WarningObservation.hasMemberElements differ in short: 'Related resource that belongs to the Observation group' vs 'A reference from one resource to another'
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 'A reference from one resource to another.'
WarningObservation.hasMemberElements differ in comments: '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] below. Note that a system may calculate results from [QuestionnaireResponse] into a final score and represent the score as an Observation.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.hasMemberElement minimum cardinalities differ: '0' vs '1'
WarningObservation.componentElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-base
    • 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-08-242023-03-28T18:30:00+00:00
    • Values Differ
    .descriptionThe US Core Occupation Status Observation Profile is based upon the core FHIR Observation Resource and implements the US Core Data for Interoperability (USCDI) v3 Occupation status requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch the "Type of work of a person" and "Type of business that compensates for work or assigns work to an unpaid worker or volunteer" associated with a patient. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific use cases.A profile for observations that collects a set of activity-related measures that all pertain to the same physical activity instance.
    • Values Differ
    .experimentalfalse
    • Removed the item 'false'
    .fhirVersion4.0.1
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
          .kindresource
            .nameUSCoreObservationOccupationProfilePAObservationActivityGroup
            • Values Differ
            .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
            • Values Differ
            .purpose
              .statusactive
                .titleUS Core Observation Occupation ProfilePA Observation Activity Group
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupationhttp://hl7.org/fhir/us/physical-activity/StructureDefinition/pa-observation-activity-group
                  • Values Differ
                  .version6.0.0-ballot1.0.0-ballot
                  • Values Differ

                  Structure

                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                  .. Observation C0..*ObservationPast Or Present Occupation
                  C0..*PAObservationBaseMeasurements and simple assertions
                  • Elements differ in short: 'Past Or Present Occupation' vs 'Measurements and simple assertions'
                  • Elements differ in definition: 'Related data elements for a current or previous job.' vs 'A profile for observations that collects a set of activity-related measures that all pertain to the same physical activity instance.'
                  • Elements differ in comments: 'A person can have more than one job at the same time and multiple jobs over time' 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..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..0
                      • Element maximum cardinalities differ: '1' vs '0'
                      ... 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..0
                              • Elements differ in short: 'Extensions that cannot be ignored' vs 'Extension'
                              • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
                              • Element maximum cardinalities differ: '2147483647' vs '0'
                              ... 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): Codes providing the status of an observation.

                                    ?!SΣ1..1codefinal | amended | corrected | entered-in-error
                                    Binding: ?? (required)
                                    • Elements differ in short: 'registered | preliminary | final | amended +' vs 'final | amended | corrected | entered-in-error'
                                    • Elements differ in comments: 'This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.' vs 'In the vast majority of cases, the status value will be 'final'. Systems are not expected to distinguish amended and corrected results.'
                                    ... Slices for category S0..*CodeableConceptClassification of type of observation
                                    Slice: Unordered, Open by pattern:$this
                                    Binding: ?? (preferred): Codes for high level observation categories.


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


                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                    • Element minimum cardinalities differ: '0' vs '1'
                                    ... code SΣ1..1CodeableConceptOccupation history
                                    Binding: ?? (example): Codes identifying names of simple observations.


                                    Required Pattern: {"coding":[{"system":"http://loinc.org","code":"11341-5"}]}
                                    SΣ1..1CodeableConceptType of observation (code / type)
                                    Binding: ?? (preferred)
                                    Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/us/physical-activity/CodeSystem/pa-temporary-codes","code":"PAPanel"}]}
                                    • Elements differ in short: 'Occupation history' vs 'Type of observation (code / type)'
                                    ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(US Core Patient Profile)A reference from one resource to another
                                    • Elements differ in short: 'Who and/or what the observation is about' vs 'A reference from one resource to another'
                                    • Elements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'A reference from one resource to another.'
                                    • Elements differ in comments: 'One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
                                    ... focus ΣTU0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                    Σ0..0
                                    • Element maximum cardinalities differ: '2147483647' vs '0'
                                    ... encounter Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                      ... Slices for effective[x] Σ0..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                      Slice: Unordered, Open by type:$this
                                      SΣ1..1dateTime S, PeriodClinically relevant time/time-period for observation
                                      Slice: Unordered, Closed by type:$this
                                      • 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. This will typically be a dateTime specific to the day. If the information is available, a Period can be used to indicate the specific start and end times. It **SHOULD** be the same as the effective[x] value for all member Observations.'
                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                      • 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
                                        SΣ0..*Reference(US Core Patient Profile S | US Core Practitioner Profile S | US Core PractitionerRole Profile | RelatedPerson)A reference from one resource to another
                                        • Elements differ in short: 'Who is responsible for the observation' vs 'A reference from one resource to another'
                                        • Elements differ in definition: 'Who was responsible for asserting the observed value as "true".' vs 'A reference from one resource to another.'
                                        • 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/us/physical-activity/StructureDefinition/reference-rest-or-logical]])([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/StructureDefinition/RelatedPerson]])
                                        ... Slices for value[x] ΣC1..1CodeableConceptActual result
                                        Slice: Unordered, Closed by type:$this
                                        SΣC0..0
                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                        • Element minimum cardinalities differ: '1' vs '0'
                                        • Element maximum cardinalities differ: '1' vs '0'
                                        • Element minimum cardinalities conflict: '1..1' vs '0..0': No instances can be valid against both profiles
                                        ... dataAbsentReason C0..1CodeableConceptWhy the result is missing
                                        Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                        C0..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
                                            S0..*AnnotationComments about the observation
                                            • Elements differ in comments: 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.' vs 'May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation. Comments allows supporting and qualifying information'
                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                            .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                              .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                              Slice: Unordered, Open by value:url
                                              0..*ExtensionAdditional content defined by implementations
                                              Slice: Unordered, Open by value:url
                                                .... author[x] Σ0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotationSΣ1..1Reference(Practitioner S | Patient S | RelatedPerson)A reference from one resource to another
                                                • Elements differ in short: 'Individual responsible for the annotation' vs 'A reference from one resource to another'
                                                • Elements differ in definition: 'The individual responsible for making the annotation.' vs 'A reference from one resource to another.'
                                                • Elements differ in comments: 'Organization is used when there's no need for specific attribution as to who made the comment.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.'
                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                • Element minimum cardinalities differ: '0' vs '1'
                                                .... time Σ0..1dateTimeWhen the annotation was madeSΣ1..1dateTimeWhen the annotation was made
                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                • Element minimum cardinalities differ: '0' vs '1'
                                                .... text Σ1..1markdownThe annotation - text content (as markdown)SΣ1..1markdownThe annotation - text content (as markdown)
                                                • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                ... bodySite 0..1CodeableConceptObserved body part
                                                Binding: ?? (example): Codes describing anatomical locations. May include laterality.

                                                0..0
                                                • Element maximum cardinalities differ: '1' vs '0'
                                                ... 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..0
                                                  • Element maximum cardinalities differ: '1' vs '0'
                                                  ... 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..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(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                        SΣ1..*Reference(PA Observation - Activity-based)A reference from one resource to another
                                                                        • Elements differ in short: 'Related resource that belongs to the Observation group' vs 'A reference from one resource to another'
                                                                        • 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 'A reference from one resource to another.'
                                                                        • Elements differ in comments: '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] below. Note that a system may calculate results from [QuestionnaireResponse] into a final score and represent the score as an Observation.' vs 'References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. A variety of resources might provide support for asserting this condition, however at minimum, systems must support the Physical Activity Vital Sign observations.'
                                                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                        • Element minimum cardinalities differ: '0' vs '1'
                                                                        ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                        Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                          ... Slices for component SΣ0..*BackboneElementComponent results
                                                                          Slice: Unordered, Open by pattern:code.coding
                                                                          Σ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 Σ1..1CodeableConceptType of component observation (code / type)
                                                                                Binding: ?? (example): Codes identifying names of simple observations.

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

                                                                                  .... value[x] Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component resultΣ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                                    .... dataAbsentReason C0..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.

                                                                                      .... 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