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.

Elements / Differential

What this profile constrains beyond Location. Anything not listed is unchanged from the base; muted type/cardinality values are the base's, shown for context.

Element Flags Card. Type Description & Constraints
Location Nexus EMR Location Core
meta 0..1 Meta
source S 0..1 uri Identifies EMR instance & pipeline version the resource came from i
text S 0..1 Narrative Narrative i
identifier S 0..* Identifier Business identifier(s) for location
Slicing: pattern:system (open)
system 1..1 uri i
value 1..1 string i
identifier:sliCode S 0..1 Identifier Ontario Service Location Indicator (SLI)
use 0..1 code i
Pattern: usual
system 1..1 uri Must be ../NamingSystem/on-sli-code i
Fixed: ../NamingSystem/on-sli-code
value 1..1 string The SLI code value (string, as stored in billing_on_cheader1.location) i
status S 0..1 code i
Binding: location-status (required)
name S 0..1 string i
alias 0..* string List of alternate names i
description 0..1 string Additional details about the location i
mode 0..1 code i
type S 0..* CodeableConcept Location type with raw code support i
telecom S 0..* ContactPoint i
system S 0..1 code
value S 1..1 string i
address S 0..1 Address Physical location address i
physicalType S 0..1 CodeableConcept Physical type with raw code support
managingOrganization S 0..1 Reference(Organization Profile) i
partOf S 0..1 Reference(Location Profile)