This page is part of the FHIR Specification (v1.4.0:
STU
3 Ballot 3). The current version which supercedes this version is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
. For a full list of available versions, see the
Directory of published versions
.
Page
versions:
. Page versions:
R5
R4B
R4
R3
R2
This is the narrative for the resource. See also the
XML
or
or
JSON
format.
format.
OPERATION:
Process
Message
OPERATION: Process Message
This
operation
accepts
a
message,
processes
it
according
to
the
definition
of
the
event
in
the
message
header,
and
returns
a
one
or
more
response
messages.
This
operation
is
described
in
detail
on
the
messaging
page
This operation accepts a message, processes it according to the definition of the event in the message header, and returns a one or more response messages. This operation is described in detail
on the messaging page
URL:
[base]/$process-message
URL: [base]/$process-message
Parameters
| Use | Name | Cardinality | Type | Binding | Documentation |
| IN | content | 1..1 | Bundle |
|
|
| IN | async | 0..1 | boolean |
|
|
| IN | response-url | 0..1 | uri |
|
|
| OUT | return | 0..1 | Bundle |
|
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
message
parameter
is
always
the
body
of
the
HTTP
message
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 message parameter is always the body of the HTTP message
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.