This page is part of the Argonaut Provider Directory Guide (v1.0.0: Release) based on FHIR R3. This is the current published version. For a full list of available versions, see the Directory of published versions
This profile sets minimum expectations for the Location resource for recording, searching for and fetching a Location associated with a provider or organization. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.
The following data-elements are mandatory (i.e data MUST be present). These are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.
Each Location must have:
Each Location must have:
Each Location SHOULD have:
Profile specific implementation guidance:
The official URL for this profile is:
http://fhir.org/guides/argonaut-pd/StructureDefinition/argo-location
This profile builds on Location.
This profile was published on Wed Nov 09 00:00:00 AEDT 2016 as a draft by Argonaut Project.
Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.
Downloads: StructureDefinition: (XML, JSON, CSV), Schema: XML Schematron
Below is an overview of the required search and read operations for this profile. See the Conformance requirements for a complete list of supported RESTful operations and search parameters for this IG.
GET [base]/Location?identifier=[system]|[code]
Example: GET [base]/Location?identifier=http://hospital.smarthealthit.org/Location|123571
Support: Mandatory to search by identifier.
Implementation Notes: Search based on Location identifier (how to search by token).
GET [base]/Location?name=[string]
Example: GET [base]/Location?name=Health
Support: Mandatory to support search by Location name.
Implementation Notes: Search based on text name (how to search by string).
GET [base]/Location?address=[string]
Example: GET [base]/Location?address=Arbor
Example: GET [base]/Location?address-postalcode=48104
Support: Mandatory to support search by address.
Implementation Notes: Search based on text address (how to search by string).
SHOULD support the following search parameters: