For a full list of available versions, see the Directory of published versions

4.1.2. Submit Transaction Bundle - Medical Imaging Report

4.1.2.1. Scope

This transaction involves a request by a Data Contribution system to transfer a medical imaging report, using FHIR Transaction Bundle, including a DiagnosticReport resource and its referenced resources to the OCRE Solution to make these available to point of service systems (e.g. EMRs). The request is received by the OCRE which validates and forwards the received Transaction Bundle to OH Pub/Sub services and returns an HTTP response code and an OperationOutcome resource if applicable.

4.1.2.1.1. Attachments

• For all attachments, submitters SHALL follow the Upload Attachment flow and use AttachmentMetadata extension on DiagnosticReport.presentedForm.data instead of embedding an actual base64Binary in DiagnosticReport.presentedForm.data.

4.1.2.2. Interaction Diagram

Actor: Data Contributor (e.g., Hospital or ICHSC)

Role: Submits a Medical Imaging Report as a Transaction Bundle with the DiagnosticReport resource and its reference resources to the OCRE FHIR server.

Actor: OCRE Solution

Role: Receives and validates a Bundle containing DiagnosticReport instances (as well as reference resources), and sends it to OH Pub/Sub services.

Actor: OH Pub/Sub services

Role: Receives and stores DiagnosticReport and reference resources, notifies subscribers.

4.1.2.3. Specification

This interaction is based on FHIR R4 transaction.

Submit Transaction Bundle Interaction

POST [base-submit]/Bundle

4.1.2.4. Medical Imaging Report Transaction Bundle Submission Resources

4.1.2.5. Medical Imaging Report Submission Example

Transaction Bundle Example

4.1.2.6. Expected Behavior

See Response Handling page for additional response handling behavior.