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

4.1.3. Interaction: Submit MI Report

The Submit MI Report interaction is based on RESTful asynchronous HTTP interaction using FHIR transaction bundle. Each transaction bundle must include an DiagnosticReport resource and its referenced resources.

The transaction interactions submit a set of actions to perform on a server in a single HTTP request/response. The actions are performed as a single atomic "transaction" where the entire set of changes succeeds or fails as a single entity.

The content of the post submission is a Bundle with Bundle.type = transaction. Each entry SHALL carry request details (Bundle.entry.request) that provides the HTTP details of the action in order to inform the system processing the batch or transaction what to do for the entry. In most casess, this should be a PUT command with business identifiers of the associated resource to support conditional update. The FHIR server will use the business identifier to determine if the resource will be created or updated if it already exists. If multiple matches are found, no action shall be performed and the bundle will be rejected. The resources in the bundle are each processed separately as if they were an individual interaction. The actions are subject to the normal processing for each, including transactional integrity. In a transaction, all interactions or operations either succeed or fail together.

4.1.3.0.1. Transaction Processing Rules

For a transaction, servers will either accept all actions or reject all resources. The outcome of processing the transaction will not depend on the order of the resources in the transaction. A resource can only appear in a transaction once (by identity).

When processing a transaction, the server will assign new ids to all submitted resources, irrespective of any claimed logical id in the resource or fullUrl on entries in the transaction.

4.1.3.0.2. Transaction Response

As miCDR supports submission asynchrounously, after miCDR receives the submission, it returns "Accepted" (HTTP 202) response. The submission payload is placed in a queue waiting to be validated. If it is valid, the data is stored in miCDR. If validation fails, the errors and warnings are recorded in the DQS solution. The access of DQS solution is out of the scope of this implmentation guide. The applicable information will be provided to HICs at onboarding time.

4.1.3.1. Interaction Diagram

Actor: miCDR DiagnosticReport Contributor

Role: Submits a DiagnosticReport resource and other referenced resources to the miCDR FHIR server.

Actor: miCDR FHIR server

Role: Performs validation of the submission payload and returns HTTP acknowledgement and applicable FHIR OperationOutcome depending on the validation outcome.

4.1.3.2. Specification

This interaction is based on FHIR R4 transaction bundle.

Submit MI Report Interaction

POST [base]/Bundle

4.1.3.3. MI Report Submission Resources

4.1.3.4. MI Report Submission Example

Transaction Bundle Example

4.1.3.5. Expected Behavior

See Response Handling page for additional response handling behavior.