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

4.1.1. Submit Document Bundle - Clinical Report

4.1.1.1. Scope

This transaction involves a request by a Data Contribution system to transfer a clinical report as a Document Bundle, including a Composition and other linked resources to the OCRE Solution to make these available to the point of service systems (e.g. EMRs). The request is received by the OCRE which validates and forwards the received Bundle to OH Pub/Sub services and returns an HTTP response code and an OperationOutcome resource if applicable.

4.1.1.1.1. Attachments

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

4.1.1.2. Interaction Diagram

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

Role: Submits a clinical report as a Document Bundle to the OCRE FHIR server.

Actor: OCRE Solution

Role: Receives and validates a Document Bundle, sends to OH Pub/Sub services.

Actor: OH Pub/Sub services

Role: Receives and stores a Document Bundle, notifies subscribers.

4.1.1.3. Specification

This interaction is based on FHIR R4 transaction.

Submit Document Bundle Interaction

POST [base-submit]/Bundle

4.1.1.4. Clinical Report Document Bundle Submission Resources

4.1.1.5. Clinical Report Document Bundle Submission Example

Unstructured Document Bundle Example

Dicharge Summary (Structured Document Bundle) Example

Consultation Note (Structured Document Bundle) Example

4.1.1.6. Expected Behavior

See Response Handling page for additional response handling behavior.