Location Profile¶
| Canonical | ../StructureDefinition/nexus-emr-core-location |
|---|---|
| Status | draft · 1.26.0 |
| Base | Location (constraint) |
| Source | FSH · JSON |
Generic Nexus EMR core profile for Location, represents an EMR 'location' or 'site' -- basically whatever the EMR uses to break the EMR up into separate slices (often for multisite clinics using the same EMR instance) For single-site clinics, at least one Location object must exist that represents the main site: this makes downstream consumers of the FHIR data easier to write as they can always assume Locations exist. Also, note that NexusEmrAppointment REQUIRES a Location as a participant.
Examples
Conforming instances (each opens inside this tab):
- Cedarbrook Clinic Site A — Example healthcare facility location for Cedarbrook Clinic