Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationScreeningResponse

Left:US Core Observation Occupation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation)
Right:SDOHCC Observation Screening Response (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationScreeningResponse)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupation' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationScreeningResponse'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationOccupationProfile' vs 'SDOHCCObservationScreeningResponse'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Occupation Profile' vs 'SDOHCC Observation Screening Response'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2022-08-24' vs '2022-11-21T18:34:14+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Patient Care WG'
WarningObservationElements differ in short: 'Past Or Present Occupation' vs 'SDOH screening questionnaire observations'
WarningObservationElements differ in definition: 'Related data elements for a current or previous job.' vs 'For Observations derived from SDOH screening surveys/questionnaires.'
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 education status, food insecurity observations, etc. This profile allows the representation of SDOH observations based on SDOH screening questionnaire responses (which can also be represented using SDC QuestionnaireResponse). 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.statusElements differ in short: 'registered | preliminary | final | amended +' vs 'final | corrected | entered-in-error | unknown'
WarningObservation.statusElements differ in definition: 'The status of the result value.' vs 'The status of the observation value.'
WarningObservation.statusElements differ in requirements: 'Need to track the status of individual results. Some results are finalized before the whole report is finalized.' vs 'Further constrained to values that are relevant for SDOH.'
WarningObservation.categoryElements differ in requirements: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that an SDOH screening response observation is derived from an SDOH questionnaire, the “social-history” and “survey” codes are required.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.categoryElement minimum cardinalities differ: '0' vs '2'
WarningObservation.codeElements differ in short: 'Occupation history' vs 'Type of observation (code / type)'
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. For SDOH questions represented in LOINC that specify “check all that apply”, the LOINC question should be used for Observation.code and for Observation.component.code. For “check all that apply” questions, the answers (regardless of whether one or more are selected) should only be represented using Observation.component.value and Observation.value should be empty. As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set will be refined to codes that pertain to SDOH categories. For further guidance on external value sets vetted by the Gravity Project see: [Supplemental Guide]'
WarningObservation.codeElements differ in requirements: 'Knowing what kind of observation is being made is essential to understanding the observation.' vs 'Knowing what kind of observation is being made is essential to understanding the observation. The Gravity implemenation guide restricts questionnaire/survey observations to LOINC to move the industry to the use of LOINC panels/surveys (structures that are not available in other terminology systems) to standardize the coding of SDOH related risk assessment instruments. In addition, USCDI and US Core have standardized on the use of LOINC to represent Observations in general.'
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 'Cardinality is 1..1.'
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 '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'.'
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.'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.performerElements differ in requirements: 'May give a degree of confidence in the observation and also indicates where follow-up questions should be directed.' vs 'Some questions on an SDOH screening questionnaire are not answered directly (e.g., asserted) by the individual completing the questionnaire. Rather, the answer to some questions (e.g., the Hunger Vital Sign 88124-3 “Food insecurity risk”) may be derived from answers to one or more other questions. For a Screening Response Observation that is derived, as opposed to answered directly, Observation.performer should not be specified and Observation.derivedFrom should reference the relevant Screening Response Observation(s).'
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 definition for mustSupport: 'false' vs 'true'
InformationObservation.value[x]Element minimum cardinalities differ: '1' vs '0'
WarningObservation.dataAbsentReasonElements differ in comments: 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be 'detected', 'not detected', 'inconclusive', or 'specimen unsatisfactory'. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code 'error' could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' vs ''Null' or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.'
WarningObservation.dataAbsentReasonElements 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 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 an observation is a group observation (e.g., the LOINC 88121-9 Hunger Vital Sign [HVS] panel) that includes the target as a member of the group.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.componentElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observation
      .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-242022-11-21T18:34:14+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.Profile for observations that represent question and answer pairs from Social Determinants of Health (SDOH) screening instruments that are represented in LOINC. The Cross-Group Projects work group granted a variance to US Core on 12/03/2020 - Jira ticket FHIR-29795.
      • Values Differ
      .experimentalfalse
      • Removed the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreObservationOccupationProfileSDOHCCObservationScreeningResponse
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
              • Values Differ
              .purpose
                .statusactivedraft
                • Values Differ
                .titleUS Core Observation Occupation ProfileSDOHCC Observation Screening Response
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-occupationhttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationScreeningResponse
                  • 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..*ObservationPast Or Present Occupation
                  C0..*ObservationSDOH screening questionnaire observations
                  • Elements differ in short: 'Past Or Present Occupation' vs 'SDOH screening questionnaire observations'
                  • Elements differ in definition: 'Related data elements for a current or previous job.' vs 'For Observations derived from SDOH screening surveys/questionnaires.'
                  • 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 education status, food insecurity observations, etc. This profile allows the representation of SDOH observations based on SDOH screening questionnaire responses (which can also be represented using SDC QuestionnaireResponse). 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: US Core Status for Smoking Status Observation (required)
                                        ?!SΣ1..1codefinal | corrected | entered-in-error | unknown
                                        Binding: SDOHCC ValueSet Observation Status (required)
                                        • Elements differ in short: 'registered | preliminary | final | amended +' vs 'final | corrected | entered-in-error | unknown'
                                        • Elements differ in definition: 'The status of the result value.' vs 'The status of the observation value.'
                                        • Elements differ in requirements: 'Need to track the status of individual results. Some results are finalized before the whole report is finalized.' vs 'Further constrained to values that are relevant for SDOH.'
                                        ... Slices for category S0..*CodeableConceptClassification of type of observation
                                        Slice: Unordered, Open by pattern:$this
                                        Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


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


                                        • Elements differ in requirements: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that an SDOH screening response observation is derived from an SDOH questionnaire, the “social-history” and “survey” codes are required.'
                                        • Elements differ in definition for mustSupport: 'true' vs 'false'
                                        • Element minimum cardinalities differ: '0' vs '2'
                                        ... code SΣ1..1CodeableConceptOccupation history
                                        Binding: LOINCCodes (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: LOINCCodes (required)
                                        • Elements differ in short: 'Occupation history' vs 'Type of observation (code / type)'
                                        • 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. For SDOH questions represented in LOINC that specify “check all that apply”, the LOINC question should be used for Observation.code and for Observation.component.code. For “check all that apply” questions, the answers (regardless of whether one or more are selected) should only be represented using Observation.component.value and Observation.value should be empty. As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set will be refined to codes that pertain to SDOH categories. For further guidance on external value sets vetted by the Gravity Project see: [Supplemental Guide]'
                                        • Elements differ in requirements: 'Knowing what kind of observation is being made is essential to understanding the observation.' vs 'Knowing what kind of observation is being made is essential to understanding the observation. The Gravity implemenation guide restricts questionnaire/survey observations to LOINC to move the industry to the use of LOINC panels/surveys (structures that are not available in other terminology systems) to standardize the coding of SDOH related risk assessment instruments. In addition, USCDI and US Core have standardized on the use of LOINC to represent Observations in general.'
                                        ... 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
                                        • 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 'Cardinality is 1..1.'
                                        ... 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
                                            ... Slices for effective[x] Σ1..1PeriodClinically relevant time/time-period for observation
                                            Slice: Unordered, Closed by type:$this
                                            SΣ1..1dateTime, PeriodClinically relevant time/time-period for observation
                                            • 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 '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".'
                                            • 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.'
                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                            ... 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 requirements: 'May give a degree of confidence in the observation and also indicates where follow-up questions should be directed.' vs 'Some questions on an SDOH screening questionnaire are not answered directly (e.g., asserted) by the individual completing the questionnaire. Rather, the answer to some questions (e.g., the Hunger Vital Sign 88124-3 “Food insecurity risk”) may be derived from answers to one or more other questions. For a Screening Response Observation that is derived, as opposed to answered directly, Observation.performer should not be specified and Observation.derivedFrom should reference the relevant Screening Response Observation(s).'
                                              • 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] ΣC1..1CodeableConceptActual result
                                              Slice: Unordered, Closed by type:$this
                                              SΣC0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual result
                                              Slice: Unordered, Open by type:$this
                                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                                              • Element minimum cardinalities differ: '1' vs '0'
                                              ... dataAbsentReason C0..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.

                                              • Elements differ in comments: 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' vs '"Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.'
                                              • 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.


                                                ... 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..0
                                                  • Element maximum cardinalities differ: '1' vs '0'
                                                  ... 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..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..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(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                          • 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 an observation is a group observation (e.g., the LOINC 88121-9 Hunger Vital Sign [HVS] panel) that includes the target as a member of the group.'
                                                                          ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                          SΣ0..*Reference(DocumentReference | QuestionnaireResponse | Observation)Related measurements the observation is made from
                                                                          Slice: Unordered, Open by profile:resolve()
                                                                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                          ... 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: LOINCCodes (example): Codes identifying names of simple observations.

                                                                                Σ1..1CodeableConceptType of component observation (code / type)
                                                                                Binding: LOINCCodes (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: 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.

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