Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicity

Left:US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab)
Right:SDOHCC Observation Ethnicity (http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicity)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicity'
ErrorStructureDefinition.versionValues for version differ: '4.1.0' vs '1.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'SDOHCCObservationEthnicity'
InformationStructureDefinition.titleValues for title differ: 'US Core Laboratory Result Observation Profile' vs 'SDOHCC Observation Ethnicity'
InformationStructureDefinition.statusValues for status differ: 'active' vs 'draft'
InformationStructureDefinition.dateValues for date differ: '2020-06-27' 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' 'Ethnicity observation'
WarningObservationElements differ in definition: 'This profile is created to meet the 2015 Edition Common Clinical Data Set 'Laboratory test(s) and Laboratory value(s)/result(s)' requirements.' 'For observations about the ethnicity 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: 'Laboratory Test Name' 'Type of observation (code / type)'
WarningObservation.codeElements differ in definition: 'The test that was performed. A LOINC **SHALL** be used if the concept is present in LOINC.' 'Describes what was observed. Sometimes this is called the observation 'name'.'
WarningObservation.codeElements differ in comments: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.'
WarningObservation.codeElements differ in binding.description: 'LOINC codes' 'Codes identifying names of simple observations.'
WarningObservation.effective[x]Elements differ in definition: 'For lab tests this is the specimen collection date. For Ask at Order Entry Questions (AOE)'s this is the date the question was asked.' '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.'
ErrorObservation.effective[x]Elements differ in definition for mustSupport: 'true' 'false'
ErrorObservation.performerElements differ in definition for mustSupport: 'false' 'true'
WarningObservation.value[x]Elements differ in short: 'Result Value' 'Actual result'
WarningObservation.value[x]Elements differ in definition: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT] if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM]. A FHIR [UCUM Codes value set] that defines all UCUM codes is in the FHIR specification.' 'The information determined as a result of making the observation, if the information has a simple value.'
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. 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.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'
      .date2020-06-272021-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 laboratory test resultsProfile for observations about ethnicity using Office of Management and Budget (OMB) ethnicity category codes and CDC ethnicity 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
              .nameUSCoreLaboratoryResultObservationProfileSDOHCCObservationEthnicity
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 International - Patient Care WG
              • Values Differ
              .purpose
                .statusactivedraft
                • Values Differ
                .titleUS Core Laboratory Result Observation ProfileSDOHCC Observation Ethnicity
                • Values Differ
                .typeObservation
                  .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-labhttp://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationEthnicity
                  • 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" "Ethnicity observation"
                  • Elements differ in definition: "This profile is created to meet the 2015 Edition Common Clinical Data Set 'Laboratory test(s) and Laboratory value(s)/result(s)' requirements." "For observations about the ethnicity 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: "Laboratory Test Name" "Type of observation (code / type)"
                                        • Elements differ in definition: "The test that was performed. A LOINC **SHALL** be used if the concept is present in LOINC." "Describes what was observed. Sometimes this is called the observation "name"."
                                        • Elements differ in comments: "The typical patterns for codes are: 1) a LOINC code either as a translation from a "local" code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display." "*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation."
                                        • Elements differ in binding.description: "LOINC codes" "Codes identifying names of simple observations."
                                        ... subject SΣSΣI
                                          ... focus ΣΣI
                                            ... encounter ΣΣ
                                              ... effective[x] SΣIΣ
                                              • Elements differ in definition: "For lab tests this is the specimen collection date. For Ask at Order Entry Questions (AOE)'s this is the date the question was asked." "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 definition for mustSupport: "true" "false"
                                              ... issued ΣΣ
                                                ... performer ΣSΣI
                                                • Elements differ in definition for mustSupport: "false" "true"
                                                ... value[x] SΣIΣI
                                                • Elements differ in short: "Result Value" "Actual result"
                                                • Elements differ in definition: "The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT] if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM]. A FHIR [UCUM Codes value set] that defines all UCUM codes is in the FHIR specification." "The information determined as a result of making the observation, if the information has a simple value."
                                                • 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. 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."
                                                ... 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ΣI
                                                                                • 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