Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result vs http://hl7.org/fhir/us/home-lab-report/StructureDefinition/Observation-patient-question-answer

Left:US Core Observation Clinical Result Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result)
Right:Observation - Patient Question Answer (http://hl7.org/fhir/us/home-lab-report/StructureDefinition/Observation-patient-question-answer)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/us/home-lab-report/StructureDefinition/Observation-patient-question-answer'
ErrorStructureDefinition.versionValues for version differ: '6.0.0-ballot' vs '1.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationClinicalResultProfile' vs 'ObservationPatientQuestionAnswer'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Clinical Result Profile' vs 'Observation - Patient Question Answer'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2023-03-25T16:46:40+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'Orders and Observations'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey'
WarningObservationElements differ in short: 'Measurements and simple assertions' vs 'Survey Observation'
WarningObservation.categoryElements differ in requirements: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that observation is derived from a questionnaire.'
WarningObservation.codeElements differ in short: 'Clinical Test or Procedure Name' vs 'Questions asked of the patient by the app when recording or uploading their at-home in-vitro test results.'
WarningObservation.codeElements differ in definition: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
WarningObservation.codeElements differ in comments: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.'
ErrorObservation.codeUnable to resolve right value set http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1099.55 at Observation.code
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.performerElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.value[x]Elements differ in short: 'Result Value' vs 'Answer given to a question asked of the patient by the app when recording or uploading their test results.'
WarningObservation.value[x]Elements differ in definition: 'The clinical test or procedure result value. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM]. A FHIR [UCUM Codes value set] that defines all UCUM codes is in the FHIR specification.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
WarningObservation.value[x]Elements differ in comments: '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] below.' vs 'An observation may have a value if it represents an individual survey question and answer pair. An observation should not have a value if it represents a multi-question survey or multi-select “check all that apply” question. 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.'
InformationObservation.value[x]Element minimum cardinalities differ: '0' vs '1'
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.hasMemberElements differ in short: 'Related resource that belongs to the Observation group' vs 'Reference to panel or multi-select responses'
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 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.'
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 'This grouping element is used to represent surveys 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. In a survey that has a heirarchical grouping of questions, the observation 'panels' can be nested. Because surveys can be arbitrarily complex structurally, not all survey structures can be represented using this Observation grouping pattern.'
WarningObservation.hasMemberElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.derivedFromElements differ in short: 'Related measurements the observation is made from' vs 'Related Observations or QuestionnaireResponses that the observation is made from'
WarningObservation.derivedFromElements differ in definition: '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.' vs 'Observations or QuestionnaireResponses from which this observation value is derived.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'false' vs 'true'
ErrorObservation.derivedFromType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], 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]])

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey
    • Values Differ
    .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
    • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
    .date2022-04-202023-03-25T16:46:40+00:00
    • Values Differ
    .descriptionThe US Core Observation Clinical Result Profile is based upon the core FHIR Observation Resource and, along with the US Core DiagnosticReport Profile, meets the US Core Data for Interoperability (USCDI) requirements for *Diagnostic Imaging* and *Clinical Tests* Data Classes. This profile sets minimum expectations for the Observation resource to record and search non-laboratory clinical test results (e.g., radiology and other clinical observations generated from procedures). An example would be when a gastroenterologist reports the size of a polyp observed during a colonoscopy. This profile is the basis for the US Core Laboratory Result Observation Profile, which defines additional data elements to record and search laboratory test results. The US Core Observation Clinical Result Profile sets minimum expectations to promote interoperability and adoption through common implementation. 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.This profile constrains the FHIR Observation Resource to represent an answer given to a question asked of the patient by the app when recording or uploading their test results.
    • Values Differ
    .experimental
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreObservationClinicalResultProfileObservationPatientQuestionAnswer
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsOrders and Observations
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Observation Clinical Result ProfileObservation - Patient Question Answer
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-resulthttp://hl7.org/fhir/us/home-lab-report/StructureDefinition/Observation-patient-question-answer
                    • Values Differ
                    .version6.0.0-ballot1.0.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. Observation C0..*ObservationMeasurements and simple assertions
                    us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                    C0..*USCoreObservationSurveyProfileSurvey Observation
                    • Elements differ in short: 'Measurements and simple assertions' vs 'Survey Observation'
                    ... 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..*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: ?? (required): Codes providing the status of an observation.

                                          ?!SΣ1..1coderegistered | preliminary | final | amended +
                                          Binding: ?? (required): Codes providing the status of an observation.

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


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


                                            • Elements differ in requirements: 'Used for filtering what observations are retrieved and displayed.' vs 'To identify that observation is derived from a questionnaire.'
                                            ... code SΣ1..1CodeableConceptClinical Test or Procedure Name
                                            Binding: ?? (extensible)
                                            SΣ1..1CodeableConceptQuestions asked of the patient by the app when recording or uploading their at-home in-vitro test results.
                                            Binding: ?? (extensible): Clinical Focus Clinical FocusThis set of values contains concepts representing questions asked of the patient by the app when recording or uploading their at-home in-vitro test results.

                                            • Elements differ in short: 'Clinical Test or Procedure Name' vs 'Questions asked of the patient by the app when recording or uploading their at-home in-vitro test results.'
                                            • Elements differ in definition: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation "name".'
                                            • Elements differ in comments: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a "local" code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.'
                                            • Unable to resolve right value set http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1099.55 at Observation.code
                                            ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is about
                                              ... focus ΣTU0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                              ΣTU0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                                ... encounter Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                                  ... effective[x] SΣC0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                                  us-core-1: Datetime must be at least to day.
                                                  SΣC0..1dateTime S, Period, Timing, instantClinically 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.'
                                                  ... 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 Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core RelatedPerson Profile)Who is responsible for the observation
                                                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                    ... value[x] SΣC0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodResult Value
                                                    us-core-3: SHALL use UCUM for coded quantity units.
                                                    SΣC1..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodAnswer given to a question asked of the patient by the app when recording or uploading their test results.
                                                    • Elements differ in short: 'Result Value' vs 'Answer given to a question asked of the patient by the app when recording or uploading their test results.'
                                                    • Elements differ in definition: 'The clinical test or procedure result value. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM]. A FHIR [UCUM Codes value set] that defines all UCUM codes is in the FHIR specification.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
                                                    • Elements differ in comments: '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] below.' vs 'An observation may have a value if it represents an individual survey question and answer pair. An observation should not have a value if it represents a multi-question survey or multi-select “check all that apply” question. 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.'
                                                    • Element minimum cardinalities differ: '0' vs '1'
                                                    ... dataAbsentReason SC0..1CodeableConceptWhy the result is missing
                                                    Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                    SC0..1CodeableConceptWhy the result is missing
                                                    Binding: ?? (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.'
                                                    ... 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
                                                      0..*AnnotationComments about the observation
                                                        ... bodySite 0..1CodeableConceptObserved body part
                                                        Binding: ?? (example): Codes describing anatomical locations. May include laterality.

                                                        0..1CodeableConceptObserved body part
                                                        Binding: ?? (example): Codes describing anatomical locations. May include laterality.

                                                          ... 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..1Reference(Specimen)Specimen used for this observation
                                                              ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)(Measurement) Device
                                                                ... referenceRange C0..*BackboneElementProvides guide for interpretation
                                                                C0..*BackboneElementProvides guide for interpretation
                                                                  .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                    .... extension 0..*ExtensionAdditional content defined by implementations
                                                                    0..*ExtensionAdditional content defined by implementations
                                                                      .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                      ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                        .... low C0..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Σ0..*Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile | MolecularSequence)Reference to panel or multi-select responses
                                                                                    • Elements differ in short: 'Related resource that belongs to the Observation group' vs 'Reference to panel or multi-select responses'
                                                                                    • 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 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.'
                                                                                    • 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 'This grouping element is used to represent surveys 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. In a survey that has a heirarchical grouping of questions, the observation "panels" can be nested. Because surveys can be arbitrarily complex structurally, not all survey structures can be represented using this Observation grouping pattern.'
                                                                                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                    ... derivedFrom Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                    SΣ0..*Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile S | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence)Related Observations or QuestionnaireResponses that the observation is made from
                                                                                    • Elements differ in short: 'Related measurements the observation is made from' vs 'Related Observations or QuestionnaireResponses that the observation is made from'
                                                                                    • Elements differ in definition: '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.' vs 'Observations or QuestionnaireResponses from which this observation value is derived.'
                                                                                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                    • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], 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]])
                                                                                    ... component Σ0..*BackboneElementComponent results
                                                                                    Σ0..*BackboneElementComponent results
                                                                                      .... 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