Imaging Diagnostic Report
0.0.1-current - ci-build International flag

Imaging Diagnostic Report, published by IHE Radiology Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/RAD.IDR/ and changes regularly. See the Directory of published versions

4.Y3 Retrieve Imaging Diagnostic Report

2:4.Y3 Retrieve Imaging Diagnostic Report

NOTE TO READERS: Transactions RAD-Y1, RAD-Y2 and RAD-Y3 are placeholders.

Both this profile (IDR) and IHE Interactive Multimedia Reports (IMR) have transactions to store and query/retrieve reports based on FHIR DiagnosticReport.

The intention is for IDR to become the base profile for reports. The IMR profile would be restructured to add its hyperlink details and behaviors either as a profile with IDR as a pre-requisite, or as named Options in IDR.

In Phase II of IDR, IDR will “adopt” the IMR transactions, generalize the names, add any general requirements (e.g. more query details), and factor out any multimedia content back into IMR.

2:4.Y3.1 Scope

This transaction is used to retrieve imaging diagnostic report instances.

The structure of the bundle and other constraints are specified in the Content Definition LATER.

Considerations include:

  • Pull example query scenarios and patterns from the IDR Public Comment draft
  • See the Find Multimedia Report [RAD-143] transaction: https://profiles.ihe.net/RAD/IMR/RAD-143.html

2:4.Y3.2 Actors Roles

Table 2:4.Y3.2-1: Actor Roles

Role Description Actor(s)
Requester Request an imaging report Report Reader
Report Consumer
Responder Return the imaging report Report Repository

2:4.Y3.3 Referenced Standards

2:4.Y3.4 Messages

Figure 2:4.Y3.4-1: Interaction Diagram

2:4.Y3.5 Security Considerations

The patient and clinical details provided in the imaging diagnostic report constitute personal health information.

2:4.Y3.5.1 Security Audit Considerations

Requesters and Responders that support the ATNA Profile shall audit this transaction.

This transaction corresponds to a TODO ATNA Trigger Event.