| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/uv/ips/StructureDefinition/DiagnosticReport-uv-ips' vs 'http://hl7.eu/fhir/base-r5/StructureDefinition/diagnosticReport-eu-core' |
| Error | StructureDefinition.version | Values for version differ: '2.0.0' vs '2.0.0-ballot' |
| Information | StructureDefinition.name | Values for name differ: 'DiagnosticReportUvIps' vs 'DiagnosticReportEuCore' |
| Information | StructureDefinition.title | Values for title differ: 'DiagnosticReport (IPS)' vs 'DiagnosticReport (EU core)' |
| Information | StructureDefinition.date | Values for date differ: '2024-06-19T10:50:07-05:00' vs '2025-12-22T08:19:43+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Patient Care' vs 'HL7 Europe' |
| Information | StructureDefinition.jurisdiction | Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001' |
| Information | StructureDefinition.jurisdiction | Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#150' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '4.0.1' vs '5.0.0' |
| Information | StructureDefinition.short | Values for short differ: 'A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports' vs 'Diagnostic Report EU core' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'Diagnostic Report EU core' |
| Information | StructureDefinition.comment | Values for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' |
| Information | StructureDefinition.definition | Values for definition differ: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.' |
| Information | StructureDefinition.comment | Values for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.' |
| Information | StructureDefinition.short | Values for short differ: 'Additional content defined by implementations' vs 'Extension' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'An Extension' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.comment | Values for comment differ: 'Usually assigned by the Information System of the diagnostic service provider (filler id).' vs 'Usually assigned by the Information System of the diagnostic service provider for facilitating the Report search. The order id can be used as one of the Report identifier if only one report is produced for that order.' |
| Error | DiagnosticReport.basedOn | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/CarePlan|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/NutritionOrder|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest|4.0.1]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]]) |
| Information | StructureDefinition.short | Values for short differ: 'registered | partial | preliminary | final +' vs 'Status of the Report' |
| Information | StructureDefinition.short | Values for short differ: 'Name/Code for this diagnostic report' vs 'Type of Diagnostic Report' |
| Information | StructureDefinition.definition | Values for definition differ: 'A code or name that describes this diagnostic report.' vs 'Defines the document type, it is recommended to take this from the suggested LOINC set.' |
| Warning | DiagnosticReport.code | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | DiagnosticReport.code | Example/preferred bindings differ at DiagnosticReport.code using binding from DiagnosticReportUvIps |
| Information | StructureDefinition.short | Values for short differ: 'The subject of the report - usually, but not always, the patient' vs 'Who and/or what this report is about' |
| 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 'Who or what this report is about. The report can be about a human patient, a living subject, a device (e.g. a machine), a location or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure).' |
| Warning | DiagnosticReport.subject | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Health care event when test ordered' vs 'The healthcare event which this Diagnostic Report is about (when test ordered).' |
| Information | StructureDefinition.definition | Values for definition differ: 'The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about.' vs 'The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about.' |
| Information | StructureDefinition.comment | Values for comment differ: 'This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).' vs 'This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).' |
| Information | StructureDefinition.short | Values for short differ: 'Clinically relevant time/time-period for report' vs 'Clinically relevant time/time-period for report.' |
| Warning | DiagnosticReport.effective[x] | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | DiagnosticReport.effective[x] | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.short | Values for short differ: 'Responsible Diagnostic Service' vs 'Responsible Diagnostic Service.' |
| Information | StructureDefinition.comment | Values for comment differ: 'This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report.' vs 'If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author.' |
| Warning | DiagnosticReport.performer | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.comment | Values for comment differ: 'Might not be the same entity that takes responsibility for the clinical report.' vs 'If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author.' |
| Information | StructureDefinition.short | Values for short differ: 'Specimens this report is based on' vs 'Specimens this report is based on.' |
| Information | StructureDefinition.short | Values for short differ: 'Observation results included in the diagnostic report.' vs 'results' |
| Information | StructureDefinition.definition | Values for definition differ: 'Observation results included in the diagnostic report.' vs '[Observations](http://hl7.org/fhir/R5/observation.html) that are part of this diagnostic report.' |
| Information | StructureDefinition.short | Values for short differ: 'Key images associated with this report' vs 'Additional data (like images, diagrams or documents) associated with this report' |
| Information | StructureDefinition.definition | Values for definition differ: 'A list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest).' vs 'A list of additional data, other then presented form of the report, associated with this report. This data is generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Many diagnostic services include images in the report as part of their service.' vs 'Some diagnostic reports may include additional data such as images, diagrams or documents that are relevant to the report. This additional information can provide further context and support for the findings presented in the report.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.short | Values for short differ: 'Comment about the image (e.g. explanation)' vs 'Comment about the image or data (e.g. explanation)' |
| Information | StructureDefinition.definition | Values for definition differ: 'A comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features.' vs 'Allows for a comment about the image or data, such as an explanation of its significance or context within the diagnostic report.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.' vs 'The comment should be displayed with the image or data. It would be common for the report to include additional discussion of the image or data contents or in other sections such as the conclusion.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'The provider of the report should make a comment about each image included in the report.' vs 'The provider of the report should make a comment about each image or data included in the report. This comment can provide valuable context and help the reader understand the significance of the image or data in relation to the overall findings of the report.' |
| Information | StructureDefinition.short | Values for short differ: 'Reference to the image source' vs 'Reference to the image or data' |
| Information | StructureDefinition.definition | Values for definition differ: 'Reference to the image source.' vs 'A reference to the image or data associated with this report.' |
| Error | DiagnosticReport.media.link | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Media|4.0.1]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference|5.0.0]]) |
| Information | StructureDefinition.short | Values for short differ: 'Entire report as issued' vs 'Entire report as issued (pdf recommended)' |
abstract
jurisdiction[0]
jurisdiction[1]
DiagnosticReport
extension
modifierExtension
