Skip to content

Referral Profile

Canonical../StructureDefinition/nexus-core-referral
Statusdraft · 1.26.0
BaseServiceRequest (constraint)
SourceFSH · JSON

Defines the Nexus EMR FHIR profile for referrals: a request that another clinician or service accept the patient, for consultation, second opinion, or ongoing management. Aligned to the pan-Canadian CA-eReC / Ontario eReferral contract, which is the shape Nexus already exchanges with Ocean. Distinct from NexusEmrCoreServiceRequest, which governs laboratory, imaging and procedure ORDERS and fixes intent to order.

Elements / Key elements

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

Element Flags Card. Type Description & Constraints
ServiceRequest 0..* Nexus EMR Referral
Invariants: dom-2, dom-3, dom-4, dom-5, dom-6, prr-1, nexus-note-extension-not-where-native, referral-code-has-text, referral-category-coded
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 the referral i
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
status S ?! 1..1 code draft | active | on-hold | revoked | completed | entered-in-error i
Binding: request-status (required)
Invariants: ele-1
intent S ?! 1..1 code proposal i
Fixed: proposal
Binding: request-intent (required)
Invariants: ele-1
category S 1..* CodeableConcept Receiving service or specialty i
Binding: Referral Service Type Value Set (extensible)
Invariants: ele-1
priority S 0..1 code routine | urgent | asap | stat
Binding: request-priority (required)
Invariants: ele-1
doNotPerform ?! 0..1 boolean True if service/procedure should not be performed i
Invariants: ele-1
code S 0..1 CodeableConcept Specific requested service, when more precise than category i
Binding: procedure-code (example)
Invariants: ele-1
subject S 1..1 Reference(Patient Profile) The patient being referred
Invariants: ele-1
encounter S 0..1 Reference(Encounter Profile) Encounter in which the referral was created
Invariants: ele-1
occurrence[x] S 0..1 dateTime, Period, Timing When the referred service should occur
Invariants: ele-1
authoredOn S 1..1 dateTime Date the referral was authored i
Invariants: ele-1
requester S 1..1 Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) Who is making the referral i
Invariants: ele-1
performer S 0..* Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) The service or clinician the referral is directed to i
Invariants: ele-1
reasonCode S 0..* CodeableConcept Why the referral is being made i
Binding: procedure-reason (example)
Invariants: ele-1
supportingInfo S 0..* Reference(Resource) Prior results, notes and documents sent with the referral i
Invariants: ele-1
note S 0..* Annotation Free-text notes on the referral
Invariants: ele-1