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

5.6 Resource Location - Content

Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated.

5.6.1 Scope and Usage

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:

5.6.2 Resource Content

Location (Resource)Unique code or number identifying the location to its usersidentifier : Identifier 0..1Name of the location as used by humans. Does not need to be uniquename : string 0..1Description of the Location, which helps in finding or referencing the placedescription : string 0..1Indicates the type of function performed at the locationtype : CodeableConcept 0..1 <<Indicates the type of function performed at the locationLocationType>>The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sitestelecom : Contact 0..*Physical locationaddress : Address 0..1Physical form of the location, e.g. building, room, vehicle, roadphysicalType : CodeableConcept 0..1 <<Physical form of the locationPhysicalType>>The organization that is responsible for the provisioning and upkeep of the locationmanagingOrganization : Resource(Organization) 0..1active | suspended | inactive (this element modifies the meaning of other elements)status : code 0..1 <<Indicates whether the location is still in useLocationStatus>>Another Location which this Location is physically part ofpartOf : Resource(Location) 0..1Indicates whether a resource instance represents a specific location or a class of locations (this element modifies the meaning of other elements)mode : code 0..1 <<Indicates whether a resource instance represents a specific location or a class of locationsLocationMode>>PositionLongitude. The value domain and the interpretation are the same as for the text of the longitude element in KML (see notes below)longitude : decimal 1..1Latitude. The value domain and the interpretation are the same as for the text of the latitude element in KML (see notes below)latitude : decimal 1..1Altitude. The value domain and the interpretation are the same as for the text of the altitude element in KML (see notes below)altitude : decimal 0..1The absolute geographic location of the Location, expressed in a KML compatible manner (see notes below for KML)position0..1

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"> doco
 <!-- 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

5.6.2.1 Terminology Bindings

PathDefinitionTypeReference
Location.type Indicates the type of function performed at the locationIncompletehttp://hl7.org/fhir/v3/vs/ServiceDeliveryLocationRoleType
Location.physicalType Physical form of the locationExamplehttp://hl7.org/fhir/vs/location-physical-type
Location.status Indicates whether the location is still in useFixedhttp://hl7.org/fhir/location-status
Location.mode Indicates whether a resource instance represents a specific location or a class of locationsFixedhttp://hl7.org/fhir/location-mode

5.6.3 Notes

5.6.3.1 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':

5.6.4 Search Parameters

Search parameters for this resource. The standard parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
_idtokenThe logical resource id associated with the resource (must be supported by all servers)
_languagetokenThe language of the resource
addressstringA (part of the) address of the locationLocation.address
identifiertokenUnique code or number identifying the location to its usersLocation.identifier
namestringA (portion of the) name of the locationLocation.name
neartokenThe 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-distancetokenA distance quantity to limit the near search to locations within a specific distance
partofreferenceThe location of which this location is a partLocation.partOf
(Location)
statustokenSearches for locations with a specific kind of statusLocation.status
typetokenA code for the type of locationLocation.type

comments powered by Disqus