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

Left:US Core Screening Response Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response)
Right:SDOHCC Observation Race (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationRace)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationRace'
ErrorStructureDefinition.versionValues for version differ: '4.1.0' vs '1.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationScreeningResponse' vs 'SDOHCCObservationRace'
InformationStructureDefinition.titleValues for title differ: 'US Core Screening Response Observation Profile' vs 'SDOHCC Observation Race'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2021-11-12' vs '2021-12-07T14:30:02+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Patient Care WG'
WarningObservationElements differ in short: 'questionnaire observations' 'Race observation'
WarningObservationElements differ in definition: 'For Observations derived from surveys/questionnaires.' 'For observations about the race of an individual.'
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).' '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.extensionElements differ in short: 'Additional content defined by implementations' 'Extension'
WarningObservation.extensionElements differ in definition: '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.' 'An Extension'
WarningObservation.categoryElements differ in requirements: 'To identify that observation is derived from a questionnaire.' 'Used for filtering what observations are retrieved and displayed.'
ErrorObservation.categoryElements differ in definition for mustSupport: 'true' 'false'
InformationObservation.codeExample/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningResponse
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'.' '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.' '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.'
ErrorObservation.effective[x]Elements differ in definition for mustSupport: 'true' '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.' '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.'
ErrorObservation.value[x]Elements differ in definition for mustSupport: 'true' 'false'
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.' '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.'
ErrorObservation.methodElements differ in definition for mustSupport: 'false' 'true'
WarningObservation.derivedFromElements differ in short: 'Related questionnaire responses or observations that the observation is made from' 'Related measurements the observation is made from'
WarningObservation.derivedFromElements differ in definition: 'Questionnaire responses or observations from which this observation value is derived.' '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-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]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], 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.' 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes.'
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.' 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below.'
WarningObservation.componentElements differ in requirements: '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.' '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).'
ErrorObservation.component.codeElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.component.value[x]Elements differ in comments: 'see `Observation.value[x]` comments' '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.'
ErrorObservation.component.value[x]Elements differ in definition for mustSupport: 'true' 'false'
WarningObservation.component.dataAbsentReasonElements differ in comments: 'see `Observation.dataAbsentReason` 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 '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.'
ErrorObservation.component.dataAbsentReasonElements differ in definition for mustSupport: 'true' 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Observation
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2021-11-122021-12-07T14:30:02+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.Profile for observations about race using Office of Management and Budget (OMB) race category codes and CDC race codes. This profile is intended for draft use only. The Cross-Group Projects work group granted an exception to US Core on 11/18/2021 - Jira ticket 34245.
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreObservationScreeningResponseSDOHCCObservationRace
                • Values Differ
                .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
                • Values Differ
                .purpose
                  .statusactivedraft
                  • Values Differ
                  .titleUS Core Screening Response Observation ProfileSDOHCC Observation Race
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-responsehttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationRace
                    • Values Differ
                    .version4.1.01.1.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. Observation II
                    • Elements differ in short: "questionnaire observations" "Race observation"
                    • Elements differ in definition: "For Observations derived from surveys/questionnaires." "For observations about the race of an individual."
                    • 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)." "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 ΣΣ
                      ... meta ΣΣ
                        ... implicitRules ?!Σ?!Σ
                          ... language
                            ... text
                              ... contained
                                ... extension ExtensionExtension
                                • Elements differ in short: "Additional content defined by implementations" "Extension"
                                • Elements differ in definition: "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." "An Extension"
                                ... modifierExtension ?!?!
                                  ... identifier ΣΣ
                                    ... basedOn ΣΣ
                                      ... partOf ΣΣ
                                        ... status ?!SΣ?!SΣ
                                          ... Slices for category S
                                          • Elements differ in requirements: "To identify that observation is derived from a questionnaire." "Used for filtering what observations are retrieved and displayed."
                                          • Elements differ in definition for mustSupport: "true" "false"
                                          ... code SΣSΣ
                                          • Example/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningResponse
                                          ... subject SΣSΣI
                                            ... focus ΣΣI
                                              ... encounter ΣΣ
                                                ... effective[x] SΣIΣ
                                                • 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"." "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." "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."
                                                • Elements differ in definition for mustSupport: "true" "false"
                                                ... issued ΣΣ
                                                  ... performer SΣSΣ
                                                    ... value[x] SΣIΣI
                                                    • 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." "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."
                                                    • Elements differ in definition for mustSupport: "true" "false"
                                                    ... dataAbsentReason SISI
                                                    • 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." "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."
                                                    ... interpretation
                                                      ... note
                                                        ... bodySite
                                                          ... method S
                                                          • Elements differ in definition for mustSupport: "false" "true"
                                                          ... specimen
                                                            ... device
                                                              ... referenceRange II
                                                                .... id
                                                                  .... extension ExtensionExtension
                                                                    .... modifierExtension ?!Σ?!Σ
                                                                      .... low II
                                                                        .... high II
                                                                          .... type
                                                                            .... appliesTo
                                                                              .... age
                                                                                .... text
                                                                                  ... hasMember ΣΣ
                                                                                    ... derivedFrom SΣSΣ
                                                                                    • Elements differ in short: "Related questionnaire responses or observations that the observation is made from" "Related measurements the observation is made from"
                                                                                    • Elements differ in definition: "Questionnaire responses or observations from which this observation value is derived." "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."
                                                                                    • 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]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
                                                                                    ... component SΣSΣI
                                                                                    • 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." "Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes."
                                                                                    • 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." "For a discussion on the ways Observations can be assembled in groups together see [Notes] below."
                                                                                    • Elements differ in requirements: "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." "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)."
                                                                                    .... id
                                                                                      .... extension ExtensionExtension
                                                                                        .... modifierExtension ?!Σ?!Σ
                                                                                          .... code SΣΣ
                                                                                          • Elements differ in definition for mustSupport: "true" "false"
                                                                                          .... value[x] SΣIΣ
                                                                                          • Elements differ in comments: "see `Observation.value[x]` comments" "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" "false"
                                                                                          .... dataAbsentReason SII
                                                                                          • Elements differ in comments: "see `Observation.dataAbsentReason` 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 "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" "false"
                                                                                          .... interpretation
                                                                                            .... referenceRange

                                                                                              doco Documentation for this format