Get a location by location identifier
get
/20240101/locations/{locationId}
Retrieves details about a single location by location identifier.
Request
Path Parameters
-
locationId(required): string
The location ID to look up. A valid location ID is a positive, a non-floating point, and a numerical value.Default Value:
UNRESTRICTED
Header Parameters
-
oh-identifier-mapping-scope: string
The URI of the standard used for mapping relationships between Oracle Health EHR and an external system.
-
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 : Location
Type:
objectThe details of a location.
Match All
The details of a location.
The details of a location.
Show Source
-
object
LocationSummary
The details of the location that were retrieved.
-
object
Location-allOf[1]
Nested Schema : LocationSummary
Type:
objectThe details of the location that were retrieved.
Show Source
-
addresses:
array addresses
A collection of address details for the location.
-
aliases:
array aliases
A collection of aliases that identify the location. Aliases are grouped by type and ordered by system.
-
attributes:
array attributes
A collection of location descriptors.
-
description(required):
string
The description of the location.
-
effective(required):
object DateTimePeriod
A representation of a date and time range.
-
id(required):
string
The unique identifier for the location.
-
isPatientCareLocation(required):
boolean
True if the location is a patient care location and false if it is not.
-
name(required):
string
A display name of the location.
-
organization:
object Organization
The organization associated with the patient and encounter. Only loaded for inbox list and message details views when the
OptionalShouldLoadOrganizationSummaryis set. -
parentLocation:
object ParentLocation
The details of a parent location.
-
status(required):
string
Allowed Values:
[ "ACTIVE", "INACTIVE", "DELETED", "COMBINED" ]Indicates the status of the location. -
telecoms:
array telecoms
A collection of contact details, for example, telephone number or fax, for the location.
-
timezone:
object TimeZone
The time zone information of the location.
-
type(required):
object CodeValueSimple
A minimal representation of a code value.
-
update(required):
object Update
Meta information about a resource.
Nested Schema : Location-allOf[1]
Type:
Show Source
object-
diagnostics:
array diagnostics
Collection of diagnostic events.
Nested Schema : addresses
Type:
arrayA collection of address details for the location.
Show Source
-
Array of:
object Address
A postal address.
Nested Schema : aliases
Type:
arrayA collection of aliases that identify the location. Aliases are grouped by type and ordered by system.
Show Source
-
Array of:
object Alias
An alias for another concept.
Nested Schema : attributes
Type:
arrayA collection of location descriptors.
Show Source
-
Array of:
object Attribute
Location descriptor.
Nested Schema : DateTimePeriod
Type:
objectA representation of a date and time range.
Show Source
-
end:
string
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.
-
start:
string
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.
Nested Schema : Organization
Type:
objectThe organization associated with the patient and encounter.
Only loaded for inbox list and message details views when the
Show Source
OptionalShouldLoadOrganizationSummary is set.
-
display:
string
The display name for the organization.
-
id(required):
string
The unique identifier for the organization.
-
orgTypes:
array orgTypes
The list of the organization types.
Nested Schema : ParentLocation
Type:
objectThe details of a parent location.
Show Source
-
id:
string
The unique identifier of the parent location. This is the parent location with a root code of 0. If multiple parents have a root code of 0, the child organization is disqualified and not returned.
Nested Schema : telecoms
Type:
arrayA collection of contact details, for example, telephone number or fax, for the location.
Show Source
-
Array of:
object Telecom
A contact detail (such as a telephone number) by which the party may be contacted.
Nested Schema : TimeZone
Type:
objectThe time zone information of the location.
Show Source
-
value:
string
The time zone value for the location.
Nested Schema : CodeValueSimple
Type:
objectA minimal representation of a code value.
Show Source
-
cdfMeaning:
string
A programmatic value, primarily used by applications to search for this value.
-
display:
string
The text consumers see that represents this code value.
-
id(required):
string
The ID of the code value.
Nested Schema : Update
Type:
objectMeta information about a resource.
Show Source
-
lastModifiedDateTime(required):
string(date-time)
The date and time in ISO-8601 format of the last changed date and time of the resource.
-
version(required):
integer(int64)
The count specific identifier of the resource.
Nested Schema : Address
Type:
objectA postal address.
Show Source
-
city:
string
The text name of the city associated with the address.
-
country:
object MultivalueField
A field that can be represented by multiple values (one of which could be code value). Currently, only code value and free-text name are supported.
-
county:
object MultivalueField
A field that can be represented by multiple values (one of which could be code value). Currently, only code value and free-text name are supported.
-
postalCode:
string
A postal code designating a region defined by the postal service.
-
state:
object MultivalueField
A field that can be represented by multiple values (one of which could be code value). Currently, only code value and free-text name are supported.
-
street1:
string
The first line of the street address.
-
street2:
string
The second line of the street address.
-
street3:
string
The third line of the street address.
-
street4:
string
The fourth line of the street address.
-
type:
object CodeValueSimple
A minimal representation of a code value.
Nested Schema : MultivalueField
Type:
objectA field that can be represented by multiple values (one of which could be code value).
Currently, only code value and free-text name are supported.
Show Source
-
codeValue:
object CodeValueSimple
A minimal representation of a code value.
-
displayName:
string
The displayable free-text name of the field.
Nested Schema : Alias
Type:
objectAn alias for another concept.
Show Source
-
dateTimePeriod:
object DateTimePeriod
A representation of a date and time range.
-
displayName(required):
string
The displayable name for the alias.
-
id(required):
string
The unique identifier for the alias.
-
systemIdentifier:
object CodeValueSimple
A minimal representation of a code value.
-
systemNamespace:
string
The namespace URI with a set of possible system identifier values that are unique.
-
type:
object CodeValueSimple
A minimal representation of a code value.
Nested Schema : Attribute
Type:
objectLocation descriptor.
Show Source
-
description:
string
Location description.Example:
ICU -
type(required):
object CodeValueSimple
A minimal representation of a code value.
-
value(required):
object value
- If
valueTypeis typeCODE, the value is a system identifier. - If
valueTypeis typeNUMBERorSTRING, the value is a string representation of a number or a string value.
- If
-
valueType(required):
string
Allowed Values:
[ "CODE", "NUMBER", "STRING" ]Value type (CODE/NUMBER/STRING) of attribute.
Nested Schema : value
Type:
object- If
valueTypeis typeCODE, the value is a system identifier. - If
valueTypeis typeNUMBERorSTRING, the value is a string representation of a number or a string value.
Example:
{
"display":"ICU",
"id":"20140688",
"meaning":"ICU"
}Nested Schema : Telecom
Type:
objectA contact detail (such as a telephone number) by which the party may be contacted.
Show Source
-
contact:
object CodeValueSimple
A minimal representation of a code value.
-
extension:
string
The extension associated with this contact.
-
format:
object CodeValueSimple
A minimal representation of a code value.
-
id(required):
string
The unique Millennium Platform identifier for the telecommunication.
-
type:
object CodeValueSimple
A minimal representation of a code value.
-
value(required):
string
The actual contact point details such as phone number or fax number.
Nested Schema : diagnostics
Type:
arrayCollection of diagnostic events.
Show Source
-
Array of:
object DiagnosticEvent
The details of this diagnostic event.
Nested Schema : DiagnosticEvent
Type:
objectThe details of this diagnostic event.
Show Source
-
field:
string
The field within the parameters or criteria body that caused the event.
-
message:
string
An event message that is useful for troubleshooting.
-
type(required):
string
Allowed Values:
[ "INVALID_PARAMETER", "MAPPING_NOT_FOUND", "MAPPING_SERVICE_FAILURE", "REQUEST_API_LIMIT_EXCEEDED", "RESOURCE_NOT_FOUND", "MAPPING_SCOPE_NOT_RECOGNIZED" ]String representing the event type. -
value:
string
The value associated with the field or type.
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.