Determine if given recipients are valid

post

/20241001/actions/validateRecipients

Verifies that the given personnel inboxes, group inboxes, or both are valid recipients and can receive the provided category of messages in their inbox.

This is not a search API. It is an explicit check on provided IDs.

Request

Header Parameters
  • Specifies which media types are acceptable for the response. Defaults to application/json.
    Default Value: application/json
  • Specifies which character sets are acceptable for the response. Defaults to UTF-8.
    Default Value: UTF-8
  • Contains the credentials to authenticate a consumer to the service.
  • 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.
Body ()
Details about the recipients to be validated.
Root Schema : ValidateRecipientsDetails
Type: object
The request object containing the list of recipients to validate and additional validation criteria.
Show Source
  • Allowed Values: [ "MESSAGES", "REMINDERS" ]
    The type of message. Validates that the recipients are configured to recieve this message category.
  • The identifier of a patient. Currently validates that the recipients share a logical domain with the patient. Eventually it will be used to mark recipients as valid if they have access to the patient's chart.
    Example: 2222
  • recipients
    The list of recipients to be validated. Can contain either personnel, group inboxes, or a mix of both.
Nested Schema : recipients
Type: array
The list of recipients to be validated. Can contain either personnel, group inboxes, or a mix of both.
Show Source
Nested Schema : Recipient
Type: object
Recipient details
Show Source
Back to Top

Response

Supported Media Types

200 Response

Recipients validated successfully
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ValidatedRecipientCollection
Type: object
The results of validating the recipients
Show Source
Nested Schema : items
Type: array
The list of validated recipient details. Each requested recipient is returned, but order is not guaranteed.
Show Source
Nested Schema : ValidatedRecipientSummary
Type: object
The information about a validated recipient.
Show Source

400 Response

Bad Request
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ApiError
Type: object
Error information.
Show Source
Nested Schema : details
Type: array
A list of details regarding any and all errors from the resulting service request.
Show Source
Nested Schema : ErrorDetail
Type: object
Additional detail information pertaining to the error.
Show Source
Nested Schema : ErrorDetailSource
Type: object
An object containing references to the source of the error.
Show Source
  • headers
    A list of the request headers that caused the error.
  • parameters
    A list of which URI query parameters caused the error.
  • pointers
    A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Nested Schema : headers
Type: array
A list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type: array
A list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type: array
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Show Source

401 Response

Unauthorized
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ApiError
Type: object
Error information.
Show Source
Nested Schema : details
Type: array
A list of details regarding any and all errors from the resulting service request.
Show Source
Nested Schema : ErrorDetail
Type: object
Additional detail information pertaining to the error.
Show Source
Nested Schema : ErrorDetailSource
Type: object
An object containing references to the source of the error.
Show Source
  • headers
    A list of the request headers that caused the error.
  • parameters
    A list of which URI query parameters caused the error.
  • pointers
    A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Nested Schema : headers
Type: array
A list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type: array
A list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type: array
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Show Source

404 Response

Not Found
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ApiError
Type: object
Error information.
Show Source
Nested Schema : details
Type: array
A list of details regarding any and all errors from the resulting service request.
Show Source
Nested Schema : ErrorDetail
Type: object
Additional detail information pertaining to the error.
Show Source
Nested Schema : ErrorDetailSource
Type: object
An object containing references to the source of the error.
Show Source
  • headers
    A list of the request headers that caused the error.
  • parameters
    A list of which URI query parameters caused the error.
  • pointers
    A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Nested Schema : headers
Type: array
A list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type: array
A list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type: array
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Show Source

422 Response

Unprocessable Entity
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ApiError
Type: object
Error information.
Show Source
Nested Schema : details
Type: array
A list of details regarding any and all errors from the resulting service request.
Show Source
Nested Schema : ErrorDetail
Type: object
Additional detail information pertaining to the error.
Show Source
Nested Schema : ErrorDetailSource
Type: object
An object containing references to the source of the error.
Show Source
  • headers
    A list of the request headers that caused the error.
  • parameters
    A list of which URI query parameters caused the error.
  • pointers
    A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Nested Schema : headers
Type: array
A list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type: array
A list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type: array
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Show Source

429 Response

Too Many Requests
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ApiError
Type: object
Error information.
Show Source
Nested Schema : details
Type: array
A list of details regarding any and all errors from the resulting service request.
Show Source
Nested Schema : ErrorDetail
Type: object
Additional detail information pertaining to the error.
Show Source
Nested Schema : ErrorDetailSource
Type: object
An object containing references to the source of the error.
Show Source
  • headers
    A list of the request headers that caused the error.
  • parameters
    A list of which URI query parameters caused the error.
  • pointers
    A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Nested Schema : headers
Type: array
A list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type: array
A list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type: array
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Show Source

500 Response

Internal Server Error
Headers
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ApiError
Type: object
Error information.
Show Source
Nested Schema : details
Type: array
A list of details regarding any and all errors from the resulting service request.
Show Source
Nested Schema : ErrorDetail
Type: object
Additional detail information pertaining to the error.
Show Source
Nested Schema : ErrorDetailSource
Type: object
An object containing references to the source of the error.
Show Source
  • headers
    A list of the request headers that caused the error.
  • parameters
    A list of which URI query parameters caused the error.
  • pointers
    A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Nested Schema : headers
Type: array
A list of the request headers that caused the error.
Show Source
Nested Schema : parameters
Type: array
A list of which URI query parameters caused the error.
Show Source
Nested Schema : pointers
Type: array
A list of JSON Pointers (RFC6901) to the values in the request document that caused the error. For example, /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.
Show Source
Back to Top