Get a list of personnel

get

/20240101/personnel

Retrieves personnel using IDs or the specified search criteria. If no ID or query search criteria is provided, all active and effective personnel are returned.

Additional Search Rules

  1. The service returns any personnel that have at least one of the supplied alias values.
  2. If first name is supplied, last name is required.
  3. Partial name search is supported and personnel whose names begin with the supplied names are returned.

Example URIs

  • /personnel?id=123&id=999
  • /personnel?id=123
  • /personnel?firstName=first&lastName=last
  • /personnel?firstName=first&lastName=last&status=active_and_effectiv_only

Request

Query Parameters
  • The first name of the personnel member to be retrieved. Can be partial, and a personnel member whose first name begins with the supplied name is returned. If firstName is populated, then lastName must also be populated. The parameter is case insensitive.
  • The personnel member's first, middle, or last name. Partial matches are returned. The value is case insensitive.
  • Collection Format: multi
    The collection of IDs uniquely identifying the personnel member. If no ID is provided, all active and effective personnel are returned.
  • The family name of the personnel member to be retrieved. Can be partial, and a personnel member whose family name begins with the supplied name is returned.
  • 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
  • Collection Format: multi
    The collection of local aliases uniquely identifying a personnel member or multiple personnel to be retrieved. This value is a string composed of alias pool code, alias type, and alias value in the following format:
    ALIAS_POOL_CD$ALIAS_TYPE|ALIAS_VALUE
    • ALIAS_POOL_CD is a code value from Code Set 263.
    • ALIAS_TYPE is a string (NPI, SPI, EDIPI, and so on) or a code value from Code Set 320, representing the alias type.
    • ALIAS_VALUE is the alias value, such as a name or ID number.
    Note:
    • ALIAS_POOL_CD is optional if ALIAS_TYPE is provided and vice versa. If both ALIAS_POOL_CD and ALIAS_TYPE are supplied, the personnel returned have the alias with the supplied ALIAS_POOL_CD, ALIAS_TYPE, and ALIAS_VALUE.
    • This string should be URI-escaped, but this documentation and examples use the unescaped form for clarity.
    • Depending on the type of originating system and the type of alias, additional restrictions may apply.
    Examples for searching personnel by local aliases:
    • Alias pool code and alias value: 2170010196|56369, where 2170010196 represents the alias pool code and 56369 represents the alias value.
    • Alias type code and alias value: 4051669|56369, where 4051669 represents the alias type code and 56369 represents the alias value.
    • Alias type string and alias value: NPI|56369, where NPI represents the alias type and 56369 represents the alias value.
    • Alias pool code, alias type, and alias value: 2170010196$NPI|56369, where 2170010196 represents the alias pool code, NPI represents the alias type, and 56369 represents the alias value.
    If the string value provided does not contain the above separators, it is treated as an alias value and an alias value search is performed.
  • Minimum Length: 1
    For list pagination. The value of the opc-next-page response header from the previous List request.
  • The personnel classfication to search for specific personnel attributes. If not populated, all personnel associated with other criteria are returned.
    Allowed Values: [ "ALL", "PHYSICIAN_ONLY" ]
  • The status indicator to determine the active and effective status of the personnel details to be returned.
    Attribute Default Behavior ACTIVE_AND_EFFECTIVE_ONLY
    Personnel Active and Effective Active and Effective
    Names Active Active and Effective
    Aliases Active and Effective Active and Effective
    Telecoms Active and Effective Active and Effective
    Credentials Active and Effective Active and Effective
    Specialties Active and Effective Active and Effective
    The roles are retrieved from an API request. The default role is going to be active and effective. See Millennium Identity and Access Management Glossary for more information.
    Allowed Values: [ "ACTIVE_AND_EFFECTIVE_ONLY" ]
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

Success
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 : PersonnelCollection
Type: object
A list of personnel summaries and related information.
Show Source
Nested Schema : items
Type: array
The collection of personnel who were retrieved.
Show Source
Nested Schema : PersonnelSummary
Type: object
The details of a personnel member who was retrieved.
Show Source
Nested Schema : names
Type: array
A collection of names for the personnel member.
Show Source
Nested Schema : PersonName
Type: object
The basic data representation of a person name.
Show Source
Nested Schema : DateTimePeriod
Type: object
A representation of a date and time range.
Show Source
  • The date and time represented in YYYY-MM-DDTHH:MM:SS:SSSZ format without the UTC offset as defined by RFC 3339. No time zone information is associated with this date and time.
  • The date and time represented in YYYY-MM-DDTHH:MM:SS:SSSZ format without the UTC offset as defined by RFC 3339. No time zone information is associated with this date and time.

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

Default Response

Unknown 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