- FHIR Location Resource
- Electronic Health Records Exchange Through FHIR
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
A Location includes both incidental locations (a place which is used for healthcare without prior designation or authorization) and dedicated, formally appointed locations. Locations may be private, public, mobile or fixed and scale from small freezers to full hospital buildings or parking garages.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
Examples of Locations are:
– Building, ward, corridor, room or bed
– Mobile Clinic
– Freezer, incubator
– Vehicle or lift
– Home, shed, or a garage
– Road, parking place, a park
– Ambulance (generic)
– Ambulance (specific)
– Patient’s Home (generic)
These locations are not intended to cover locations on a patient where something occurred (i.e. a patient’s broken leg) but can happily cover the location where the patient broke the leg (the playground).
Locations and Organizations are very closely related resources and can often be mixed/matched/confused.
The Location is intended to describe the more physical structures managed/operated by an organization, whereas the Organization is intended to represent the more conceptual hierarchies, such as a ward.
A Location is valid without an address in cases where it could be purely described by a geo-coded location in remote areas, or when recorded by a device. Locations with a mode = “kind” would also likely not have an address, as they are just a type of location, but could also have an address where they can be found at the address.
Another use of location could be for describing a Jurisdiction. This jurisdiction may be considered a classified boundary which could be a combination of a physical boundary, and some other discriminator(s):
– Nation – Country-wide community or Federal Government (Ministry of Health)
– Province or State (community or Government)
– Business (throughout an enterprise)
– Business scope (CDC/FDA)
– Business segment (UK Pharmacy)
About this Dataset
John Snow Labs; Health Level Seven International;
|Source License URL
|Source License Requirements
FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR
FHIR Location Resource, Electronic Health Records Exchange Through FHIR
|Name of the concept in the FHIR structure.
|required : 1
|A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.
|The type the structure describes.
|The "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.
|A free text natural language description of the structure and its use.
|The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.
|The enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.
|The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.
|The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.
|Computer Ready Name
|This is a Location resource
|The logical id of the resource
|The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|A reference to a set of rules that were followed when the resource was constructed
|Extensions for implicitRules
|The base language in which the resource is written.
|Extensions for language
|A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data
|These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently
|May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable