R4 Draft for Comment

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 GroupMaturity 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.

Control1..1
Location.identifier
Definition

Unique code or number identifying the location to its users.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Organization label locations in registries, need to keep track of those.

Summarytrue
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.

Control0..1
Terminology BindingLocationStatus (Required)
Typecode
Is Modifiertrue
Summarytrue
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.

Control0..1
Terminology Bindingv2 Bed Status (Preferred)
TypeCoding
Summarytrue
Location.name
Definition

Name of the location as used by humans. Does not need to be unique.

Control0..1
Typestring
Summarytrue
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.

Control0..*
Typestring
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.

Control0..1
Typestring
Requirements

Humans need additional information to verify a correct location has been identified.

Summarytrue
Location.mode
Definition

Indicates whether a resource instance represents a specific location or a class of locations.

Control0..1
Terminology BindingLocationMode (Required)
Typecode
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.

Summarytrue
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.

Control0..1
Terminology BindingServiceDeliveryLocationRoleType (Extensible)
TypeCodeableConcept
Summarytrue
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.

Control0..*
TypeContactPoint
Location.address
Definition

Physical location.

Control0..1
TypeAddress
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.

Control0..1
Terminology BindingLocationType (Example)
TypeCodeableConcept
Requirements

For purposes of showing relevant locations in queries, we need to categorize locations.

Summarytrue
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).

Control0..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).

Control1..1
Typedecimal
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).

Control1..1
Typedecimal
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).

Control0..1
Typedecimal
Location.managingOrganization
Definition

The organization responsible for the provisioning and upkeep of the location.

Control0..1
TypeReference(Organization)
Requirements

Need to know who manages the location.

Summarytrue
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.

Control0..1
TypeReference(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.

Control0..*
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.

Control0..*
Terminology BindingDaysOfWeek (Required)
Typecode
Location.hoursOfOperation.allDay
Definition

The Location is open all day.

Control0..1
Typeboolean
Location.hoursOfOperation.openingTime
Definition

Time that the Location opens.

Control0..1
Typetime
Location.hoursOfOperation.closingTime
Definition

Time that the Location closes.

Control0..1
Typetime
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.

Control0..1
Typestring
Location.endpoint
Definition

Technical endpoints providing access to services operated for the location.

Control0..*
TypeReference(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.