Get multiple code values
get
/20240101/codeValues
Retrieves a collection of code values by a codeSet and a set of filters, or a set of one or
more code value id parameters.
Either the id or codeSet parameter must be supplied (but not both).
- If one or more
idvalues are supplied, no further filtering is recognized and the code values are returned first by code set and then by code value ID (ascending or descending as specified). - If a
codeSetnumber is supplied, three optional filter lists can be supplied to filter the set of code values to return further. Only one of these filters (meaning,cki, andconceptCki) can be populated, otherwise, an error is returned. Queries bycodeSetrecognize the sort order setting.
Request
Query Parameters
-
cdfMeaning: array[string]
Minimum Number of Items:
0Maximum Number of Items:20A repeatable set of cdfMeaning strings that can be used for code value filtering. This field is only recognized when querying bycodeSet. If this filter is set, theckiandconceptCKIfilters cannot be set. The filter is case sensitive and a maximum of 20 values may be provided. -
cki: array[string]
Minimum Number of Items:
0Maximum Number of Items:20A repeatable set of Common Knowledge Index (CKI) strings that can be used for code value filtering. This field is only recognized when querying bycodeSet. If this is set, thecdfMeaningandconceptCKIfilter cannot be set. A maximum of 20 values may be provided. -
codeSet: string
A code set, as a string, to lookup code values for.
-
conceptCki: array[string]
Minimum Number of Items:
0Maximum Number of Items:20A repeatable set of Concept Common Knowledge Index (CKI) strings that can be used for code value filtering. This field is only recognized when querying bycodeSet. If this is set, thecdfMeaningandckifilter cannot be set. A maximum of 20 values may be provided. -
id: array[string]
Minimum Number of Items:
0Maximum Number of Items:50When querying by code value IDs, a repeatable set of code values is supplied here. The maximum number of IDs to query on is 50. -
isActive: boolean
trueby default. When set tofalse, inactive code values are returned when querying by code set. -
isAuthenticated: boolean
trueby default. When set tofalse, unauthenticated code values are returned when querying by code set. -
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. -
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
-
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
Indicates that a successful code value query was made. If all code value items were
excluded due to the provided filters, a
200 status code is still returned.
When querying by code value IDs, all provided IDs must be found for a 200 to be returned.
Otherwise, a 400 level error is returned.
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 : CodeValueCollection
Type:
objectThe results of the ListCodeValues operation.
Show Source
-
items(required):
array items
A collection of codeValue items from the filtered list call.
Nested Schema : items
Type:
arrayA collection of codeValue items from the filtered list call.
Show Source
-
Array of:
object CodeValueSummary
A summary representation of a code value.
Nested Schema : CodeValueSummary
Type:
objectA summary representation of a code value.
Show Source
-
cdfMeaning:
string
A programmatic value, primarily used by applications to search for this value.
-
cki:
string
This value is programmatically assigned for any code value created and shipped by Oracle Cerner. This value is common between all domains.
-
codeSet(required):
string
The ID of the code set this code value is part of.
-
conceptCki:
string
The functional Concept Identifier that is the codified means within Millennium Platform to identify key medical concepts to support information processing, clinical decision support, executable knowledge, and knowledge presentation.
-
definition:
string
A text field that can be used to store additional information related to the code value.
-
description:
string
A secondary way of describing the purpose of this code value row to provide more information.
-
display(required):
string
The text that consumers see that represents this code value.
-
id(required):
string
The ID of the code value.
-
isActive(required):
boolean
Indicates if the code value is active or not.
-
isAuthenticated(required):
boolean
Indicates if the code value has been authenticated or not.
-
sequence:
integer(int64)
Minimum Value:
0This value can be used to help define relative ordering within a group of related code values.
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.
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.