messageheader $process-message

Process Message

Description: This operation accepts a message, processes it according to the definition of the event in the message header, and returns one or more response messages.

In addition to processing the message event, a server may choose to retain all or some the resources and make them available on a RESTful interface, but is not required to do so.

Comments: This operation does not use the parameters resource; the parameters "async" and "response-url" always go in the URL, if they are used, and the "content" parameter is always the body of the HTTP message.

When processing messages, a server may return one of several status codes:

• 200 OK: Indicates that the message has been fully processed. If an application-level response is expected for the submitted message, that response SHALL be returned as the body of the 200 response.
• 202 Accepted: Indicates that the receiving system has accepted custody of the message
• 204 No Content: Indicates that the message has been fully processed and would normally have had an application-level response, but because of instructions from the sender (e.g. the [[[http://hl7.org/fhir/StructureDefinition/messageheader-response-request]]] extension), no response is being provided
• 300+: Indicates that the message was not successfully processed. The server MAY return an OperationOutcome with additional information, and SHOULD do so if the response code is 400 or greater. The client SHALL interpret a 4xx response to indicate that there is no point resubmitting the unaltered message, and a 5xx response to indicate an unexpected error occurred on the part of the server, with the implication that it may be appropriate to resubmit the original message. Doing so SHOULD NOT result in a duplicate message response. Repeated failures indicate either a fatal problem with the submission or a problem with the receiving application.

The following rules apply when using $process-message:

• The operation only accepts POST transactions - any other HTTP method will result in an HTTP error
• The request content type submitted is always Bundle with type "message" containing a Message Header resource as the first resource
• The response content type returned, if not empty, is always Bundle with type "message" containing a Message Header resource as the first resource, or an HTTP error
• If the response is an error, the body SHOULD be an OperationOutcome resource with full details of the Errors ∓ Warning
• The mailbox may be authenticated using standard HTTP authentication methods, including OAuth

The $process-message operation can be used by any HTTP end-point that accepts FHIR messages, not just FHIR RESTful servers.

In order to ensure consistency of processing, the logical rules regarding processing of Bundle.id and message id SHALL be followed when messages are processed using this operation.

The $process-message operation may be used synchronously, or asynchronously.

The following rules apply when using the $process-message operation synchronously:

• The URL (http://server/base/$process-message) has no parameters
• It is an error if the sender POSTs a message that requires multiple response messages
• Servers SHALL accept multiple concurrent message submissions and process them correctly (they are allowed to process them sequentially internally, but multiple concurrent submissions is not an error in its own right)

The following rules apply when using the $process-message operation asynchronously:

• The URL has at least one parameter: http://server/base/$process-message?async=true
• The server acknowledges the message with a 200 OK with no body, or returns an HTTP error if the message cannot be processed
• Accepting the message means that the server has understood the message enough to know where to respond
• An OperationOutcome SHOULD be returned in either case
• By default, the server responds by invoking the $process-message using the sender's stated end-point in the message: POST [MessageHeader.source.endpoint]/$process-message]
• Since the source end-point may be manipulated by message transfer engines, an alternative response address may be specified using the parameter "response-url": http://server/base/$process-message?async=true&response-url=http://server2.com/base/anything. The endpoint at the specified URL SHALL implement the signature of the $process-message operation (parameter async=true, accept a Bundle, return a 200 OK or an error)
• The server submits response messages to the appropriate end-point with the parameter async=true. There is no response message for the response messages

Affects State: true

System: true

Type: false

Instance: false

URL: http://hl7.org/fhir/build/OperationDefinition/MessageHeader-process-message

Parameters

• content [in] 1..1 Bundle — The message to process (or, if using asynchronous messaging, it may be a response message to accept)
• async [in] 0..1 boolean — If 'true' the message is processed using the asynchronous messaging pattern
• response-url [in] 0..1 url — A URL to submit response messages to, if asynchronous messaging is being used, and if the MessageHeader.source.endpoint is not the appropriate place to submit responses
• return [out] 0..1 Bundle — A response message, if synchronous messaging is being used (mandatory in this case). For asynchronous messaging, there is no return value