. Page versions: R5 R4B R4 R3 R2This page is part of the FHIR Specification (v0.11: DSTU 1 Ballot 3). 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
Formal definitions for the elements in the location resource.
| Location | |
| Definition | Contact details and position information for a physical place that may be visited and where healthcare resources and participants may be found or contained, accommodated, or stored. |
| Control | 1..1 |
| Location.name | |
| Definition | Name of the location which identifies it to its users. |
| Control | 1..1 |
| Type | string |
| Requirements | Organization label locations in registries, need to keep track of those. |
| 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 identifier. |
| Location.type | |
| Definition | Classification of the location. |
| Control | 0..* |
| Binding | LocationType : (Value Set Definition) |
| Type | CodeableConcept |
| Requirements | For purposes of showing relevant locations in queries, we need to categorize locations. |
| Comments | There are many ways by which locations can be classified, so this element may be repeated. |
| Location.telecom | |
| Definition | The contact details of the main communication devices present at the location. |
| Control | 0..1 |
| 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. |
| 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.provider | |
| Definition | The organization that provides services at the location. |
| Control | 0..1 |
| Type | Resource(Organization) |
| Requirements | Need to know who manages the location. |
| To Do | EK: Shouldn't that be "owns or manages"? Why introduce the fact that an organization provides services here? If this is a home location, you wouldn't mention the organization(s) providing services there?. |
| Location.active | |
| Definition | Whether the location is still used to provide services. |
| Control | 0..1 |
| Type | boolean |
| Is Modifier | true |
| Location.partOf | |
| Definition | Another Location which this Location is physically inside 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. |