Location - FHIR v0.0.82

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.6 Resource Location - Formal Definitions

Formal definitions 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.
Control	0..1
Type	Identifier
Requirements	Organization label locations in registries, need to keep track of those.
Location.name
Definition	Name of the location as used by humans. Does not need to be unique.
Control	0..1
Type	string
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.
Location.type
Definition	Indicates the type of function performed at the location.
Control	0..1
Binding	LocationType: Indicates the type of function performed at the location (Value Set Definition)
Type	CodeableConcept
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	Contact
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
Binding	PhysicalType: (See http://hl7.org/fhir/vs/location-physical-type)
Type	CodeableConcept
Requirements	For purposes of showing relevant locations in queries, we need to categorize locations.
Location.position
Definition	The absolute geographic location of the Location, expressed in a KML compatible manner (see notes below for 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 that is responsible for the provisioning and upkeep of the location.
Control	0..1
Type	Resource(Organization)
Requirements	Need to know who manages the location.
Location.status
Definition	active \| suspended \| inactive.
Control	0..1
Binding	LocationStatus: Indicates whether the location is still in use (see http://hl7.org/fhir/location-status for values)
Type	code
Is Modifier	true
Location.partOf
Definition	Another Location which this Location is physically part of.
Control	0..1
Type	Resource(Location)
Requirements	For purposes of location, display and identification, knowing which locations are located within other locations is important.
Location.mode
Definition	Indicates whether a resource instance represents a specific location or a class of locations.
Control	0..1
Binding	LocationMode: Indicates whether a resource instance represents a specific location or a class of locations (see http://hl7.org/fhir/location-mode for values)
Type	code
Is Modifier	true
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.