Skip to content

Location Profile

Canonical../StructureDefinition/nexus-emr-core-location
Statusdraft · 1.26.0
BaseLocation (constraint)
SourceFSH · 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.

Salient fields

No salient fields have been declared for this profile yet — nothing states which few values represent a Location in charts, summaries, and LLM contexts. See Salient Fields for what they are, how they shape LLM contexts, and how to declare them.