Skip to main content

Location

Overview

The Location resource represents details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.

Resource Schema

Key fields in the Location resource:

{
"resourceType": "Location",
"id": "example-location-123",
"status": "active",
"name": "Netsmart Main Campus",
"type": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-RoleCode",
"code": "HOSP",
"display": "Hospital"
}
]
}
],
"telecom": [
{
"system": "phone",
"value": "555-123-4567"
}
],
"address": {
"line": ["123 Healthcare Drive"],
"city": "Overland Park",
"state": "KS",
"postalCode": "66210",
"country": "US"
},
"managingOrganization": {
"reference": "Organization/456"
}
}

Operations

The Location resource supports Read and Search operations. Support varies by CareRecord solution.

CareRecord / SolutionReadSearch
GEHRIMED
myAvatar
myEvolv
myUnity
TheraOffice

Read

Retrieves a specific Location resource by ID.

HTTP Method: GET
URL: /Location/{id}

Examples

curl -X GET https://fhir.netsmartcloud.com/uscore/v1/Location/123456 \
-H "Authorization: Bearer {token}" \
-H "Accept: application/fhir+json"

Retrieves Location resources matching specified criteria.

HTTP Method: GET or POST
URL: /Location or /Location/_search

Examples

Search Locations
curl -X GET https://fhir.netsmartcloud.com/uscore/v1/Location \
-H "Authorization: Bearer {token}" \
-H "Accept: application/fhir+json"

Integration Patterns

Common Workflows

  1. Facility Lookup - Find healthcare facilities and their details
  2. Service Location - Identify where specific services are provided
  3. Geographic Queries - Search for locations by geographic criteria

Relationships to Other Resources

The Location resource relates to:

  • Organization - Organizations that manage the location
  • Encounter - Healthcare encounters that occurred at the location
  • Procedure - Procedures performed at the location

Error Handling

For common errors and troubleshooting guidance, see Common Errors.

Supported Profiles

Profiles supported by this resource (as defined in the CapabilityStatement):