| # | Name | Source | Ver | Description | |
| 1 | BioSignalReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | ||
| 2 | DiagnosticReport (IPS) | hl7.fhir.uv.ips#current | R4 | This profile constrains the DiagnosticReport resource to represent diagnostic test and procedure reports in a patient summary. | |
| 3 | DiagnosticReport - Stability Study Results dx-PQ | hl7.fhir.uv.dx-pq#current | R5 | Section 11 - Stability Study - Results | |
| 4 | DiagnosticReport Context | ihe.rad.ira#current | R5 | IHE IRA DiagnosticReport-open report context | |
| 5 | DiagnosticReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | ||
| 6 | FHIRcast Diagnostic Report for Open Events | hl7.fhir.uv.fhircast#current | R4B | Provides guidance as to which DiagnosticReport attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-open events. At least one business identifier of the DiagnosticReport SHALL be provided in a [FHIR resource]-open request. Typically the report is associated with an order from an information system. In this case the accession number of the order is provided in the DiagnosticReport's `basedOn` array attribute as a reference using a ServiceRequest reference type and the “ACSN” identifier type. The accession number SHALL be included as a business identifier if it is known. A reporting system may also include its own identifier and should use an appropriate identifier type and system when supplying such a business identifier. In radiology reports or other image related uses of FHIRcast, at least one imaging study would likely be the subject of the report and included in the event's context. In this case, the reference to one or more ImagingStudy resources would be provided. **FHIR R4 versus FHIR R5** In the FHIR R4 DiagnosticReport resource image study references would be placed in the `imagingStudy` attribute. In a FHIR R5 (or above) DiagnosticReport this attribute has been renamed `study` since the allowed reference types has been expanded to include references to GenomicStudy resources. This is obviously a breaking change. In FHIRcast deployments based on FHIR R5, the attribute `study` SHALL be used rather than the `imagingStudy` attribute. Additionally FHIR R5 includes a `supportingInfo` attribute. While not yet formally provided for in FHIR R5, it has been recommended that the next release of FHIR allow an ImagingStudy reference be included in this attribute so that the DiagnosticReport could indicate one or more image studies were consulted during the creation of the report. As such in FHIR R5 deployments, this field is considered labeled as must support. | |
| 7 | FHIRcast DiagnosticReport for Close Events | hl7.fhir.uv.fhircast#current | R4B | Provides guidance as to which DiagnosticReport attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-close events. **FHIR R4 versus FHIR R5** In the FHIR R4 DiagnosticReport resource image study references would be placed in the `imagingStudy` attribute. In a FHIR R5 (or above) DiagnosticReport this attribute has been renamed `study` since the allowed reference types has been expanded to include references to GenomicStudy resources. This is obviously a breaking change. In FHIRcast deployments based on FHIR R5, the attribute `study` SHALL be used rather than the `imagingStudy` attribute. Additionally FHIR R5 includes a `supportingInfo` attribute. While not yet formally provided for in FHIR R5, it has been recommended that the next release of FHIR allow an ImagingStudy reference be included in this attribute so that the DiagnosticReport could indicate one or more image studies were consulted during the creation of the report. As such in FHIR R5 deployments, this field is considered labeled as must support. | |
| 8 | Genomics Report | hl7.fhir.uv.genomics-reporting#current | R4 | Genomics profile of DiagnosticReport. | |
| 9 | IHE SDC/eCP on FHIR DiagnosticReport | hl7.fhir.uv.ihe-sdc-ecc#current | R4 | A DiagnosticReport Profile meant to capture what should be represented in a report parsed from an IHE SDC Form | |
| 10 | ImagingReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | ||
| 11 | IMR DiagnosticReport | ihe.rad.imr#current | R4 | IHE Interactive Multimedia Report (IMR) profile on DiagnosticReport | |
| 12 | LaboratoryReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | ||
| 13 | OCT macula Diagnostic Report | hl7.fhir.uv.eyecare#current | R4 | The DiagnosticReport profile for an OCT macula | |
| 14 | OCT RNFL Diagnostic Report | hl7.fhir.uv.eyecare#current | R4 | The DiagnosticReport profile for an OCT RNFL | |
| 15 | Ophthalmic diagnostic test report | hl7.fhir.uv.eyecare#current | R4 | Base profile specifically constrained for describing ophthalmic reports | |
| 16 | VF Diagnostic Report | hl7.fhir.uv.eyecare#current | R4 | The DiagnosticReport profile for a visual field DT | |
| 17 | VitalSignReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | |
| DiagnosticReport | I | I | I | ||||||||||||||
| DiagnosticReport.imagingStudy | D | D | C D | C | C | ||||||||||||
| DiagnosticReport.id | C D | C D | |||||||||||||||
| DiagnosticReport.meta | |||||||||||||||||
| DiagnosticReport.implicitRules | |||||||||||||||||
| DiagnosticReport.language | C D | ||||||||||||||||
| DiagnosticReport.text | |||||||||||||||||
| DiagnosticReport.contained | |||||||||||||||||
| DiagnosticReport.extension | S C (3) | S C D (6) | S C (2) | ||||||||||||||
| DiagnosticReport.modifierExtension | |||||||||||||||||
| DiagnosticReport.identifier | C D | D | D | ||||||||||||||
| DiagnosticReport.basedOn | D | D | S C (2) | ||||||||||||||
| DiagnosticReport.status | F | F | F | D | |||||||||||||
| DiagnosticReport.category | C B M | C | S C (2) | C B M | C | ||||||||||||
| DiagnosticReport.category.coding | C F | S C (2) | |||||||||||||||
| DiagnosticReport.category.coding.code | F | C F | F | ||||||||||||||
| DiagnosticReport.category.coding.system | F | C F | F | ||||||||||||||
| DiagnosticReport.code | |||||||||||||||||
| DiagnosticReport.code.coding | S C (2) | S C (2) | S C (2) | ||||||||||||||
| DiagnosticReport.code.coding.code | C F | C F | C F | ||||||||||||||
| DiagnosticReport.code.coding.system | C F | C F | C F | ||||||||||||||
| DiagnosticReport.subject | C | C | C D | C D | C | ||||||||||||
| DiagnosticReport.subject.reference | C | C | |||||||||||||||
| DiagnosticReport.encounter | |||||||||||||||||
| DiagnosticReport.effective[x] | C | C | |||||||||||||||
| DiagnosticReport.effective[x].extension | S C D | ||||||||||||||||
| DiagnosticReport.issued | C | ||||||||||||||||
| DiagnosticReport.performer | C D | S C (2) | |||||||||||||||
| DiagnosticReport.resultsInterpreter | C D | C D | |||||||||||||||
| DiagnosticReport.specimen | C | C | C | C | |||||||||||||
| DiagnosticReport.result | C | S D (2) | S C (10) | C | |||||||||||||
| DiagnosticReport.note | |||||||||||||||||
| DiagnosticReport.study | |||||||||||||||||
| DiagnosticReport.supportingInfo | |||||||||||||||||
| DiagnosticReport.supportingInfo.extension | |||||||||||||||||
| DiagnosticReport.supportingInfo.modifierExtension | |||||||||||||||||
| DiagnosticReport.supportingInfo.type | |||||||||||||||||
| DiagnosticReport.supportingInfo.reference | |||||||||||||||||
| DiagnosticReport.media | C | C | |||||||||||||||
| DiagnosticReport.media.extension | |||||||||||||||||
| DiagnosticReport.media.modifierExtension | |||||||||||||||||
| DiagnosticReport.media.comment | |||||||||||||||||
| DiagnosticReport.media.link | |||||||||||||||||
| DiagnosticReport.composition | |||||||||||||||||
| DiagnosticReport.conclusion | |||||||||||||||||
| DiagnosticReport.conclusionCode | |||||||||||||||||
| DiagnosticReport.presentedForm | C D | S C I (3) | |||||||||||||||
| DiagnosticReport.presentedForm.hash | C | ||||||||||||||||
| DiagnosticReport.presentedForm.size | C | ||||||||||||||||
| DiagnosticReport.presentedForm.contentType | C F (3) |
Produced 08 Sep 2023