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

Cedarbrook Clinic Site A

Example healthcare facility location for Cedarbrook Clinic

Location/cedarbrook-site-a — claims conformance to Location Profile

{
  "resourceType": "Location",
  "id": "cedarbrook-site-a",
  "meta": {
    "profile": [
      "../StructureDefinition/nexus-emr-core-location"
    ]
  },
  "text": {
    "status": "generated",
    "div": "<div xmlns='http://www.w3.org/1999/xhtml'><p>Cedarbrook Family Health - Site A, postal code T2N 1A1.</p></div>"
  },
  "identifier": [
    {
      "use": "usual",
      "system": "../NamingSystem/on-sli-code",
      "value": "CBRK01"
    }
  ],
  "name": "Cedarbrook Family Health - Site A",
  "address": {
    "postalCode": "T2N 1A1"
  },
  "managingOrganization": {
    "identifier": {
      "system": "../NamingSystem/organization-identifier",
      "value": "cedarbrook-clinic"
    }
  }
}

Referenced by: Appointment With Slot Linkage · Avery COVID-19 Vaccination (Prevention) · Avery TDAP Immunization · Dr. Navarro Bookable Schedule · Nexus EMR Appointment Example · Nexus EMR Invoice Example · nexus-emr-core-appointment-example-telephone · Walk-in Appointment Example