DRAFT Implementation Guide

This is for collaboration and discussion purposes and is subject to change.

North West Genomics Testing Workflow (GTW) - Local Development build (v0.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Narrative Content
• XML
• JSON

: Process Message - XML Representation

Draft as of 2025-02-23

Raw xml | Download

<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="ProcessMessage"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: OperationDefinition ProcessMessage</b></p><a name="ProcessMessage"> </a><a name="hcProcessMessage"> </a><a name="ProcessMessage-en-GB"> </a><p>URL: [base]/$process-message</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>content</td><td/><td>1..1</td><td><a href="http://hl7.org/fhir/R4/bundle.html">Bundle</a></td><td/><td><div><p>The message to process (or, if using asynchronous messaging, it may be a response message to accept)</p>
</div></td></tr><tr><td>OUT</td><td>return</td><td/><td>0..1</td><td><a href="http://hl7.org/fhir/R4/bundle.html">Bundle</a></td><td/><td><div><p>A response message, if synchronous messaging is being used (mandatory in this case). For asynchronous messaging, there is no return value</p>
</div></td></tr></table><div><p>This <code>event message</code> differs from traditional NHS England definitions of this operation is that this operation is designed to be an interface to a mix of broker and event consumer actors, and so other standards they suport.</p>
<p>This is <strong>NOT</strong> intended to be a method of transferring health records or data between computer systems (i.e. it is not a health record type).</p>
</div></div>
  </text>
  <url value="https://hl7.mft.nhs.uk/OperationDefinition/ProcessMessage"/>
  <version value="0.0.1"/>
  <name value="ProcessMessage"/>
  <title value="Process Message"/>
  <status value="draft"/>
  <kind value="operation"/>
  <date value="2025-02-23T07:23:30+00:00"/>
  <publisher value="Manchester University NHS Foundation Trust"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="https://mft.nhs.uk/"/>
    </telecom>
  </contact>
  <contact>
    <telecom>
      <system value="email"/>
      <value value="pressoffice@mft.nhs.uk"/>
    </telecom>
  </contact>
  <contact>
    <name value="Press Office"/>
    <telecom>
      <system value="email"/>
      <value value="pressoffice@mft.nhs.uk"/>
    </telecom>
  </contact>
  <description
               value="This is documentation on the version of [HL7 FHIR process-message](https://hl7.org/fhir/R4/messageheader-operation-process-message.html) to be used for regional FHIR Messaging, this HL7 FHIR definition **SHALL** be followed."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="GB"/>
      <display value="United Kingdom of Great Britain and Northern Ireland"/>
    </coding>
  </jurisdiction>
  <code value="process-message"/>
  <comment
           value="
This `event message` differs from traditional NHS England definitions of this operation is that this operation is designed to be an interface to a mix of broker and event consumer actors, and so other standards they suport.

This is **NOT** intended to be a method of transferring health records or data between computer systems (i.e. it is not a health record type).
"/>
  <resource value="MessageHeader"/>
  <system value="true"/>
  <type value="false"/>
  <instance value="false"/>
  <parameter>
    <name value="content"/>
    <use value="in"/>
    <min value="1"/>
    <max value="1"/>
    <documentation
                   value="The message to process (or, if using asynchronous messaging, it may be a response message to accept)"/>
    <type value="Bundle"/>
  </parameter>
  <parameter>
    <name value="return"/>
    <use value="out"/>
    <min value="0"/>
    <max value="1"/>
    <documentation
                   value="A response message, if synchronous messaging is being used (mandatory in this case). For asynchronous messaging, there is no return value"/>
    <type value="Bundle"/>
  </parameter>
</OperationDefinition>