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 / Key elements

The working view: must-support, required, modifier and sliced elements from the effective (snapshot) definition.

Element Flags Card. Type Description & Constraints
Location 0..* Nexus EMR Location Core
Invariants: dom-2, dom-3, dom-4, dom-5, dom-6
meta 0..1 Meta Metadata about the resource
Invariants: ele-1
source S 0..1 uri Identifies EMR instance & pipeline version the resource came from i
Invariants: ele-1
implicitRules ?! 0..1 uri A set of rules under which this content was created i
Invariants: ele-1
text S 0..1 Narrative Narrative i
Invariants: ele-1
identifier S 0..* Identifier Business identifier(s) for location
Slicing: pattern:system (open)
Invariants: ele-1
use ?! 0..1 code usual | official | temp | secondary | old (If known) i
Binding: identifier-use (required)
Invariants: ele-1
system 1..1 uri The namespace for the identifier value i
Invariants: ele-1
value 1..1 string The value that is unique i
Invariants: ele-1
identifier:sliCode S 0..1 Identifier Ontario Service Location Indicator (SLI)
Invariants: ele-1
use ?! 0..1 code usual | official | temp | secondary | old (If known) i
Pattern: usual
Binding: identifier-use (required)
Invariants: ele-1
system 1..1 uri Must be ../NamingSystem/on-sli-code i
Fixed: ../NamingSystem/on-sli-code
Invariants: ele-1
value 1..1 string The SLI code value (string, as stored in billing_on_cheader1.location) i
Invariants: ele-1
status S ?! 0..1 code active | suspended | inactive i
Binding: location-status (required)
Invariants: ele-1
name S 0..1 string Name of the location as used by humans i
Invariants: ele-1
type S 0..* CodeableConcept Location type with raw code support i
Binding: v3-ServiceDeliveryLocationRoleType (extensible)
Invariants: ele-1
telecom S 0..* ContactPoint Contact details of the location i
Invariants: ele-1
system S 0..1 code phone | fax | email | pager | url | sms | other
Binding: contact-point-system (required)
Invariants: ele-1
value S 1..1 string The actual contact point details i
Invariants: ele-1
use ?! 0..1 code home | work | temp | old | mobile - purpose of this contact point i
Binding: contact-point-use (required)
Invariants: ele-1
address S 0..1 Address Physical location address i
Invariants: ele-1
physicalType S 0..1 CodeableConcept Physical type with raw code support
Binding: location-physical-type (example)
Invariants: ele-1
position 0..1 BackboneElement The absolute geographic location
Invariants: ele-1
longitude 1..1 decimal Longitude with WGS84 datum
Invariants: ele-1
latitude 1..1 decimal Latitude with WGS84 datum
Invariants: ele-1
managingOrganization S 0..1 Reference(Organization Profile) Organization responsible for provisioning and upkeep i
Invariants: ele-1
partOf S 0..1 Reference(Location Profile) Another Location this one is physically a part of
Invariants: ele-1