Get a list of chief complaints for a patient

get

/20240101/chiefComplaints

Retrieves chief complaints for a patient that you can filter by the patient's encounter.

Chief complaints are only documented once per patient encounter. If the encounterId filter is set and a chief complaint exists for the encounter, the system returns only one response.

Note: The encounterId filter is required until retrieving all chief complaints for a patient is supported.

Request

Query Parameters
  • The unique identifier of the patient's encounter.
  • Minimum Value: 1000
    Maximum Value: 1000
    For list pagination. The maximum number of results per page, or items to return in a paginated List request.
    Default Value: 1000
  • Minimum Length: 1
    For list pagination. The value of the opc-next-page response header from the previous List request.
  • The unique identifier of the patient.
Header Parameters
  • Contains the credentials to authenticate a consumer to the service.
  • Unique Oracle Cerner-assigned identifier for the request. If you need to contact Oracle Cerner about a particular request, you must provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
Back to Top

Response

Supported Media Types

200 Response

OK
Headers
  • For list pagination. When this header appears in the response, additional pages of results remain.
  • For list pagination. When this header appears in the response, additional pages of results remain.
  • Unique Oracle Cerner-assigned identifier for the request. If you need to contact Oracle Cerner about a particular request, you must provide the request ID.
Body ()
Root Schema : ChiefComplaintSummaryCollection
Type: object
The response from the list chief complaints operation.
Show Source
Nested Schema : items
Type: array
A collection of chief complaint summaries from the list chief complaints operation.
Show Source
Nested Schema : ChiefComplaintSummary
Type: object
A summary of a patient's chief complaint for an encounter.
Show Source

400 Response

Bad Request
Headers
  • Unique Oracle Cerner-assigned identifier for the request. If you need to contact Oracle Cerner about a particular request, you must 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 errors from the resulting service call.
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 which 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, ignore the pointer.

Nested Schema : headers
Type: array
A list of the request headers which 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, ignore the pointer.

Show Source

401 Response

Unauthorized
Headers
  • Unique Oracle Cerner-assigned identifier for the request. If you need to contact Oracle Cerner about a particular request, you must 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 errors from the resulting service call.
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 which 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, ignore the pointer.

Nested Schema : headers
Type: array
A list of the request headers which 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, ignore the pointer.

Show Source

404 Response

Not Found
Headers
  • Unique Oracle Cerner-assigned identifier for the request. If you need to contact Oracle Cerner about a particular request, you must 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 errors from the resulting service call.
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 which 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, ignore the pointer.

Nested Schema : headers
Type: array
A list of the request headers which 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, ignore the pointer.

Show Source

429 Response

Too Many Requests
Headers
  • Unique Oracle Cerner-assigned identifier for the request. If you need to contact Oracle Cerner about a particular request, you must 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 errors from the resulting service call.
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 which 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, ignore the pointer.

Nested Schema : headers
Type: array
A list of the request headers which 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, ignore the pointer.

Show Source

500 Response

Internal Server Error
Headers
  • Unique Oracle Cerner-assigned identifier for the request. If you need to contact Oracle Cerner about a particular request, you must 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 errors from the resulting service call.
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 which 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, ignore the pointer.

Nested Schema : headers
Type: array
A list of the request headers which 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, ignore the pointer.

Show Source
Back to Top