description: Base StructureDefinition for DiagnosticReport Resource package_name: hl7.fhir.core derivation: specialization name: DiagnosticReport type: DiagnosticReport elements: category: {short: Service category, comments: 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., type: CodeableConcept, isSummary: true, index: 2} conclusion: {short: Clinical Interpretation of test results, type: string, index: 19} request: short: What was requested refers: ['http://hl7.org/fhir/StructureDefinition/DiagnosticRequest', 'http://hl7.org/fhir/StructureDefinition/ProcedureRequest', 'http://hl7.org/fhir/StructureDefinition/ReferralRequest'] comments: 'Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports.' type: Reference array: true index: 12 encounter: short: Health care event when test ordered refers: ['http://hl7.org/fhir/StructureDefinition/Encounter'] type: Reference isSummary: true index: 5 specimen: short: Specimens this report is based on refers: ['http://hl7.org/fhir/StructureDefinition/Specimen'] comments: 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. type: Reference array: true index: 13 effectiveDateTime: {short: Clinically Relevant time/time-period for report, comments: '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.', type: dateTime, choiceOf: effective, isSummary: true, index: 8} status: {isModifier: true, short: registered | partial | final | corrected | appended | cancelled | entered-in-error, comments: This is labeled as "Is Modifier" because applications need to take appropriate action if a report is withdrawn., type: code, isSummary: true, index: 1} result: short: Observations - simple, or complex nested groups refers: ['http://hl7.org/fhir/StructureDefinition/Observation'] type: Reference array: true index: 14 effective: short: Clinically Relevant time/time-period for report comments: 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. choices: [effectiveDateTime, effectivePeriod] isSummary: true index: 7 code: {short: Name/Code for this diagnostic report, type: CodeableConcept, isSummary: true, index: 3} identifier: {short: Id for external references to this report, type: Identifier, array: true, isSummary: true, index: 0} image: short: Key images associated with this report type: BackboneElement array: true isSummary: true index: 16 elements: comment: {short: Comment about the image (e.g. explanation), comments: 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., type: string, index: 17} link: short: Reference to the image source refers: ['http://hl7.org/fhir/StructureDefinition/Media'] type: Reference isSummary: true index: 18 required: [link] issued: {short: DateTime this version was released, comments: 'May be different from the update time of the resource itself, because that is the status of the record (potentially a secondary copy), not the actual release time of the report.', type: instant, isSummary: true, index: 10} presentedForm: {short: Entire report as issued, comments: '"application/pdf" is recommended as the most reliable and interoperable in this context.', type: Attachment, array: true, index: 21} imagingStudy: short: Reference to full details of imaging associated with the diagnostic report refers: ['http://hl7.org/fhir/StructureDefinition/ImagingManifest', 'http://hl7.org/fhir/StructureDefinition/ImagingStudy'] comments: ImagingStudy and ImageManifest 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. type: Reference array: true index: 15 codedDiagnosis: {short: Codes for the conclusion, type: CodeableConcept, array: true, index: 20} subject: short: The subject of the report, usually, but not always, the patient refers: ['http://hl7.org/fhir/StructureDefinition/Device', 'http://hl7.org/fhir/StructureDefinition/Group', 'http://hl7.org/fhir/StructureDefinition/Location', 'http://hl7.org/fhir/StructureDefinition/Patient'] type: Reference isSummary: true index: 4 performer: short: Responsible Diagnostic Service refers: ['http://hl7.org/fhir/StructureDefinition/Organization', 'http://hl7.org/fhir/StructureDefinition/Practitioner'] comments: This is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report. type: Reference array: true isSummary: true index: 11 effectivePeriod: {short: Clinically Relevant time/time-period for report, comments: '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.', type: Period, choiceOf: effective, isSummary: true, index: 9} package_version: 1.8.0 class: resource kind: resource url: http://hl7.org/fhir/StructureDefinition/DiagnosticReport base: http://hl7.org/fhir/StructureDefinition/DomainResource version: null required: [status, code]