| Error | StructureDefinition.url | Values for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-diagnosticreport' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-lab' |
| Information | StructureDefinition.name | Values for name differ: 'Argonaut DiagnosticReport Profile' vs 'USCoreDiagnosticReportProfileLaboratoryReporting' |
| Information | StructureDefinition.status | Values for status differ: 'draft' vs 'active' |
| Information | StructureDefinition.date | Values for date differ: '2016-10-18T00:00:00+11:00' vs '2023-10-17' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'Argonaut Project' vs 'HL7 International / Cross-Group Projects' |
| Information | StructureDefinition.jurisdiction | Added the item 'urn:iso:std:iso:3166#US' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '1.0.2' vs '4.0.1' |
| Information | StructureDefinition.short | Values for short differ: 'Argonaut DiagnosticReport Profile' 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 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 '\-' |
| Information | StructureDefinition.comment | Values for comment differ: '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 '\-' |
| Information | DiagnosticReport | StructureDefinition USCoreDiagnosticReportProfileLaboratoryReporting has added constraint that is not found in Argonaut DiagnosticReport Profile and it is uncertain whether they are compatible (contained.contained.empty()) |
| Information | DiagnosticReport | StructureDefinition USCoreDiagnosticReportProfileLaboratoryReporting has added constraint that is not found in Argonaut DiagnosticReport Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()) |
| Information | DiagnosticReport | StructureDefinition USCoreDiagnosticReportProfileLaboratoryReporting has added constraint that is not found in Argonaut DiagnosticReport Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) |
| Information | DiagnosticReport | StructureDefinition USCoreDiagnosticReportProfileLaboratoryReporting has added constraint that is not found in Argonaut DiagnosticReport Profile and it is uncertain whether they are compatible (contained.meta.security.empty()) |
| Information | DiagnosticReport | StructureDefinition USCoreDiagnosticReportProfileLaboratoryReporting has added constraint that is not found in Argonaut DiagnosticReport Profile and it is uncertain whether they are compatible (text.`div`.exists()) |
| Information | DiagnosticReport | StructureDefinition USCoreDiagnosticReportProfileLaboratoryReporting has added constraint that is not found in Argonaut DiagnosticReport Profile and it is uncertain whether they are compatible ((status='partial' or status='preliminary' or status='final' or status='amended' or status='corrected' or status='appended' ) implies effective.exists()) |
| Information | DiagnosticReport | StructureDefinition USCoreDiagnosticReportProfileLaboratoryReporting has added constraint that is not found in Argonaut DiagnosticReport Profile and it is uncertain whether they are compatible ((status='partial' or status='preliminary' or status='final' or status='amended' or status='corrected' or status='appended' ) implies issued.exists()) |
| 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. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.' |
| Information | StructureDefinition.definition | Values for definition differ: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.' |
| 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 as much as possible.' 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 it's narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' |
| Information | StructureDefinition.definition | Values for definition differ: 'A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs '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.' |
| 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.' 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 'Additional content defined by implementations' |
| 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. In order 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.' vs '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.' |
| 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. Usually modifier elements provide negation or qualification. In order 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.' 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 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).' |
| Information | StructureDefinition.short | Values for short differ: 'Id for external references to this report' vs 'Business identifier for report' |
| Information | StructureDefinition.definition | Values for definition differ: 'The local ID assigned to the report by the order filler, usually by the Information System of the diagnostic service provider.' vs 'Identifiers assigned to this report by the performer or other systems.' |
| Information | StructureDefinition.short | Values for short differ: 'registered | partial | final | corrected | appended | cancelled | entered-in-error' vs 'registered | partial | preliminary | final +' |
| Information | StructureDefinition.definition | Values for definition differ: 'The status of the diagnostic report as a whole.' vs 'The status of the diagnostic report.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code.' vs 'Multiple categories are allowed using various categorization schemes. The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code.' |
| Information | DiagnosticReport.category | Element maximum cardinalities differ: '1' vs '2147483647' |
| Information | StructureDefinition.short | Values for short differ: 'Name/Code for this diagnostic report' vs 'US Core Laboratory Report Order Code' |
| Information | StructureDefinition.definition | Values for definition differ: 'A code or name that describes this diagnostic report.' vs 'The test, panel or battery that was ordered.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The test, panel or battery that was ordered.' vs '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.' |
| Information | StructureDefinition.short | Values for short differ: 'The subject of the report, usually, but not always, the patient' vs 'The subject of the report - usually, but not always, the patient' |
| 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.definition | Values for definition differ: 'The link to the health care event (encounter) when the order was made.' vs 'The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about.' |
| Warning | DiagnosticReport.encounter | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | StructureDefinition.short | Values for short differ: 'Clinically Relevant time/time-period for report' vs 'Diagnostically relevant time (typically the time of specimen collection)' |
| Information | StructureDefinition.comment | Values for comment differ: 'This is the Specimen Collection Datetime or Period which is the physically relevent dateTime for laboratory tests.' vs 'If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Specimen Collection Datetime or Period.' vs 'Need to know where in the patient history to file/present this report.' |
| Information | DiagnosticReport.effective[x] | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.short | Values for short differ: 'DateTime this version was released' vs 'When the report was released' |
| Information | StructureDefinition.definition | Values for definition differ: 'The date and time that this version of the report was released from the source diagnostic service.' vs 'The date and time that this version of the report was made available to providers, typically after the report was reviewed and verified.' |
| Information | DiagnosticReport.issued | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.comment | Values for comment differ: 'This is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report.' vs '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.' |
| Information | DiagnosticReport.performer | Element minimum cardinalities differ: '1' vs '0' |
| Information | DiagnosticReport.performer | Element maximum cardinalities differ: '1' vs '2147483647' |
| Information | StructureDefinition.comment | Values for comment differ: 'If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per Observation or group.' vs 'If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group.' |
| Information | StructureDefinition.short | Values for short differ: 'Observations - simple, or complex nested groups' vs 'Observations' |
| Information | StructureDefinition.definition | Values for definition differ: 'Observations that are part of this diagnostic report. Observations can be simple name/value pairs (e.g. 'atomic' results), or they can be grouping observations that include references to other members of the group (e.g. 'panels').' vs '[Observations](http://hl7.org/fhir/R4/observation.html) that are part of this diagnostic report.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Need to support individual results, or report groups of results, where the result grouping is arbitrary, but meaningful. This structure is recursive - observations can contain observations.' vs 'Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful.' |
| Information | StructureDefinition.comment | Values for comment differ: 'ImagingStudy and ImageObjectStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.' vs 'ImagingStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.' |
| Information | StructureDefinition.short | Values for short differ: 'Clinical Interpretation of test results' vs 'Clinical conclusion (interpretation) of test results' |
| Information | StructureDefinition.definition | Values for definition differ: 'Concise and clinically contextualized narrative interpretation of the diagnostic report.' vs 'Concise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Gives Laboratory the ability to provide its own fully formatted report for clinical fidelity.' vs 'Gives laboratory the ability to provide its own fully formatted report for clinical fidelity.' |
| Warning | DiagnosticReport.presentedForm | Elements differ in definition for mustSupport: 'true' vs 'false' |
abstract
jurisdiction[0]
DiagnosticReport
extension
modifierExtension