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
-
encounterId(required): string
The unique identifier of the patient's encounter.
-
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 unique identifier of the patient.
Header Parameters
-
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
OK
Headers
-
oh-next-page: string
For list pagination. When this header appears in the response, additional pages of results remain.
-
oh-prev-page: string
For list pagination. When this header appears in the response, additional pages of results remain.
-
opc-request-id: string
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.
Root Schema : ChiefComplaintSummaryCollection
Type:
objectThe response from the list chief complaints operation.
Show Source
-
items(required):
array items
A collection of chief complaint summaries from the list chief complaints operation.
Nested Schema : items
Type:
arrayA collection of chief complaint summaries from the list chief complaints operation.
Show Source
-
Array of:
object ChiefComplaintSummary
A summary of a patient's chief complaint for an encounter.
Nested Schema : ChiefComplaintSummary
Type:
objectA summary of a patient's chief complaint for an encounter.
Show Source
-
display(required):
string
The displayable representation of the chief complaint.Example:
Ankle sprain -
effectiveDateTime(required):
string
The date and time the chief complaint became effective for the patient. In UTC time and ISO 8601 format.Example:
2023-09-29T11:20:09Z -
encounterId(required):
string
The unique identifier of the encounter that the chief complaint is for.Example:
97787429 -
id(required):
string
The unique identifier of the chief complaint.Example:
189786617 -
patientId(required):
string
The unique identifier of the patient that the chief complaint is for.Example:
12552026
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.
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.