This page is part of the Magentus Practice Management FHIR Implementation Guide (v1.3.2: Releases Draft) based on FHIR (HL7® FHIR® Standard) R4. No current official version has been published yet. For a full list of available versions, see the Directory of published versions

Referrals

The Magentus Referrals Service supports the creation and tracking of clinical referrals to specialists. It follows the same ServiceRequest/Task pattern used by the Requesting Service — a GSReferralRequest (ServiceRequest) captures the referral content and a GSReferralTask (Task) tracks its fulfilment lifecycle.

Note: This module is in draft. The profiles and examples are available but the integration workflow is not yet fully implemented. Do not build production integrations against this module without confirming the current server support with Magentus.

Profiles

Magentus Profile	FHIR® Resource
Referral Request	ServiceRequest
Referral Fulfilment Task	Task

Workflow

Creating a Referral

A placer creates a GSReferralRequest containing:

• The patient (subject)
• The requesting clinician (requester — a GSPractitionerRole)
• The referred-to specialist or service (performer — a GSPractitionerRole, GSOrganization, or GSHealthcareService)
• The reason for referral (reasonCode — required)
• Optional supporting clinical information (conditions, observations, procedures, allergies, medications, and/or an attached PDF letter)

A GSReferralTask is created alongside the request with:

• focus referencing the GSReferralRequest
• status = #requested
• owner identifying the specialist or service to fulfil the referral

Task Status Lifecycle

The Task status follows the same pattern as eOrders fulfilment tasks:

Status	Meaning
requested	Referral created, not yet acknowledged
received	Referral received by the specialist
accepted	Specialist has accepted the referral
in-progress	Referral appointment or consultation underway
completed	Referral fulfilled; specialist letter available via Task.output
rejected	Referral declined by the specialist
cancelled	Referral cancelled by requester

When the referral is completed, Task.output should carry a reference to the specialist's letter (e.g. a DocumentReference or Binary resource).

Supporting Clinical Information

The GSReferralRequest.supportingInfo element accepts:

Profile	FHIR® Resource
AU Core Condition	Condition
AU Core Observation	Observation
AU Core Procedure	Procedure
AU Core AllergyIntolerance	AllergyIntolerance
AU Core MedicationStatement	MedicationStatement
Binary	Binary — attached referral letter PDF

Examples

Example
Referral Request
Referral Task