Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note vs http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note

Left:US Core DiagnosticReport Profile for Report and Note exchange (http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note)
Right:US Core DiagnosticReport Profile for Report and Note Exchange (http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note)

Messages

ErrorStructureDefinition.versionValues for version differ: '3.1.1' vs '6.0.0-ballot'
InformationStructureDefinition.titleValues for title differ: 'US Core DiagnosticReport Profile for Report and Note exchange' vs 'US Core DiagnosticReport Profile for Report and Note Exchange'
InformationStructureDefinition.dateValues for date differ: '2019-05-21' vs '2022-04-20'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 US Realm Steering Committee' vs 'HL7 International - Cross-Group Projects'
WarningDiagnosticReportElements differ in short: 'US Core Diagnostic Report Profile for Report and Note exchange' vs 'A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports'
WarningDiagnosticReportElements differ in definition: 'The US Core Diagnostic Report Profile for Report and Note exchange is based upon the requirements of the Argonauts to exchang imaginge reports.' vs '\-'
WarningDiagnosticReportElements differ in comments: 'This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.' vs '\-'
WarningDiagnosticReport.codeElements differ in comments: 'UsageNote= 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.' vs '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.'
WarningDiagnosticReport.subjectElements differ in definition: 'The subject of the report. Usually, but not always, this is a patient. However diagnostic services also perform analyses on specimens collected from a variety of other sources.' vs 'The subject of the report. Usually, but not always, this is a patient. However, diagnostic services also perform analyses on specimens collected from a variety of other sources.'
WarningDiagnosticReport.effective[x]Elements differ in short: 'Time of the report or note' vs 'Diagnostically relevant time (typically the time of the procedure)'
WarningDiagnosticReport.effective[x]Elements differ in definition: 'This is the Datetime or Period when the report or note was written.' vs 'The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself.'
InformationDiagnosticReport.effective[x]Element minimum cardinalities differ: '1' vs '0'
WarningDiagnosticReport.resultElements differ in definition for mustSupport: 'false' vs 'true'
WarningDiagnosticReport.mediaElements differ in definition for mustSupport: 'false' vs 'true'
WarningDiagnosticReport.media.linkElements differ in definition for mustSupport: 'false' vs 'true'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/DiagnosticReport
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Added the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2019-05-212022-04-20
      • Values Differ
      .descriptionDefines constraints and extensions on the DiagnosticReport resource for the minimal set of data to query and retrieve diagnostic reports associated with clinical notes for a patientTo promote interoperability and adoption through common implementation, this profile sets minimum expectations for searching and fetching Diagnostic Reports and Notes using the DiagnosticReport resource. This profile identifies the mandatory core elements, extensions, vocabularies and value sets which **SHALL** be present in the DiagnosticReport when using this profile. It provides the floor for standards development for specific use cases. Prior to reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of US Core DiagnosticReport Profile for Report and Note exchange and US Core DocumentReference Profile.
      • Values Differ
      .experimental
        .fhirVersion4.0.1
          .jurisdiction
            ..jurisdiction[0]urn:iso:std:iso:3166#US
              .kindresource
                .nameUSCoreDiagnosticReportProfileNoteExchange
                  .publisherHL7 US Realm Steering CommitteeHL7 International - Cross-Group Projects
                  • Values Differ
                  .purpose
                    .statusactive
                      .titleUS Core DiagnosticReport Profile for Report and Note exchangeUS Core DiagnosticReport Profile for Report and Note Exchange
                      • Values Differ
                      .typeDiagnosticReport
                        .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note
                          .version3.1.16.0.0-ballot
                          • Values Differ

                          Structure

                          NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                          .. DiagnosticReport 0..*DiagnosticReportUS Core Diagnostic Report Profile for Report and Note exchange
                          C0..*DiagnosticReportA Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
                          us-core-10: effective[x] SHALL be present if the status is 'partial', 'preliminary', 'final', 'amended', 'corrected' or 'appended'
                          • Elements differ in short: 'US Core Diagnostic Report Profile for Report and Note exchange' vs 'A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports'
                          • Elements differ in definition: 'The US Core Diagnostic Report Profile for Report and Note exchange is based upon the requirements of the Argonauts to exchang imaginge reports.' vs '\-'
                          • Elements differ in comments: 'This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.' vs '\-'
                          ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical 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 report
                                          Σ0..*IdentifierBusiness identifier for report
                                            ... basedOn 0..*Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)What was requested
                                            0..*Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)What was requested
                                              ... status ?!SΣ1..1coderegistered | partial | preliminary | final +
                                              Binding: DiagnosticReportStatus (required)
                                              ?!SΣC1..1coderegistered | partial | preliminary | final +
                                              Binding: DiagnosticReportStatus (required)
                                                ... category SΣ1..*CodeableConceptService category
                                                Binding: USCoreDiagnosticReportCategory (extensible)
                                                SΣ1..*CodeableConceptService category
                                                Slice: Unordered, Open by pattern:$this
                                                Binding: DiagnosticServiceSectionCodes (example): Codes for diagnostic service sections.


                                                  ... code SΣ1..1CodeableConceptUS Core Report Code
                                                  Binding: USCoreDiagnosticreportReportAndNoteCodes (extensible): LOINC codes

                                                  SΣ1..1CodeableConceptUS Core Report Code
                                                  Binding: US Core Non Laboratory Codes (extensible): LOINC codes

                                                  • Elements differ in comments: 'UsageNote= 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.' vs '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.'
                                                  ... subject SΣ1..1Reference(US Core Patient Profile)The subject of the report - usually, but not always, the patientSΣ1..1Reference(US Core Patient Profile)The subject of the report - usually, but not always, the patient
                                                  • Elements differ in definition: 'The subject of the report. Usually, but not always, this is a patient. However diagnostic services also perform analyses on specimens collected from a variety of other sources.' vs 'The subject of the report. Usually, but not always, this is a patient. However, diagnostic services also perform analyses on specimens collected from a variety of other sources.'
                                                  ... encounter SΣ0..1Reference(US Core Encounter Profile)Health care event when test orderedSΣ0..1Reference(US Core Encounter Profile)Health care event when test ordered
                                                    ... effective[x] SΣ1..1dateTime, PeriodTime of the report or noteSΣC0..1dateTime S, PeriodDiagnostically relevant time (typically the time of the procedure)
                                                    • Elements differ in short: 'Time of the report or note' vs 'Diagnostically relevant time (typically the time of the procedure)'
                                                    • Elements differ in definition: 'This is the Datetime or Period when the report or note was written.' vs 'The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself.'
                                                    • Element minimum cardinalities differ: '1' vs '0'
                                                    ... issued SΣ0..1instantDateTime this version was madeSΣ0..1instantDateTime this version was made
                                                      ... performer SΣ0..*Reference(US Core Practitioner Profile | US Core Organization Profile)Responsible Diagnostic Service
                                                      SΣ0..*Reference(US Core Practitioner Profile S | US Core Organization Profile S | US Core PractitionerRole Profile | US Core CareTeam Profile)Responsible Diagnostic Service
                                                        ... resultsInterpreter Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam)Primary result interpreter
                                                        Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam)Primary result interpreter
                                                          ... specimen 0..*Reference(Specimen)Specimens this report is based on
                                                          0..*Reference(Specimen)Specimens this report is based on
                                                            ... result 0..*Reference(Observation)Observations
                                                            S0..*Reference(US Core Laboratory Result Observation Profile S | US Core Observation Clinical Result Profile S | US Core Observation Clinical Result Profile S)Observations
                                                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                            ... imagingStudy 0..*Reference(ImagingStudy)Reference to full details of imaging associated with the diagnostic report
                                                            0..*Reference(ImagingStudy)Reference to full details of imaging associated with the diagnostic report
                                                              ... media Σ0..*BackboneElementKey images associated with this report
                                                              SΣ0..*BackboneElementKey images associated with this report
                                                              • 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
                                                                    .... comment 0..1stringComment about the image (e.g. explanation)0..1stringComment about the image (e.g. explanation)
                                                                      .... link Σ1..1Reference(Media)Reference to the image sourceSΣ1..1Reference(Media)Reference to the image source
                                                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                                      ... conclusion 0..1stringClinical conclusion (interpretation) of test results0..1stringClinical conclusion (interpretation) of test results
                                                                        ... conclusionCode 0..*CodeableConceptCodes for the clinical conclusion of test results
                                                                        Binding: SNOMEDCTClinicalFindings (example): Diagnosis codes provided as adjuncts to the report.


                                                                        0..*CodeableConceptCodes for the clinical conclusion of test results
                                                                        Binding: SNOMEDCTClinicalFindings (example): Diagnosis codes provided as adjuncts to the report.


                                                                          ... presentedForm S0..*AttachmentEntire report as issued
                                                                          S0..*AttachmentEntire report as issued

                                                                            doco Documentation for this format