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

## : Submit Order Operation - XML Representation

Active as of 2026-04-03

Raw xml | Download

    <OperationDefinition xmlns="http://hl7.org/fhir">
      <id value="EOrderSubmitOrderOperation"/>
      <text>
        <status value="generated"/>
        <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: OperationDefinition EOrderSubmitOrderOperation</b></p><a name="EOrderSubmitOrderOperation"> </a><a name="hcEOrderSubmitOrderOperation"> </a><p>URL: [base]/$submit_order</p><h3>Parameters</h3><table class="grid"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>order</td><td/><td>1..1</td><td><a href="http://hl7.org/fhir/R4/bundle.html">Bundle</a></td><td/><td><div><p>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.</p>
    </div></td></tr><tr><td>OUT</td><td>return</td><td/><td>1..1</td><td><a href="http://hl7.org/fhir/R4/resource.html">Resource</a></td><td/><td><div><p>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.</p>
    </div></td></tr></table></div>
      </text>
      <url
           value="http://fhir.geniesolutions.io/OperationDefinition/EOrderSubmitOrderOperation"/>
      <version value="1.2.60"/>
      <name value="EOrderSubmitOrderOperation"/>
      <title value="Submit Order Operation"/>
      <status value="active"/>
      <kind value="operation"/>
      <date value="2026-04-03"/>
      <publisher value="Magentus Practice Management"/>
      <contact>
        <name value="Magentus Practice Management"/>
        <telecom>
          <system value="url"/>
          <value value="https://www.magentus.com/practice-management"/>
        </telecom>
        <telecom>
          <system value="email"/>
          <value value="andy.bond@magentus.com"/>
        </telecom>
      </contact>
      <contact>
        <name value="Magentus Practice Management"/>
        <telecom>
          <system value="url"/>
          <value value="https://www.magentus.com/practice-management"/>
          <use value="work"/>
        </telecom>
      </contact>
      <description
                   value="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."/>
      <jurisdiction>
        <coding>
          <system value="urn:iso:std:iso:3166"/>
          <code value="AU"/>
        </coding>
      </jurisdiction>
      <code value="submit_order"/>
      <system value="true"/>
      <type value="false"/>
      <instance value="false"/>
      <parameter>
        <name value="order"/>
        <use value="in"/>
        <min value="1"/>
        <max value="1"/>
        <documentation
                       value="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."/>
        <type value="Bundle"/>
      </parameter>
      <parameter>
        <name value="return"/>
        <use value="out"/>
        <min value="1"/>
        <max value="1"/>
        <documentation
                       value="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."/>
        <type value="Resource"/>
      </parameter>
    </OperationDefinition>