Get a list of messages sent by a patient
get
/20241001/patientMessages/sentItems
Retrieves the sent messages based on a given patient ID.
The service currently only supports a page limit of 1000 and returns 1 page.
Adjust date and time parameters to retrieve further items.
Request
Query Parameters
-
createDateTimeGreaterThanOrEqualTo: string
Messages created after this date and time value are retrieved. Reminders set to show up after this date and time are retrieved. Defaults to 90 days before the current date and time. Must be before the
createDateTimeLessThanOrEqualTo. The ISO 8601 combined date and time in UTC point-in-time format is used to specify the date and time value, excluding milliseconds. -
createDateTimeLessThanOrEqualTo: string
Messages created before this date and time value are retrieved. Reminders set to show up before this date and time are retrieved. Defaults to the current date and time. Must be after the
createDateTimeGreaterThanOrEqualTo. Future dates are not supported and if provided, the default current date and time are used instead. The ISO 8601 combined date and time in UTC point-in-time format is used to specify the date and time value, excluding milliseconds. -
limit: integer
Minimum Value:
1000Maximum Value:1000For list pagination. The maximum number of results per page, or items to return in a paginated List request.Default Value:1000 -
page: string
Minimum Length:
1For list pagination. The value of the opc-next-page response header from the previous List request. -
patientId(required): string
The patient ID to filter the resource query against.
-
sortBy: string
The field to sort by. Only one sort order may be provided. Default order for createDateTime is descending. Sort the patient messages by createDatTime for sent items. Sort the reminders by remindDateTime and the messages by createDateTime for inbox items.Default Value:
createDateTimeAllowed Values:[ "createDateTime", "priority" ] -
sortOrder: string
The sort order to use, either ascending (
ASC) or descending (DESC).Allowed Values:[ "ASC", "DESC" ]
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.
Response
Supported Media Types
- application/json
200 Response
Returns the list of messages retrieved for a given patient
Headers
-
opc-next-page: string
For list pagination. When this header appears in the response, additional pages of results remain.
-
opc-prev-page: string
For list pagination. When this header appears in the response, additional pages of results remain.
-
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 : PatientSentMessagesCollection
Type:
objectThe list of messages that have been sent by the patient.
Show Source
-
items(required):
array items
The list of the sent patient messages retrieved. Can be empty.
Nested Schema : items
Type:
arrayThe list of the sent patient messages retrieved. Can be empty.
Show Source
-
Array of:
object PatientSentMessageSummary
The representation of a sent message for a patient.
Nested Schema : PatientSentMessageSummary
Type:
objectThe representation of a sent message for a patient.
Show Source
-
carbonCopyRecipients:
array carbonCopyRecipients
The list of the personnel and group inboxes who received a copy of the sent message.
-
conversationId:
string
The identifier of the conversation. All messages are assigned a conversationId, even if no replies have taken place. Multiple messages could have the same conversation ID if they are part of the same thread or back and forth of replies. This allows the consumer to group the messages together visually in a thread.
-
createdDateTime(required):
object DateTimeWithZone
A representation of the date and time with the time zone.
-
id(required):
string
The identifier for the sent message.
-
messageSender(required):
object Participant
The sender or recipient of the message.
-
patient(required):
object PersonSimple
A simple representation of the individual person that was retrieved. The individual could be a personnel member (provider), a patient, or a nonpatient person.
-
priority:
object Priority
The priority of the message.
-
recipients(required):
array recipients
The list of the personnel and group inboxes who are the recipient of the sent message.
-
recipientsAccessed:
array recipientsAccessed
The list of the personnel and group inboxes who have read the message.
-
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 sent message.
Nested Schema : carbonCopyRecipients
Type:
arrayThe list of the personnel and group inboxes who received a copy of the sent message.
Show Source
-
Array of:
object Participant
The sender or recipient of the message.
Nested Schema : DateTimeWithZone
Type:
objectA representation of the date and time with the time zone.
Show Source
-
dateTime:
string(date-time)
The date and time represented in YYYY-MM-DDTHH:MM:SS:SSSZ format without the UTC offset as defined by RFC 3339. No timezone information is associated with this date/time.
-
ianaTimeZone:
string
The time zone, provided that the date includes time precision. If
dateTimecontains time, then this field is required.
Nested Schema : Participant
Type:
objectThe sender or recipient of the message.
Show Source
-
groupInboxName:
string
The name of the group inbox, for cases where the participant is of type group inbox.
-
id(required):
string
The unique identifier for the participant.
-
personName:
object PersonNameSummary
A summary of just first, last, and full name for a person (which could be a personnel member, patient, or nonpatient person).
-
personnelName:
object PersonNameSummary
A summary of just first, last, and full name for a person (which could be a personnel member, patient, or nonpatient person).
-
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 and inbox item carbon copy recipients. Set toPERSON,PERSONNEL, orGROUPINBOXfor inbox item recipients.
Nested Schema : PersonSimple
Type:
objectA simple representation of the individual person that was retrieved.
The individual could be a personnel member (provider), a patient, or a nonpatient person.
Show Source
-
id(required):
string
The unique identifier for the individual.
-
name:
object PersonNameSummary
A summary of just first, last, and full name for a person (which could be a personnel member, patient, or nonpatient person).
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 the personnel and group inboxes who are the recipient of the sent message.
Show Source
-
Array of:
object Participant
The sender or recipient of the message.
Nested Schema : recipientsAccessed
Type:
arrayThe list of the personnel and group inboxes who have read the message.
Show Source
-
Array of:
object Participant
The sender or recipient of the message.
Nested Schema : PersonNameSummary
Type:
objectA summary of just first, last, and full name for a person (which could be a personnel member, patient, or nonpatient person).
Show Source
-
firstName:
string
The person's first given name.
-
fullName:
string
The fully formatted name.
-
lastName:
string
The person's family last name.
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.
403 Response
NotAuthorized
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.
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.