Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response vs http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-comorbidities-elixhauser

Left:US Core Screening Response Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response)
Right:Comorbidities Elixhauser Profile (http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-comorbidities-elixhauser)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response' vs 'http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-comorbidities-elixhauser'
ErrorStructureDefinition.versionValues for version differ: '4.1.0' vs '2.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationScreeningResponse' vs 'ComorbiditiesElixhauser'
InformationStructureDefinition.titleValues for title differ: 'US Core Screening Response Observation Profile' vs 'Comorbidities Elixhauser Profile'
InformationStructureDefinition.dateValues for date differ: '2021-11-12' vs '2022-01-18T03:17:40+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International Clinical Interoperability Council'
ErrorStructureDefinition.baseDefinitionValues for baseDefinition differ: 'http://hl7.org/fhir/StructureDefinition/Observation' vs 'http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-comorbidities-parent'
WarningObservationElements differ in short: 'questionnaire observations' vs 'Measurements and simple assertions'
WarningObservationElements differ in definition: 'For Observations derived from surveys/questionnaires.' vs 'Measurements and simple assertions made about a patient, device or other subject.'
WarningObservationElements differ in comments: '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).' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
WarningObservation.categoryElements differ in requirements: 'To identify that observation is derived from a questionnaire.' vs 'Used for filtering what observations are retrieved and displayed.'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.categoryElement minimum cardinalities differ: '1' vs '0'
InformationObservation.codeExample/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningResponse
WarningObservation.subjectElements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'The patient whose comorbidities are recorded.'
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
WarningObservation.focusElements differ in short: 'What the observation is about, when it is not about the subject of record' vs 'The Index Condition'
WarningObservation.focusElements differ in definition: 'The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.' vs 'A reference to the cancer condition that is the context for the current list of comorbid conditions.'
WarningObservation.focusElements differ in definition for mustSupport: 'false' vs 'true'
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'.' 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.'
WarningObservation.effective[x]Elements differ in comments: '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] datatype which allow the measurement to be tied to regular life events.'
WarningObservation.performerElements differ in definition for mustSupport: 'true' vs 'false'
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.' 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] below.'
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. 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'
WarningObservation.bodySiteElements differ in short: 'Observed body part' vs 'Not used in this profile'
WarningObservation.bodySiteElements differ in definition: 'Indicates the site on the subject's body where the observation was made (i.e. the target site).' vs 'Not used in this profile'
WarningObservation.specimenElements differ in short: 'Specimen used for this observation' vs 'Not used in this profile'
WarningObservation.specimenElements differ in definition: 'The specimen that was used when this observation was made.' vs 'Not used in this profile'
WarningObservation.deviceElements differ in short: '(Measurement) Device' vs 'Not used in this profile'
WarningObservation.deviceElements differ in definition: 'The device used to generate the observation data.' vs 'Not used in this profile'
WarningObservation.derivedFromElements differ in short: 'Related questionnaire responses or observations that the observation is made from' vs 'Related measurements the observation is made from'
WarningObservation.derivedFromElements differ in definition: 'Questionnaire responses or observations 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.'
WarningObservation.derivedFromElements differ in definition for mustSupport: 'true' vs 'false'
ErrorObservation.derivedFromType Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response], CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-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/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]])
WarningObservation.componentElements differ in definition: 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples: Individuals may be multiracial. Component is used to capture one or more races.' vs 'Component representing the presence or absence of the named comorbidity, with optional condition code(s) or reference to the actual condition(s).'
WarningObservation.componentElements differ in comments: 'For 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.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below.'
WarningObservation.component.extensionElements differ in short: 'Additional content defined by implementations' vs 'Extensions to capture specific conditions that fall into the given category.'
WarningObservation.component.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. 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 'If more detail about the comorbid condition is desired, elements in this extension can be populated with a specific condition code or a reference to a Condition resource. The extension elements SHALL be used only if the comorbidity category is present.'
WarningObservation.component.modifierExtensionElements differ in short: 'Extensions that cannot be ignored even if unrecognized' vs 'Extension'
WarningObservation.component.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
InformationObservation.component.modifierExtensionElement maximum cardinalities differ: '2147483647' vs '0'
WarningObservation.component.codeElements differ in short: 'Type of component observation (code / type)' vs 'Code representing the comorbidity category'
WarningObservation.component.codeElements differ in definition: 'Describes what was observed. Sometimes this is called the observation 'code'.' vs 'The code identifying category of comorbidity, for example, congestive heart failure or severe renal disease. The category typically represents a set of specific diagnosis codes.'
WarningObservation.component.codeElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.value[x]Elements differ in comments: 'see `Observation.value[x]` comments' vs 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). 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.'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.component.dataAbsentReasonElements differ in comments: 'see `Observation.dataAbsentReason` comments' 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 'test not done'. 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. Because of these options, use-case agreements are required to interpret general observations for exceptional values.'
WarningObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observationhttp://hl7.org/fhir/us/mcode/StructureDefinition/mcode-comorbidities-parent
    • 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'
    .date2021-11-122022-01-18T03:17:40+00:00
    • Values Differ
    .descriptionProfile for observations that represent question and answer pairs from from surveys/questionnaires such as Social Determinants of Health (SDOH) screening instruments.Comorbid condition checklist and optional risk score, using Elixhauser comorbidity categories as defined by the Agency for Healthcare Research and Quality (AHRQ) Healthcare Cost and Utilization Project (H-CUP).
    • Values Differ
    .experimental
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreObservationScreeningResponseComorbiditiesElixhauser
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 International Clinical Interoperability Council
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Screening Response Observation ProfileComorbidities Elixhauser Profile
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-responsehttp://hl7.org/fhir/us/mcode/StructureDefinition/mcode-comorbidities-elixhauser
                    • Values Differ
                    .version4.1.02.0.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. Observation I0..*Observationquestionnaire observations
                    us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                    I0..*ComorbiditiesParentMeasurements and simple assertions
                    • Elements differ in short: 'questionnaire observations' vs 'Measurements and simple assertions'
                    • Elements differ in definition: 'For Observations derived from surveys/questionnaires.' vs 'Measurements and simple assertions made about a patient, device or other subject.'
                    • Elements differ in comments: '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).' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
                    ... id Σ0..1stringLogical id of this artifactΣ0..1stringLogical 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)
                          Max Binding: AllLanguages: A human language.

                          0..1codeLanguage of the resource content
                          Binding: CommonLanguages (preferred)
                          Max Binding: AllLanguages: A human language.

                            ... 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: ObservationStatus (required): Codes providing the status of an observation.

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

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


                                            0..*CodeableConceptClassification of type of observation
                                            Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.


                                            • Elements differ in requirements: 'To identify that observation is derived from a questionnaire.' vs 'Used for filtering what observations are retrieved and displayed.'
                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                            • Element minimum cardinalities differ: '1' vs '0'
                                            ... code SΣ1..1CodeableConceptType of observation (code / type)
                                            Binding: US Core Common SDOH Assessments ValueSet (preferred)
                                            SΣ1..1CodeableConceptType of observation (code / type)
                                            Binding: LOINCCodes (example): Codes identifying names of simple observations.


                                            Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/us/mcode/CodeSystem/loinc-requested-cs","code":"comorbidities-elixhauser","display":"Elixhauser Comorbidity Panel"}]}
                                            • Example/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningResponse
                                            ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutSΣ0..1Reference(Cancer Patient Profile)Who and/or what the observation is about
                                            • Elements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'The patient whose comorbidities are recorded.'
                                            • 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
                                            SΣ0..*Reference(Primary Cancer Condition Profile)The Index Condition
                                            • Elements differ in short: 'What the observation is about, when it is not about the subject of record' vs 'The Index Condition'
                                            • Elements differ in definition: 'The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.' vs 'A reference to the cancer condition that is the context for the current list of comorbid conditions.'
                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                            ... 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ΣI0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                              us-core-1: Datetime must be at least to day.
                                              SΣ0..1dateTime, 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".' 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.'
                                              • Elements differ in comments: '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] datatype which allow the measurement to be tied to regular life events.'
                                              ... 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 S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core Related Person)Who is responsible for the observation
                                                Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                ... value[x] SΣI0..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ΣI0..1integerActual result
                                                • 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.' 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] below.'
                                                ... dataAbsentReason SI0..1CodeableConceptWhy the result is missing
                                                Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                I0..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. 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.'
                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                ... 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..1CodeableConceptNot used in this profile
                                                    Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

                                                    • Elements differ in short: 'Observed body part' vs 'Not used in this profile'
                                                    • Elements differ in definition: 'Indicates the site on the subject's body where the observation was made (i.e. the target site).' vs 'Not used in this profile'
                                                    ... 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..1Reference(Specimen)Not used in this profile
                                                      • Elements differ in short: 'Specimen used for this observation' vs 'Not used in this profile'
                                                      • Elements differ in definition: 'The specimen that was used when this observation was made.' vs 'Not used in this profile'
                                                      ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)Not used in this profile
                                                      • Elements differ in short: '(Measurement) Device' vs 'Not used in this profile'
                                                      • Elements differ in definition: 'The device used to generate the observation data.' vs 'Not used in this profile'
                                                      ... referenceRange I0..*BackboneElementProvides guide for interpretation
                                                      obs-3: Must have at least a low or a high or text
                                                      I0..*BackboneElementProvides guide for interpretation
                                                      obs-3: Must have at least a low or a high or text
                                                        .... 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 I0..1SimpleQuantityLow Range, if relevantI0..1SimpleQuantityLow Range, if relevant
                                                                .... high I0..1SimpleQuantityHigh Range, if relevantI0..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
                                                                            ... derivedFrom SΣ0..*Reference(US Core Screening Response Observation Profile S | http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse S | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence)Related questionnaire responses or observations that the observation is made from
                                                                            Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                            • Elements differ in short: 'Related questionnaire responses or observations that the observation is made from' vs 'Related measurements the observation is made from'
                                                                            • Elements differ in definition: 'Questionnaire responses or observations 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.'
                                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                            • Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response], CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-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/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]])
                                                                            ... component SΣ0..*BackboneElementComponent results
                                                                            SΣ0..*BackboneElementComponent results
                                                                            Slice: Unordered, Closed by pattern:code
                                                                            • Elements differ in definition: 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples: Individuals may be multiracial. Component is used to capture one or more races.' vs 'Component representing the presence or absence of the named comorbidity, with optional condition code(s) or reference to the actual condition(s).'
                                                                            • Elements differ in comments: 'For 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.' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below.'
                                                                            .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                              .... extension 0..*ExtensionAdditional content defined by implementations
                                                                              0..*ExtensionExtensions to capture specific conditions that fall into the given category.
                                                                              Slice: Unordered, Open by value:url
                                                                              • Elements differ in short: 'Additional content defined by implementations' vs 'Extensions to capture specific conditions that fall into the given category.'
                                                                              • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. 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 'If more detail about the comorbid condition is desired, elements in this extension can be populated with a specific condition code or a reference to a Condition resource. The extension elements SHALL be used only if the comorbidity category is present.'
                                                                              .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                              ?!Σ0..0
                                                                              • Elements differ in short: 'Extensions that cannot be ignored even if unrecognized' vs 'Extension'
                                                                              • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'An Extension'
                                                                              • Element maximum cardinalities differ: '2147483647' vs '0'
                                                                              .... code SΣ1..1CodeableConceptType of component observation (code / type)
                                                                              Binding: LOINCCodes (extensible)
                                                                              Σ1..1CodeableConceptCode representing the comorbidity category
                                                                              Binding: LOINCCodes (example): Codes identifying names of simple observations.

                                                                              • Elements differ in short: 'Type of component observation (code / type)' vs 'Code representing the comorbidity category'
                                                                              • Elements differ in definition: 'Describes what was observed. Sometimes this is called the observation "code".' vs 'The code identifying category of comorbidity, for example, congestive heart failure or severe renal disease. The category typically represents a set of specific diagnosis codes.'
                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              .... value[x] SΣI0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component result
                                                                              us-core-3: SHALL use UCUM for coded quantity units.
                                                                              Σ0..1CodeableConceptActual component result
                                                                              Binding: Present Absent Value Set (required)
                                                                              • Elements differ in comments: 'see `Observation.value[x]` comments' vs 'Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). 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.'
                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              .... dataAbsentReason SI0..1CodeableConceptWhy the component result is missing
                                                                              Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                              I0..1CodeableConceptWhy the component result is missing
                                                                              Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

                                                                              • Elements differ in comments: 'see `Observation.dataAbsentReason` comments' 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 "test not done". 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. Because of these options, use-case agreements are required to interpret general observations for exceptional values.'
                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              .... 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