| 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) |
| Error | StructureDefinition.version | Values for version differ: '3.1.1' vs '7.0.0' |
| Information | StructureDefinition.title | Values for title differ: 'US Core DiagnosticReport Profile for Report and Note exchange' vs 'US Core DiagnosticReport Profile for Report and Note Exchange' |
| Information | StructureDefinition.date | Values for date differ: '2019-05-21' vs '2023-10-17' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 US Realm Steering Committee' vs 'HL7 International / Cross-Group Projects' |
| Information | StructureDefinition.short | Values for short differ: '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' |
| Information | StructureDefinition.definition | Values for definition differ: 'The US Core Diagnostic Report Profile for Report and Note exchange is based upon the requirements of the Argonauts to exchang imaginge reports.' vs 'The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Health care event when test ordered' vs 'Encounter associated with DiagnosticReport' |
| Information | StructureDefinition.short | Values for short differ: 'Time of the report or note' vs 'Diagnostically relevant time (typically the time of the procedure)' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | DiagnosticReport.effective[x] | Element minimum cardinalities differ: '1' vs '0' |
| Warning | DiagnosticReport.result | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Warning | DiagnosticReport.media | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Warning | DiagnosticReport.media.link | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Name | Value | Comments | |
|---|---|---|---|
 abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/DiagnosticReport | ||
| copyright | Used by permission of HL7 International, all rights reserved Creative Commons License |
| |
| date | 2019-05-21 | 2023-10-17 |
|
| description | Defines 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 patient | The US Core DiagnosticReport Profile for Report and Note Exchange inherits from the FHIR [DiagnosticReport](https://hl7.org/fhir/R4/diagnosticreport.html) resource; refer to it for scope and usage definitions. This profile sets minimum expectations for searching and fetching Diagnostic Reports and Notes using the DiagnosticReport resource. It specifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. Before reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of the US Core DiagnosticReport Profile for Report and Note exchange and the US Core DocumentReference Profile. |
|
| experimental | |||
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreDiagnosticReportProfileNoteExchange | ||
| publisher | HL7 US Realm Steering Committee | HL7 International / Cross-Group Projects |
|
| purpose | |||
| status | active | ||
| title | US Core DiagnosticReport Profile for Report and Note exchange | US Core DiagnosticReport Profile for Report and Note Exchange |
|
| type | DiagnosticReport | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note | ||
| version | 3.1.1 | 7.0.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 DiagnosticReport | 0..* | DiagnosticReport | US Core Diagnostic Report Profile for Report and Note exchange | C | 0..* | DiagnosticReport | A 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' | ||||||||||
 id | Σ | 0..1 | string | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation | 0..1 | Narrative | Text summary of the resource, for human interpretation | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||||||
| identifier | Σ | 0..* | Identifier | Business identifier for report | Σ | 0..* | Identifier | Business 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..1 | code | registered | partial | preliminary | final + Binding: ?? (required) | ?!SΣC | 1..1 | code | registered | partial | preliminary | final + Binding: ?? (required) | |||||||||
| category | SΣ | 1..* | CodeableConcept | Service category Binding: ?? (extensible) | SΣ | 1..* | CodeableConcept | Service category Slice: Unordered, Open by pattern:$this Binding: ?? (example): Codes for diagnostic service sections. | |||||||||
| code | SΣ | 1..1 | CodeableConcept | US Core Report Code Binding: ?? (extensible): LOINC codes | SΣ | 1..1 | CodeableConcept | US Core Report Code Binding: ?? (extensible): LOINC codes | |||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile) | The subject of the report - usually, but not always, the patient | SΣ | 1..1 | Reference(US Core Patient Profile S | Group | Device | US Core Location Profile) | The subject of the report - usually, but not always, the patient | |||||||||
| encounter | SΣ | 0..1 | Reference(US Core Encounter Profile) | Health care event when test ordered | SΣ | 0..1 | Reference(US Core Encounter Profile) | Encounter associated with DiagnosticReport | |||||||||
| effective[x] | SΣ | 1..1 | dateTime, Period | Time of the report or note | SΣC | 0..1 | dateTime S, Period | Diagnostically relevant time (typically the time of the procedure) |
| ||||||||
| issued | SΣ | 0..1 | instant | DateTime this version was made | SΣ | 0..1 | instant | DateTime 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 | S | 0..* | Reference(US Core Laboratory Result Observation Profile S | US Core Observation Clinical Result Profile S | Observation) | Observations |
| |||||||||
| 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..* | BackboneElement | Key images associated with this report | SΣ | 0..* | BackboneElement | Key images associated with this report |
| ||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| comment | 0..1 | string | Comment about the image (e.g. explanation) | 0..1 | string | Comment about the image (e.g. explanation) | |||||||||||
| link | Σ | 1..1 | Reference(Media) | Reference to the image source | SΣ | 1..1 | Reference(Media) | Reference to the image source |
| ||||||||
| conclusion | 0..1 | string | Clinical conclusion (interpretation) of test results | 0..1 | string | Clinical conclusion (interpretation) of test results | |||||||||||
| conclusionCode | 0..* | CodeableConcept | Codes for the clinical conclusion of test results Binding: ?? (example): Diagnosis codes provided as adjuncts to the report. | 0..* | CodeableConcept | Codes for the clinical conclusion of test results Binding: ?? (example): Diagnosis codes provided as adjuncts to the report. | |||||||||||
| presentedForm | S | 0..* | Attachment | Entire report as issued | S | 0..* | Attachment | Entire report as issued | |||||||||
| Documentation for this format | |||||||||||||||||