This page is part of the FHIR Specification (v3.2.0: R4 Ballot 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
Patient Administration Work Group | Maturity Level: 3 | Trial Use | Compartments: Not linked to any defined compartments |
Detailed Descriptions for the elements in the Location resource.
Location | |
Definition | Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated. |
Control | 1..1 |
Location.identifier | |
Definition | Unique code or number identifying the location to its users. |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Requirements | Organization label locations in registries, need to keep track of those. |
Summary | true |
Location.status | |
Definition | The status property covers the general availability of the resource, not the current value which may be covered by the operationStatus, or by a schedule/slots if they are configured for the location. |
Control | 0..1 |
Terminology Binding | LocationStatus (Required) |
Type | code |
Is Modifier | true |
Summary | true |
Comments | This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Location.operationalStatus | |
Definition | The Operational status covers operation values most relevant to beds (but can also apply to rooms/units/chair/etc such as an isolation unit/dialisys chair). This typically covers concepts such as contamination, housekeeping and other activities like maintenance. |
Control | 0..1 |
Terminology Binding | v2 Bed Status (Preferred) |
Type | Coding |
Summary | true |
Location.name | |
Definition | Name of the location as used by humans. Does not need to be unique. |
Control | 0..1 |
Type | string |
Summary | true |
Comments | If the name of an location changes, consider putting the old name in the alias column so that it can still be located through searches. |
Location.alias | |
Definition | A list of alternate names that the location is known as, or was known as in the past. |
Control | 0..* |
Type | string |
Requirements | Over time locations and organizations go through many changes and can be known by different names. For searching knowing previous names that the location was known by can be very useful. |
Comments | There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the location. |
Location.description | |
Definition | Description of the Location, which helps in finding or referencing the place. |
Control | 0..1 |
Type | string |
Requirements | Humans need additional information to verify a correct location has been identified. |
Summary | true |
Location.mode | |
Definition | Indicates whether a resource instance represents a specific location or a class of locations. |
Control | 0..1 |
Terminology Binding | LocationMode (Required) |
Type | code |
Requirements | When using a Location resource for scheduling or orders, we need to be able to refer to a class of Locations instead of a specific Location. |
Summary | true |
Comments | This is labeled as a modifer because whether or not the location is a class of locations changes how it can be used and understood. |
Location.type | |
Definition | Indicates the type of function performed at the location. |
Control | 0..1 |
Terminology Binding | ServiceDeliveryLocationRoleType (Extensible) |
Type | CodeableConcept |
Summary | true |
Location.telecom | |
Definition | The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites. |
Control | 0..* |
Type | ContactPoint |
Location.address | |
Definition | Physical location. |
Control | 0..1 |
Type | Address |
Requirements | If locations can be visited, we need to keep track of their address. |
Comments | This was kept as 0..1 as there is no use property on the address, so wouldn't be able to identify different address types. |
Location.physicalType | |
Definition | Physical form of the location, e.g. building, room, vehicle, road. |
Control | 0..1 |
Terminology Binding | LocationType (Example) |
Type | CodeableConcept |
Requirements | For purposes of showing relevant locations in queries, we need to categorize locations. |
Summary | true |
Location.position | |
Definition | The absolute geographic location of the Location, expressed using the WGS84 datum (This is the same co-ordinate system used in KML). |
Control | 0..1 |
Requirements | For mobile applications and automated route-finding knowing the exact location of the Location is required. |
Location.position.longitude | |
Definition | Longitude. The value domain and the interpretation are the same as for the text of the longitude element in KML (see notes below). |
Control | 1..1 |
Type | decimal |
Location.position.latitude | |
Definition | Latitude. The value domain and the interpretation are the same as for the text of the latitude element in KML (see notes below). |
Control | 1..1 |
Type | decimal |
Location.position.altitude | |
Definition | Altitude. The value domain and the interpretation are the same as for the text of the altitude element in KML (see notes below). |
Control | 0..1 |
Type | decimal |
Location.managingOrganization | |
Definition | The organization responsible for the provisioning and upkeep of the location. |
Control | 0..1 |
Type | Reference(Organization) |
Requirements | Need to know who manages the location. |
Summary | true |
Comments | This can also be used as the part of the organization hierarchy where this location provides services. These services can be defined through the HealthcareService resource. |
Location.partOf | |
Definition | Another Location which this Location is physically part of. |
Control | 0..1 |
Type | Reference(Location) |
Requirements | For purposes of location, display and identification, knowing which locations are located within other locations is important. |
Location.hoursOfOperation | |
Definition | What days/times during a week is this location usually open. |
Control | 0..* |
Comments | This type of information is commonly found published in directories and on websites informing customers when the facility is available. Specific services within the location may have their own hours which could be shorter (or longer) than the locations hours. |
Location.hoursOfOperation.daysOfWeek | |
Definition | Indicates which days of the week are available between the start and end Times. |
Control | 0..* |
Terminology Binding | DaysOfWeek (Required) |
Type | code |
Location.hoursOfOperation.allDay | |
Definition | The Location is open all day. |
Control | 0..1 |
Type | boolean |
Location.hoursOfOperation.openingTime | |
Definition | Time that the Location opens. |
Control | 0..1 |
Type | time |
Location.hoursOfOperation.closingTime | |
Definition | Time that the Location closes. |
Control | 0..1 |
Type | time |
Location.availabilityExceptions | |
Definition | A description of when the locations opening ours are different to normal, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as detailed in the opening hours Times. |
Control | 0..1 |
Type | string |
Location.endpoint | |
Definition | Technical endpoints providing access to services operated for the location. |
Control | 0..* |
Type | Reference(Endpoint) |
Requirements | Organizations may have different systems at different locations that provide various services and need to be able to define the technical connection details for how to connect to them, and for what purpose. |