US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This guide is not an authorized publication; it is the continuous build for version 8.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/US-Core/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/core/StructureDefinition/us-core-location | Version: 8.0.0 | |||
Standards status: Trial-use | Computable Name: USCoreLocationProfile | |||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.42.35 | ||||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License |
The US Core Location Profile inherits from the FHIR Location resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Location resource for recording, searching, and fetching a "physical place of available services or resources." It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption.
The following data elements must always be present (Mandatory definition) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Views below provides the formal summary, definitions, and terminology requirements.
Each Location Must Have:
Each Location Must Support:
*see guidance below
Additional Profile specific implementation guidance:
Encounter.location
and Immunization.location
.If the event facility/location differs from the Encounter.location
, systems SHOULD reference it directly:
location
element for all resources where the element is available.Location.address.line
and Location.address.city
.Usage:
Changes since version 7.0.0:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
Other representations of profile: CSV, Excel, Schematron
Below is an overview of the required Server RESTful FHIR interactions for this profile - for example, search and read operations - when supporting the US Core interactions to access this profile's information (Profile Support + Interaction Support). Note that systems that support only US Core Profiles (Profile Only Support) are not required to support these interactions. See the US Core Server CapabilityStatement for a complete list of supported RESTful interactions for this IG.
Servers providing access to data MAY support these US Core SMART Scopes:
<patient|user|system>/Location.rs
The following search parameters and search parameter combinations SHALL be supported:
SHALL support searching by location name using the name
search parameter:
GET [base]/Location?name=[string]
Example:
Implementation Notes: Fetches a bundle of all Location resources that match the name (how to search by string)
SHALL support searching location based on text address using the address
search parameter:
GET [base]/Location?address=[string]
Example:
Implementation Notes: Fetches a bundle of all Location resources that match the address string (how to search by string)
The following search parameter combinations SHOULD be supported:
SHOULD support searching using the address-city
search parameter:
GET [base]/Location?address-city=[string]
Example:
Implementation Notes: Fetches a bundle of all Location resources for the city (how to search by string)
SHOULD support searching using the address-state
search parameter:
GET [base]/Location?address-state=[string]
Example:
Implementation Notes: Fetches a bundle of all Location resources for the state (how to search by string)
SHOULD support searching using the address-postalcode
search parameter:
GET [base]/Location?address-postalcode=[string]
Example:
Implementation Notes: Fetches a bundle of all Location resources for the ZIP code (how to search by string)