This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated.
A Location includes both incidental locations (a place which is used for healthcare without prior designation or authorization) and dedicated, formally appointed locations. Locations may be private, public, mobile or fixed and scale from small freezers to full hospital buildings or parking garages.
Examples of Locations are:
This resource is referenced by CarePlan, Composition, Device, DeviceObservationReport, DiagnosticOrder, DiagnosticReport, Encounter, Immunization, List, MedicationDispense, Observation, Organization, Practitioner, Provenance and Supply
<Location xmlns="http://hl7.org/fhir"> <!-- from Resource: extension, modifierExtension, language, text, and contained --> <identifier><!-- 0..1 Identifier Unique code or number identifying the location to its users --></identifier> <name value="[string]"/><!-- 0..1 Name of the location as used by humans --> <description value="[string]"/><!-- 0..1 Description of the Location, which helps in finding or referencing the place --> <type><!-- 0..1 CodeableConcept Indicates the type of function performed at the location --></type> <telecom><!-- 0..* Contact Contact details of the location --></telecom> <address><!-- 0..1 Address Physical location --></address> <physicalType><!-- 0..1 CodeableConcept Physical form of the location --></physicalType> <position> <!-- 0..1 The absolute geographic location --> <longitude value="[decimal]"/><!-- 1..1 Longitude as expressed in KML --> <latitude value="[decimal]"/><!-- 1..1 Latitude as expressed in KML --> <altitude value="[decimal]"/><!-- 0..1 Altitude as expressed in KML --> </position> <managingOrganization><!-- 0..1 Resource(Organization) The organization that is responsible for the provisioning and upkeep of the location --></managingOrganization> <status value="[code]"/><!-- 0..1 active | suspended | inactive --> <partOf><!-- 0..1 Resource(Location) Another Location which this Location is physically part of --></partOf> <mode value="[code]"/><!-- 0..1 instance | kind --> </Location>
Alternate definitions: Schema/Schematron, Resource Profile
Path | Definition | Type | Reference |
---|---|---|---|
Location.type | Indicates the type of function performed at the location | Incomplete | http://hl7.org/fhir/v3/vs/ServiceDeliveryLocationRoleType |
Location.physicalType | Physical form of the location | Example | http://hl7.org/fhir/vs/location-physical-type |
Location.status | Indicates whether the location is still in use | Fixed | http://hl7.org/fhir/location-status |
Location.mode | Indicates whether a resource instance represents a specific location or a class of locations | Fixed | http://hl7.org/fhir/location-mode |
The Location.mode element can be used to indicate whether a Location resource represents a specific (potentially identifiable) Location ('instance'), or a class of Locations ('kind'). Especially Resources capturing orders, resource scheduling, plans and definitions may refer to Locations in 'kind' mode. For these domains, it is often not necessary to refer to a specific Location, but rather to a class of Locations. An example of this is found in planning, where we need to allocate an "isolation room" for a patient, or need to dispatch "an ambulance" at a certain time. In these cases it is not important exactly which isolation room or ambulance is allocated, and it is sufficient to just indicate a 'kind' of Location.
Note that 'kind' should not be used to represent Locations where an actual instance of a Location was involved, but identifying information is missing. E.g. when a patient arrived 'by ambulance', but it is not known by which ambulance, this should be represented using a Location in 'instance' mode with a missing identifier, not a Location of 'kind' ambulance.
Some of Location's data elements are only relevant when mode is 'instance' and should not be used when mode is 'kind':
Search parameters for this resource. The standard parameters also apply. See Searching for more information about searching in REST, messaging, and services.
Name | Type | Description | Paths |
_id | token | The logical resource id associated with the resource (must be supported by all servers) | |
_language | token | The language of the resource | |
address | string | A (part of the) address of the location | Location.address |
identifier | token | Unique code or number identifying the location to its users | Location.identifier |
name | string | A (portion of the) name of the location | Location.name |
near | token | The coordinates expressed as [lat],[long] (using KML, see notes) to find locations near to (servers may search using a square rather than a circle for efficiency) | |
near-distance | token | A distance quantity to limit the near search to locations within a specific distance | |
partof | reference | The location of which this location is a part | Location.partOf (Location) |
status | token | Searches for locations with a specific kind of status | Location.status |
type | token | A code for the type of location | Location.type |