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

Left:US Core Smoking Status Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-smokingstatus)
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-smokingstatus' 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: 'USCoreSmokingStatusProfile' vs 'SDOHCCObservationRace'
InformationStructureDefinition.titleValues for title differ: 'US Core Smoking Status Observation Profile' vs 'SDOHCC Observation Race'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2019-05-21T00:00:00+00:00' 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: 'Measurements and simple assertions' 'Race observation'
WarningObservationElements differ in definition: 'The US Core Smoking Status Observation Profile is based upon the core FHIR Observation Resource and created to meet the USCDI Data Set 'Smoking status' requirements.' 'For observations about the race of an individual.'
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'
ErrorObservation.categoryElements differ in definition for mustSupport: 'true' 'false'
WarningObservation.codeElements differ in short: 'Smoking Status' 'Type of observation (code / type)'
ErrorObservation.performerElements differ in definition for mustSupport: 'false' 'true'
ErrorObservation.value[x]Cardinality Mismatch: 1..1/0..0
WarningObservation.dataAbsentReasonElements differ in comments: 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be 'detected', 'not detected', 'inconclusive', or 'specimen unsatisfactory'. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code 'error' could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' '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.dataAbsentReasonElements differ in definition for mustSupport: 'false' 'true'
ErrorObservation.methodElements differ in definition for mustSupport: 'false' 'true'
ErrorObservation.derivedFromElements differ in definition for mustSupport: 'false' 'true'
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 include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.' '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 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.componentElements differ in definition for mustSupport: 'false' 'true'

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'
      .date2019-05-21T00:00:00+00:002021-12-07T14:30:02+00:00
      • Values Differ
      .descriptionDefines constraints and extensions on the Observation resource for the minimal set of data to query and retrieve patient's Smoking Status information.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
      .experimentalfalse
      • Removed the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreSmokingStatusProfileSDOHCCObservationRace
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
              • Values Differ
              .purpose
                .statusactivedraft
                • Values Differ
                .titleUS Core Smoking Status Observation ProfileSDOHCC Observation Race
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-smokingstatushttp://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: "Measurements and simple assertions" "Race observation"
                  • Elements differ in definition: "The US Core Smoking Status Observation Profile is based upon the core FHIR Observation Resource and created to meet the USCDI Data Set 'Smoking status' requirements." "For observations about the race of an individual."
                  ... 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 definition for mustSupport: "true" "false"
                                        ... code SΣSΣ
                                        • Elements differ in short: "Smoking Status" "Type of observation (code / type)"
                                        ... subject SΣSΣI
                                          ... focus ΣΣI
                                            ... encounter ΣΣ
                                              ... Slices for effective[x] ΣΣ
                                                ... issued ΣΣ
                                                  ... performer ΣSΣ
                                                  • Elements differ in definition for mustSupport: "false" "true"
                                                  ... Slices for value[x] ΣIΣI
                                                  • Cardinality Mismatch: 1..1/0..0
                                                  ... dataAbsentReason ISI
                                                  • 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." "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."
                                                  • Elements differ in definition for mustSupport: "false" "true"
                                                  ... 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Σ
                                                                                  • Elements differ in definition for mustSupport: "false" "true"
                                                                                  ... component Σ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 include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations." "Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes."
                                                                                  • 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)."
                                                                                  • Elements differ in definition for mustSupport: "false" "true"
                                                                                  .... id
                                                                                    .... extension ExtensionExtension
                                                                                      .... modifierExtension ?!Σ?!Σ
                                                                                        .... code ΣΣ
                                                                                          .... value[x] ΣΣ
                                                                                            .... dataAbsentReason II
                                                                                              .... interpretation
                                                                                                .... referenceRange

                                                                                                  doco Documentation for this format