Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaging vs http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation

Left:US Core Observation Imaging Result Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaging)
Right:eICR Processing Status Reason Observation (http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaging' vs 'http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation'
ErrorStructureDefinition.versionValues for version differ: '5.0.1' vs '2.1.0'
InformationStructureDefinition.nameValues for name differ: 'USCoreObservationImagingResultProfile' vs 'RR_Eicr_Processing_Status_Reason_Observation'
InformationStructureDefinition.titleValues for title differ: 'US Core Observation Imaging Result Profile' vs 'eICR Processing Status Reason Observation'
InformationStructureDefinition.dateValues for date differ: '2022-04-20' vs '2022-08-31T17:40:18+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 Public Health Work Group (http://www.hl7.org/Special/committees/pher/index.cfm)'
WarningObservationElements differ in short: 'Measurements and simple assertions' vs 'eICR Processing Status Reason'
WarningObservationElements differ in definition: '\-' vs 'If the incoming eICR was not successfully processed for a determination of reportability, contains the reason it was not processed. If any of the trigger codes used to generate the eICR are from an outdated version of the RCTC or the codes are marked as inactive in the latest version fo the RCTC, these are flagged and compoent observations will hold the details of the outdated and expected versions of the RCTC.'
WarningObservationElements differ in comments: '\-' 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.'
WarningObservationElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.statusElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.categoryElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.categoryElement minimum cardinalities differ: '1' vs '0'
WarningObservation.codeElements differ in short: 'Imaging Name' vs 'Type of observation (code / type)'
WarningObservation.codeElements differ in definition: 'The name of the imaging test performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.'
WarningObservation.codeElements differ in comments: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.'
WarningObservation.codeElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.subjectElements differ in definition for mustSupport: 'true' vs 'false'
InformationObservation.subjectElement minimum cardinalities differ: '1' vs '0'
WarningObservation.effective[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.value[x]Elements differ in short: 'Result Value' vs 'Processing status reason'
WarningObservation.value[x]Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'If the incoming eICR was not successfully processed for a determination of reportability, contains the reason it was not processed.'
WarningObservation.value[x]Elements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.dataAbsentReasonElements differ in definition for mustSupport: 'true' vs 'false'
WarningObservation.componentElements differ in short: 'Component results' vs 'eICR Processing Status Reason Detail'
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.' vs 'Further details about eICR processing status warnings or errors. If any of the trigger codes used to generate the eICR are from an outdated version of the RCTC or the codes are marked as inactive in the latest version of the RCTC, will contain the details of the outdated and expected versions of the RCTC.'
WarningObservation.componentElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.component.codeElements differ in short: 'Type of component observation (code / type)' vs 'Type of processing status reason detail'
WarningObservation.component.codeElements differ in definition for mustSupport: 'false' vs 'true'
WarningObservation.component.codeElements differ in binding.description: 'Codes identifying names of simple observations.' vs 'Processing Status Reason Detail Type'
WarningObservation.component.value[x]Elements differ in short: 'Actual component result' vs 'Processing status reason detail'
WarningObservation.component.value[x]Elements differ in definition for mustSupport: 'false' vs 'true'
InformationObservation.component.value[x]Element minimum cardinalities differ: '0' vs '1'

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'
      .date2022-04-202022-08-31T17:40:18+00:00
      • Values Differ
      .descriptionThe US Core Observation Imaging Result Profile is based upon the core FHIR Observation Resource, and, along with the US Core DiagnosticReport Profile for Report and Note exchange, meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Diagnostic Imaging’ requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch retrieve structured and unstructured (narrative) components of diagnostic imaging test results for a patient. These observations include reasons, findings, and impressions. It provides the floor for standards development for specific uses cases.This Observation profile represents, if the incoming eICR was not successfully processed for a determination of reportability, the reason it was not processed.
      • Values Differ
      .experimentalfalse
      • Added the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCoreObservationImagingResultProfileRR_Eicr_Processing_Status_Reason_Observation
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 Public Health Work Group (http://www.hl7.org/Special/committees/pher/index.cfm)
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Observation Imaging Result ProfileeICR Processing Status Reason Observation
                  • Values Differ
                  .typeObservation
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-imaginghttp://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation
                    • Values Differ
                    .version5.0.12.1.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. Observation I0..*ObservationMeasurements and simple assertions
                    us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present
                    SI0..*ObservationeICR Processing Status Reason
                    • Elements differ in short: 'Measurements and simple assertions' vs 'eICR Processing Status Reason'
                    • Elements differ in definition: '\-' vs 'If the incoming eICR was not successfully processed for a determination of reportability, contains the reason it was not processed. If any of the trigger codes used to generate the eICR are from an outdated version of the RCTC or the codes are marked as inactive in the latest version fo the RCTC, these are flagged and compoent observations will hold the details of the outdated and expected versions of the RCTC.'
                    • Elements differ in comments: '\-' 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.'
                    • Elements differ in definition for mustSupport: 'false' vs 'true'
                    ... 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): A human language.

                          Additional BindingsPurpose
                          AllLanguagesMax Binding
                          0..1codeLanguage of the resource content
                          Binding: CommonLanguages (preferred): A human language.

                          Additional BindingsPurpose
                          AllLanguagesMax Binding
                            ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                              ... contained 0..*ResourceContained, inline Resources
                              0..*ResourceContained, inline Resources
                                ... extension 0..*ExtensionAdditional content defined by implementations
                                0..*ExtensionAdditional content defined by implementations
                                  ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                  ?!0..*ExtensionExtensions that cannot be ignored
                                    ... identifier Σ0..*IdentifierBusiness Identifier for observation
                                    Σ0..*IdentifierBusiness Identifier for observation
                                      ... basedOn Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                      Σ0..*Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)Fulfills plan, proposal or order
                                        ... partOf Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                        Σ0..*Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)Part of referenced event
                                          ... status ?!SΣ1..1coderegistered | preliminary | final | amended +
                                          Binding: ObservationStatus (required): Codes providing the status of an observation.

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


                                          Fixed Value: final
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... 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 definition for mustSupport: 'true' vs 'false'
                                          • Element minimum cardinalities differ: '1' vs '0'
                                          ... code SΣ1..1CodeableConceptImaging Name
                                          Binding: US Core DiagnosticReport Report And Note Codes (extensible)
                                          Σ1..1CodeableConceptType of observation (code / type)
                                          Binding: LOINCCodes (example): Codes identifying names of simple observations.


                                          Required Pattern: {"coding":[{"system":"urn:oid:2.16.840.1.114222.4.5.232","code":"RR6","display":"eICR Processing Status Reason"}]}
                                          • Elements differ in short: 'Imaging Name' vs 'Type of observation (code / type)'
                                          • Elements differ in definition: 'The name of the imaging test performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation "name".'
                                          • Elements differ in comments: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a "local" code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.'
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          ... subject SΣ1..1Reference(US Core Patient Profile)Who and/or what the observation is aboutΣ0..1Reference(Patient | Group | Device | Location)Who and/or what the observation is about
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          • 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
                                          Σ0..*Reference(Resource)What the observation is about, when it is not about the subject of record
                                            ... encounter Σ0..1Reference(Encounter)Healthcare event during which this observation is madeΣ0..1Reference(Encounter)Healthcare event during which this observation is made
                                              ... effective[x] SΣI0..1dateTime S, Period, Timing, instantClinically relevant time/time-period for observation
                                              us-core-1: Datetime must be at least to day.
                                              Σ0..1dateTime, Period, Timing, instantClinically relevant time/time-period for observation
                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                              ... issued Σ0..1instantDate/Time this version was made availableΣ0..1instantDate/Time this version was made available
                                                ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)Who is responsible for the observation
                                                  ... value[x] SΣI0..1Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodResult Value
                                                  us-core-3: SHALL use UCUM for coded quantity units.
                                                  ΣI0..1CodeableConceptProcessing status reason
                                                  Binding: eICR Processing Status Reason (eCR) (extensible): Processing Status Reason


                                                  Example Example for CodeableConcept: {"coding":[{"system":"urn:oid:2.16.840.1.114222.4.5.274","code":"RRVS30","display":"eICR was processed with the warning of: inactive RCTC code"}]}
                                                  • Elements differ in short: 'Result Value' vs 'Processing status reason'
                                                  • Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'If the incoming eICR was not successfully processed for a determination of reportability, contains the reason it was not processed.'
                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                  ... 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 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..1CodeableConceptObserved body part
                                                      Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

                                                        ... 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)Specimen used for this observation
                                                            ... device 0..1Reference(Device | DeviceMetric)(Measurement) Device0..1Reference(Device | DeviceMetric)(Measurement) Device
                                                              ... referenceRange I0..*BackboneElementProvides guide for interpretation
                                                              I0..*BackboneElementProvides guide for interpretation
                                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                                  0..*ExtensionAdditional content defined by implementations
                                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                    ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                      .... low 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 Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                    Σ0..*Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)Related measurements the observation is made from
                                                                                      ... component Σ0..*BackboneElementComponent results
                                                                                      SΣ0..*BackboneElementeICR Processing Status Reason Detail
                                                                                      • Elements differ in short: 'Component results' vs 'eICR Processing Status Reason Detail'
                                                                                      • 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.' vs 'Further details about eICR processing status warnings or errors. If any of the trigger codes used to generate the eICR are from an outdated version of the RCTC or the codes are marked as inactive in the latest version of the RCTC, will contain the details of the outdated and expected versions of the RCTC.'
                                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                        .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                        0..*ExtensionAdditional content defined by implementations
                                                                                          .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                          ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                            .... code Σ1..1CodeableConceptType of component observation (code / type)
                                                                                            Binding: LOINCCodes (example): Codes identifying names of simple observations.

                                                                                            SΣ1..1CodeableConceptType of processing status reason detail
                                                                                            Binding: eICR Processing Status Reason Detail Type (eCR) (extensible): Processing Status Reason Detail Type


                                                                                            Example General: {"coding":[{"system":"urn:oid:2.16.840.1.114222.4.5.274","code":"RRVS32","display":"Inactive RCTC code detail"}]}
                                                                                            • Elements differ in short: 'Type of component observation (code / type)' vs 'Type of processing status reason detail'
                                                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                            • Elements differ in binding.description: 'Codes identifying names of simple observations.' vs 'Processing Status Reason Detail Type'
                                                                                            .... value[x] Σ0..1Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, PeriodActual component resultSΣ1..1CodeableConcept, stringProcessing status reason detail
                                                                                            Example General: {"coding":[{"system":"http://snomed.info/sct","code":"69092001","display":"Leptospirosis icterohemorrhagica (disorder)"}]}
                                                                                            • Elements differ in short: 'Actual component result' vs 'Processing status reason detail'
                                                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                                            • Element minimum cardinalities differ: '0' vs '1'
                                                                                            .... dataAbsentReason I0..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.

                                                                                              .... 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