Magentus Practice Management FHIR Implementation Guide
1.2.60 - ci-build

Magentus Practice Management FHIR Implementation Guide - Local Development build (v1.2.60) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## OperationDefinition: Submit Order Operation

Official URL: http://fhir.geniesolutions.io/OperationDefinition/EOrderSubmitOrderOperation | Version: 1.2.60
Active as of 2026-04-03 | Computable Name: EOrderSubmitOrderOperation

This operation submits a diagnostic order (pathology or imaging/radiology) as a transaction Bundle conforming to the EOrdersSubmitOrderBundle profile. The server validates the Bundle contents and processes the transaction. The response body is a single resource whose resourceType indicates the outcome: a transaction-response Bundle on directed-order success, or an OperationOutcome on error or undirected-order lodgement.

URL: [base]/$submit_order

### Parameters

Use | Name | Scope | Cardinality | Type | Binding | Documentation
IN | order |  | 1..1 | Bundle |  | The order transaction Bundle conforming to the EOrdersSubmitOrderBundle profile. Must be a transaction Bundle containing at minimum: Patient, Organization, Practitioner, PractitionerRole, at least one ServiceRequest (EOrdersDiagnosticRequest, EOrdersPathologyRequest or EOrdersRadiologyRequest), an EOrdersTaskFulfillmentGroup and at least one EOrdersTaskFulfillmentRequest.
OUT | return |  | 1..1 | Resource |  | The response resource. A transaction-response Bundle when the order is directed and successfully processed. An OperationOutcome (severity error/fatal) when the order fails validation or cannot be processed. An OperationOutcome (severity information) when the order is undirected — all fulfillment Tasks lack an owner and the order has been lodged for later routing. The caller distinguishes between cases by inspecting resourceType and, for OperationOutcome, issue.severity.

### Notes:

### Response behaviour

The HTTP response body is always a single resource. Check `resourceType` to determine the outcome:

`resourceType` | Condition | Details
--- | --- | ---
`Bundle` (type `transaction-response`) | Order is directed and successfully processed | All fulfillment Tasks had an `owner` and the transaction committed.
`OperationOutcome` (severity `error` or `fatal`) | Order failed validation or cannot be processed | `issue.details` describes the problem; do not retry without correcting the reported issues.
`OperationOutcome` (severity `information`) | Order is undirected — no fulfillment Task has an `owner` | The order has been lodged for later routing. This is not an error; no corrective action is required.

### Response examples

Example | Description
--- | ---
Directed Order Success | Transaction-response Bundle returned when all fulfillment Tasks have an owner and the order is successfully processed.
Error Response | OperationOutcome returned when the submitted Bundle fails validation or cannot be processed.
Undirected Order Response | Informational OperationOutcome returned when no fulfillment Task has an owner; the order has been lodged for later routing.