Get nomenclatures for a supplied terminology group
get
/20240101/nomenclatures
Retrieves nomenclatures for the supplied terminology group.
Request
Query Parameters
-
groupId(required): string
The terminology group identifier.
-
groupType(required): string
The terminology group type.Allowed Values:
[ "problem", "procedure", "drg" ] -
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 -
search(required): string
The search string.
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
Success
Root Schema : NomenclatureCollection
Type:
objectRepresents a collection of nomenclatures.
Show Source
-
items(required):
array items
The collection of nomenclatures.
Nested Schema : items
Type:
arrayThe collection of nomenclatures.
Show Source
-
Array of:
object NomenclatureSummary
The details of a returned nomenclature entry.
Nested Schema : NomenclatureSummary
Type:
objectThe details of a returned nomenclature entry.
Show Source
-
code:
string
The unique code given to the term by the terminology.
-
crossMappedNomenclatures:
array crossMappedNomenclatures
Nomenclatures from other medical terminologies that are cross-mapped to this nomenclature. A cross-mapped nomenclature is an equivalent term from a more or less specific medical terminology. This field may be empty. Values are only returned when the groupType is Problem.
-
displayName(required):
string
The display or description from the content source.
-
id(required):
string
The ID of the nomenclature in the context of the authority.
-
isFavorite:
boolean
Indicator specifying that the nomenclature is a favorite nomenclature. Values are only returned when the groupType is Problem.
-
specificity:
string
Allowed Values:
[ "POST_COORD_NEEDED", "UNKNOWN" ]The specificity of the nomenclature. Values are only returned when the groupType is Problem. -
terminology(required):
string
The medical terminology that this nomenclature belongs to.
Example:
{
"id":"1234abc",
"displayName":"coronary artery bypass",
"terminology":"CERNER_US_CPT4_PROCEDURES"
}Nested Schema : crossMappedNomenclatures
Type:
arrayNomenclatures from other medical terminologies that are cross-mapped to this nomenclature. A cross-mapped nomenclature is an equivalent term from a more or less specific medical terminology. This field may be empty. Values are only returned when the groupType is Problem.
Show Source
-
Array of:
object CrossMappedNomenclature
The details of a nomenclature that exists as a cross mapping of a source nomenclature.
Nested Schema : CrossMappedNomenclature
Type:
objectThe details of a nomenclature that exists as a cross mapping of a source nomenclature.
Show Source
-
category:
string
Allowed Values:
[ "PREFERRED_PRIMARY", "OTHER_PREFERRED_PRIMARY", "PREFERRED_SECONDARY", "ALTERNATE_SECONDARY" ]The category of this cross mapping. -
code:
string
The vendor-specific codified value for this nomenclature.
-
riskIndicators:
array riskIndicators
A list of risk indicators for the nomenclature.
-
terminology:
string
The medical terminology that this cross-mapped nomenclature belongs too.
Example:
{
"code":"W56.21XS",
"terminology":"ICD10-CM",
"riskIndicators":{
"type":"HCC",
"code":167,
"description":"Major Head Injury"
},
"category":"PREFERRED_PRIMARY"
}Nested Schema : riskIndicators
Type:
arrayA list of risk indicators for the nomenclature.
Show Source
-
Array of:
object RiskIndicator
The details of a risk indicator.
Nested Schema : RiskIndicator
Type:
objectThe details of a risk indicator.
Show Source
-
code:
string
The codified value of the risk indicator.
-
description:
string
A description of this particular risk indicator.
-
type:
string
Allowed Values:
[ "HCC" ]The risk indicator type.
Example:
{
"type":"HCC",
"code":167,
"description":"Major Head Injury"
}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.
412 Response
Precondition Failed
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.