Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicityOMB

Left:US Core Observation Screening Assessment Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment)
Right:SDOHCC Observation Ethnicity OMB (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicityOMB)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicityOMB'
ErrorStructureDefinition.versionValues for version differ: '7.0.0' vs '2.2.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationScreeningAssessmentProfile' vs 'SDOHCCObservationEthnicityOMB'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Screening Assessment Profile' vs 'SDOHCC Observation Ethnicity OMB'
InformationStructureDefinition.dateValues for date differ: '2023-10-17' vs '2024-08-27T17:19:22+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Patient Care'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalCharacteristic'
InformationStructureDefinition.shortValues for short differ: 'Survey Observation' vs 'Ethnicity observation'
InformationStructureDefinition.definitionValues for definition differ: 'Measurements and simple assertions made about a patient, device or other subject.' vs 'For ethnicity observations that use Office of Management and Budget (OMB) ethnicity category codes and CDC ethnicity codes.'
InformationStructureDefinition.commentValues for comment differ: 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.' vs 'Used for observations about the ethnicity of an individual.'
InformationStructureDefinition.shortValues for short differ: 'Additional content defined by implementations' vs 'Extension'
InformationStructureDefinition.definitionValues for definition differ: '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'
InformationStructureDefinition.shortValues for short differ: 'registered | preliminary | final | amended +' vs 'final | corrected | entered-in-error | unknown'
InformationStructureDefinition.definitionValues for definition differ: 'The status of the result value.' vs 'The status of the observation value.'
InformationStructureDefinition.requirementsValues for requirements differ: '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 personal characteristic observations.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.commentValues for comment differ: '*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. NOTE: In LOINC, System Patient is used in the modeling of codes referenced by the Personal Characteristics profiles (e.g., 72826-1 Race OMB.1997, 69490-1 Ethnicity OMB.1997, 76691-5 Gender identity, 76690-7 Sexual orientation, 90778-2 Personal pronouns – Reported, and 99502-7 Recorded sex or gender). If the draft profiles are adopted, new LOINC codes without System Patient would be needed since these profiles can also be used to capture characteristics of a provider (using an extension) or a related person (using focus).'
InformationObservation.codeExample/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningAssessmentProfile
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
InformationObservation.focusElement maximum cardinalities differ: '2147483647' vs '1'
InformationStructureDefinition.definitionValues for definition differ: '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'.' vs 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the 'physiologically relevant time'. This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.'
InformationStructureDefinition.commentValues for comment differ: 'At least a date should be present unless this observation is a historical report.' 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](datatypes.html#timing) datatype which allow the measurement to be tied to regular life events. NOTE: dateTime is Must Support, but currently tooling does not support this.'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.commentValues for comment differ: 'An observation may have a value if it represents an individual survey, screening, or assessment question and answer pair. An observation should not have a value if it represents a multi-question or multi-select “check all that apply” responses. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.' vs 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section](http://hl7.org/fhir/R4/observation.html#notes) below.'
InformationObservation.value[x]Element maximum cardinalities differ: '1' vs '0'
InformationStructureDefinition.commentValues for comment differ: ''Null' or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. 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.' 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. 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.'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.interpretationElement maximum cardinalities differ: '2147483647' vs '0'
InformationObservation.bodySiteElement maximum cardinalities differ: '1' vs '0'
WarningObservation.methodElements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.methodElement minimum cardinalities differ: '0' vs '1'
InformationObservation.specimenElement maximum cardinalities differ: '1' vs '0'
InformationObservation.referenceRangeElement maximum cardinalities differ: '2147483647' vs '0'
InformationStructureDefinition.shortValues for short differ: 'Reference to panel members or multi-select responses or multi-select responses' vs 'Related resource that belongs to the Observation group'
InformationStructureDefinition.definitionValues for definition differ: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys, screenings, and assessments and multi-select questions.' vs 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.'
InformationStructureDefinition.commentValues for comment differ: 'This grouping element is used to represent surveys, screenings, and assessments that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the 'panel' observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. When there is a heirarchical grouping of questions, the observation 'panels' can be nested. Because surveys, screenings, and assessments can be arbitrarily complex structurally, not all structures can be represented using this Observation grouping pattern.' vs 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html) into a final score and represent the score as an Observation.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.shortValues for short differ: '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Related Observation(s) or other resource the observation is made from' vs 'Related measurements the observation is made from'
InformationStructureDefinition.definitionValues for definition differ: 'Observations or or other resource such as a QuestionnaireResponse from which this observation value is derived.' vs 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.'
ErrorObservation.derivedFromType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation]])
InformationStructureDefinition.definitionValues for definition differ: '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 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes.'
InformationStructureDefinition.commentValues for comment differ: 'For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/R4/observation.html#notes) below.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes](observation.html#notes) below. NOTE: The same LOINC code is used for all three components of this draft profile. If the profile is adopted as part of the US Core standard, new LOINC codes (possibly a panel) will be needed to represent the components (e.g., a new LOINC code for detailed ethnicity and for text description of ethnicity).'
InformationStructureDefinition.requirementsValues for requirements differ: 'Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.' vs 'Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable).'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalCharacteristic
    • Values Differ
    .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
    • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
    .date2023-10-172024-08-27T17:19:22+00:00
    • Values Differ
    .descriptionThe US Core Observation Screening Assessment Profile inherits from the FHIR [Observation](https://hl7.org/fhir/R4/observation.html) resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) *Health Status Assessments* Data Class. It sets the minimum expectations for the Observation Resource to record, search, and fetch observations representing the questions and responses to surveys and screening and assessment tools. For example, a social history status such as education or food insecurity or an assessment of cognitive, functional, or disability status. It can represent a single response, multiple responses, and multi-select "check all that apply" type questions. This profile specifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. Before reviewing this profile, implementers are encouraged to read the Screening and Assessments guidance page, which documents the process of recording responses and capturing assertions/determinations resulting from surveys and questionnaires.Profile for ethnicity observations that use Office of Management and Budget (OMB) ethnicity category codes and CDC ethnicity codes. This profile is intended for draft use only. For further details on this profile see [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html).
    • Values Differ
    .experimental
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreObservationScreeningAssessmentProfileSDOHCCObservationEthnicityOMB
              • Values Differ
              .publisherHL7 International / Cross-Group ProjectsHL7 International / Patient Care
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Observation Screening Assessment ProfileSDOHCC Observation Ethnicity OMB
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessmenthttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicityOMB
                    • Values Differ
                    .version7.0.02.2.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                    .. Observation C0..*ObservationSurvey Observation
                    obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
                    obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
                    us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                    C0..*SDOHCCObservationPersonalCharacteristicEthnicity observation
                    obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present
                    obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
                    SDOH-Obs-1: Either subject or extension-Observation.subject must exist but not both
                    SDOH-Obs-2: Focus is only allowed if subject is present
                    SDOH-Obs-3: Must have either performer or derivedFrom
                    SDOH-Ethnicity-1: Must have either a dataAbsentReason or at least one of the defined ethnicity components but not both
                      ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                        ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                          ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                            ... language 0..1codeLanguage of the resource content
                            Binding: ?? (preferred): A human language.

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

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

                                            ?!SΣ1..1codefinal | corrected | entered-in-error | unknown
                                            Binding: ?? (required)
                                              ... Slices for category S1..*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 value:$this
                                              Binding: ?? (preferred): Codes for high level observation categories.


                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              ... code SΣ1..1CodeableConceptType of observation (code / type)
                                              Binding: ?? (preferred)
                                              SΣ1..1CodeableConceptType of observation (code / type)
                                              Binding: ?? (preferred): Codes identifying names of simple observations.


                                              Required Pattern: {"coding":[{"system":"http://loinc.org","code":"69490-1"}]}
                                              • Example/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningAssessmentProfile
                                              ... subject SΣ1..1Reference(US Core Patient Profile S | Group | Device | US Core Location Profile)Who and/or what the observation is aboutSΣC0..1Reference(US Core Patient Profile)Who and/or what the observation is about
                                              • Element minimum cardinalities differ: '1' vs '0'
                                              ... focus Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                              ΣC0..1Reference(RelatedPerson)What the observation is about, when it is not about the subject of record
                                              • Element maximum cardinalities differ: '2147483647' vs '1'
                                              ... 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.
                                                Σ0..1dateTime, PeriodClinically relevant time/time-period for observation
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                                  ... performer SΣ0..*Reference(US Core Practitioner Profile | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core RelatedPerson Profile)Who is responsible for the observation
                                                  SΣC0..*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, PeriodActual result
                                                    us-core-3: SHALL use UCUM for coded quantity units.
                                                    SΣC0..0
                                                    • Element maximum cardinalities differ: '1' vs '0'
                                                    ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                    Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                    C0..1CodeableConceptWhy the result is missing
                                                    Binding: ?? (required)
                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                    ... interpretation 0..*CodeableConceptHigh, low, normal, etc.
                                                    Binding: ?? (extensible): Codes identifying interpretations of observations.


                                                    0..0
                                                    • Element maximum cardinalities differ: '2147483647' vs '0'
                                                    ... note 0..*AnnotationComments about the observation
                                                    0..*AnnotationComments about the observation
                                                      ... bodySite 0..1CodeableConceptObserved body part
                                                      Binding: ?? (example): Codes describing anatomical locations. May include laterality.

                                                      0..0
                                                      • Element maximum cardinalities differ: '1' vs '0'
                                                      ... method 0..1CodeableConceptHow it was done
                                                      Binding: ?? (example): Methods for simple observations.

                                                      S1..1CodeableConceptHow it was done
                                                      Binding: ?? (extensible): Methods for personal characteristic observations.

                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                      • Element minimum cardinalities differ: '0' vs '1'
                                                      ... 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
                                                        obs-3: Must have at least a low or a high or text
                                                        C0..0
                                                        • Element maximum cardinalities differ: '2147483647' vs '0'
                                                        .... 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 SΣ0..*Reference(US Core Observation Screening Assessment Profile S | QuestionnaireResponse | MolecularSequence)Reference to panel members or multi-select responses or multi-select responses
                                                                          Σ0..*Reference(Observation | QuestionnaireResponse | MolecularSequence)Related resource that belongs to the Observation group
                                                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                          ... derivedFrom SΣ0..*Reference(US Core Observation Screening Assessment Profile S | US Core QuestionnaireResponse Profile S | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence)𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Related Observation(s) or other resource the observation is made from
                                                                          SΣC0..*Reference(DocumentReference | QuestionnaireResponse | Observation)Related measurements the observation is made from
                                                                          • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-assessment], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation]])
                                                                          ... component Σ0..*BackboneElementComponent results
                                                                          ΣC0..*BackboneElementComponent results
                                                                          Slice: Unordered, Open by pattern:code, type:value, value:value
                                                                            .... 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