This page is part of the FHIR Specification (v0.0.82: (v1.0.2: DSTU 1). 2). 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

• Content
• Examples
• Formal Definitions Detailed Descriptions
• Mappings
• Profiles

5.6 5.15 Resource Location - Content

Patient Administration Work Group

Maturity Level : 1

Compartments : Not linked to any defined compartments

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

This resource is referenced by Account , Appointment , AppointmentResponse , AuditEvent , CarePlan , Claim , Contract , Device , DiagnosticOrder , DiagnosticReport , Encounter , Flag , HealthcareService , Immunization , List , MedicationDispense , Observation , Practitioner , Procedure , Provenance , Schedule and SupplyDelivery

5.15.3 Resource Content

 

Alternate definitions: Schema / Schematron , Resource Profile ( XML , JSON ), Questionnaire

5.6.2.1 5.15.3.1 Terminology Bindings

Location.type Location.physicalType Location.status Location.mode

Path	Definition	Type	Reference
Location.status	Indicates the type of function performed at whether the location is still in use.	Incomplete Required	http://hl7.org/fhir/v3/vs/ServiceDeliveryLocationRoleType LocationStatus
Location.mode	Physical form of the Indicates whether a resource instance represents a specific location or a class of locations.	Example Required	http://hl7.org/fhir/vs/location-physical-type LocationMode
Location.type	Indicates whether the location is still in use type of function performed at the location.	Fixed Extensible	http://hl7.org/fhir/location-status ServiceDeliveryLocationRoleType
Location.physicalType	Indicates whether a resource instance represents a specific location or a class Physical form of locations the location	Fixed Example	http://hl7.org/fhir/location-mode LocationType

5.6.3 5.15.4 Notes

• Multiple Organizations or Practitioners may provide services at a Location. These references are not kept in Location, but can be found in the models for Organization and Practitioner instead.
• Locations may range from whole buildings to cabinets; it is possible to relate smaller Locations to their containing bigger Location using the Location.partOf element.
• Location.position is expressed using the same syntax, datum and reference system as used in Google Earth's KML files, see Google/OGS's KML .

5.6.3.1 5.15.4.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':
(however this information could still be included if was relevant, such as when it is a generic item, but not globally generic, e.g. a Burgers MU ambulance)

• Location.identifier
• Location.telecom
• Location.address
• Location.position
• Location.status
• Location.managingOrganization

5.6.4 5.15.5 Example Location Hierarchy

An example location hierarchy should help give some guidance as to one example of how a location hierarchy could look within a fictitious Hospital.
(The nesting here would be the "part-of" structure of the location)

Hospital A Building C (instance)
    East Wing (instance)
        Level 1 (instance)
            Reception (instance)
            Nurses Station EM-ns1 (instance)
                Medication Cupboard A (instance)
            Room 1 (instance)
                Room 1a (instance) - space in room separatable via a curtain
                    Bed 1a (instance) - always in this room
                Room 1b (instance)
                    Trolley 43 (instance) - moves about
                Room 1d (instance)
                    Trolley 19 (instance) - moves about
                Room 2 (instance)
                    ...
            Theatre EM-TA (instance)
            Coridor (generic)
        Level 2 (instance)
            Reception (instance)
                ...
            Nurses Station EM-ns1 (instance)
                Medication Cupboard A (instance)
            Coridor (generic)
Mobile Services (kind)
    Ambulance (kind)
        Ambulance AMB1 (instance)
        Ambulance AMB2 (instance)

Note: Wards/departments are not part of this structure - these would form part of the Organizational Hierarchy.

5.15.6 Search Parameters

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

Name	Type	Description	Paths
_id address	token string	The logical resource id associated with A (part of the) address of the resource (must be supported by all servers) location	Location.address
_language address-city	token string	The language of the resource A city specified in an address	Location.address.city
address-country	string	A country specified in an address	Location.address.country
address-postalcode	string	A postal code specified in an address	Location.address.postalCode
address-state	string	A (part of the) state specified in an address of the location	Location.address Location.address.state
address-use	token	A use code specified in an address	Location.address.use
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, the WGS84 datum, see notes) to find locations near to (servers may search using a square rather than a circle for efficiency)	Location.position
near-distance	token	A distance quantity to limit the near search to locations within a specific distance	Location.position
organization	reference	Searches for locations that are managed by the provided organization	Location.managingOrganization ( Organization )
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