Send a message to a set of recipients
post
/20241001/patientMessages/sentItems
This resource creates a message to a set of recipients.
Consumers can reply to a message by populating the PreviousMessageId with the identifier of the message
being replied to.
Request
Header Parameters
-
accept: string
Specifies which media types are acceptable for the response. Defaults to
application/json.Default Value:application/json -
accept-charset: string
Specifies which character sets are acceptable for the response. Defaults to
UTF-8.Default Value:UTF-8 -
authorization(required): string
Contains the credentials to authenticate a consumer to the service.
-
opc-request-id: string
Unique Oracle Health assigned identifier for the request. If you need to contact Oracle about a particular request, provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
Details about the message to be sent.
Root Schema : CreateSentItemDetails
Type:
objectThe detailed information about a message to create
Show Source
-
attachments:
array attachments
The list of attachments on the message.
-
carbonCopyRecipients:
array carbonCopyRecipients
The list of carbon copy receivers.
-
content(required):
string
The content of the message in XHTML format.
-
messageSender(required):
object ParticipantSimple
The simplified information about the sender or recipient of the message.
-
patientId(required):
string
Identifier of the patient who is the subject of the message or who the message is about.
-
previousMessageId:
string
The identifier of the previous message in the conversation that this new message is in reply to. Cannot reply to a REMINDER. Previous message must have the same encounter and
responsiblePersonnelIdif those fields are also provided. If they are not provided, they are carried forward automatically. -
priority:
object Priority
The priority of the message.
-
recipients(required):
array recipients
The list of receivers. Required to have at least one recipient.
-
responsiblePersonnelId:
string
The identifier of the responsible personnel for the message. Used for reporting and helps systems and users handle the message.
-
subject:
string
The subject of the message. Oracle recommends that replies begin with Re: and forwarded messages begin with Fw:.
Nested Schema : attachments
Type:
arrayThe list of attachments on the message.
Show Source
-
Array of:
object Attachment
The details about a message attachment.
Nested Schema : carbonCopyRecipients
Type:
arrayThe list of carbon copy receivers.
Show Source
-
Array of:
object ParticipantSimple
The simplified information about the sender or recipient of the message.
Nested Schema : ParticipantSimple
Type:
objectThe simplified information about the sender or recipient of the message.
Show Source
-
id(required):
string
The unique identifier for the participant.
-
type(required):
string
Allowed Values:
[ "PERSON", "PERSONNEL", "GROUPINBOX" ]The type of the participant. This field must be set. Set toPERSONfor sent item sender. Set toPERSONNELorGROUPINBOXfor sent item recipients.
Nested Schema : Priority
Type:
objectThe priority of the message.
Show Source
-
value(required):
string
Allowed Values:
[ "HIGH", "NORMAL" ]The value of the priority.HIGHdenotesSTAT.NORMALdenotesROUTINE.
Nested Schema : recipients
Type:
arrayThe list of receivers. Required to have at least one recipient.
Show Source
-
Array of:
object ParticipantSimple
The simplified information about the sender or recipient of the message.
Nested Schema : Attachment
Type:
objectThe details about a message attachment.
Show Source
-
id(required):
string
The identifier of the attachment.
-
name(required):
string
The name of the attachment
-
version(required):
integer
The version of the attachment.
Response
Supported Media Types
- application/json
200 Response
Contains details about the created message.
Headers
-
etag: string
For optimistic concurrency control. See
if-match. -
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : PatientSentMessage
Type:
objectThe information about the message that was sent.
Show Source
-
id(required):
string
The identifier of the sent message.
400 Response
Bad Request
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
401 Response
Unauthorized
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
404 Response
Not Found
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
409 Response
Conflict
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
422 Response
Unprocessable Entity
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
429 Response
Too Many Requests
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
500 Response
Internal Server Error
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Default Response
Unknown Error
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : ApiError
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
details:
array details
A list of details regarding any and all errors from the resulting service request.
-
message(required):
string
A human-readable error message.
Nested Schema : details
Type:
arrayA list of details regarding any and all errors from the resulting service request.
Show Source
-
Array of:
object ErrorDetail
Additional detail information pertaining to the error.
Nested Schema : ErrorDetail
Type:
objectAdditional detail information pertaining to the error.
Show Source
-
detail:
string
A human-readable explanation specific to this occurrence of the problem.
-
source:
object ErrorDetailSource
An object containing references to the source of the error.
Nested Schema : ErrorDetailSource
Type:
objectAn object containing references to the source of the error.
Show Source
-
headers:
array headers
A list of the request headers that caused the error.
-
parameters:
array parameters
A list of which URI query parameters caused the error.
-
pointers:
array pointers
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example,
/datafor a primary data object, or/data/attributes/titlefor a specific attribute. A JSON Pointer must point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.
Nested Schema : headers
Type:
arrayA list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type:
arrayA list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type:
arrayA list of JSON Pointers (RFC6901) to the values in the request document that caused the error.
For example,
Show Source
/data for a primary data object, or /data/attributes/title for a specific attribute. A JSON Pointer must
point to a value in the request document that exists. If it does not exist, the client should ignore the pointer.