Skip to main content

R4 Location

The Location resource describes the "Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated." (HL7 FHIR R4 Location)

Supported Profiles

This API supports the following FHIR profiles:

Operations

The General Purpose FHIR R4 Location resource supports the following standard operations. However, support varies by the targeted CareRecord or solution.

CareRecord / SolutionCreateReadUpdateSearch
GEHRIMED-Yes-Yes
myAvatarYesYesYesYes
myEvolv-Yes-Yes
myUnity-Yes-Yes
Referral Manager----
info

Not all Netsmart solutions support Location search. See supported operations table above and consult your target solution's documentation for more information.

This resource supports a combination of standard and custom search parameters in addition to the common parameters.

Standard Parameters

NameTypeDescription
address-statestringA state specified in an address
address-citystringA city specified in an address
address-postalcodestringA postal code specified in an address
identifiertokenAn identifier for the location
namestringA portion of the location's name or alias
organizationreferenceSearches for locations that are managed by the provided organization
partofreferenceA location of which this location is a part

Custom Parameters

NameTypeDescription
enddateDeprecated. Use date parameter with le prefix instead.
practitionerreferenceThe practitioner ID to be used for the search.
startdateDeprecated. Use date parameter with ge prefix instead.

Search Examples

The POST method is recommended as it keeps health information out of the URL.

Search Locations by city
curl -X POST https://fhir.netsmartcloud.com/v4/Location/_search \
-H "Authorization: {Bearer Token}" \
-H "Accept: application/fhir+json" \
-H "Content-Type: application/x-form-urlencoded" \
-d "address-city=Kansas City" \

Extended Operations

In addition to the standard operations described above, we have also implemented extended operations on the Location resource. These extended operations are not intended for CareRecord use as these operations bypass the CareRecords to communicate with FHIR directly.

Create Relay ($create-relay)

Experimental

This is an experimental operation within CareConnect that is not yet supported by any Netsmart CareRecord or other solution.

The Resource Create Relay operation is used to relay requests to another FHIR server.

Read Relay ($read-relay)

Experimental

This is an experimental operation within CareConnect that is not yet supported by any Netsmart CareRecord or other solution.

The Resource Read Relay operation is used to relay requests to another FHIR server.

Update Relay ($update-relay)

Experimental

This is an experimental operation within CareConnect that is not yet supported by any Netsmart CareRecord or other solution.

The Resource Update Relay operation is used to relay requests to another FHIR server.

Search Relay ($search-relay)

Experimental

This is an experimental operation within CareConnect that is not yet supported by any Netsmart CareRecord or other solution.

The Resource Search Relay operation is used to relay requests to another FHIR server.