The operating problem
A referral can be accepted clinically while a patient waits for a booking that requires a particular session, room, interpreter or preparation. A general-purpose booking page can show a free time without knowing whether all resources are available. Staff may ring several people for the same opening while other sessions go unused.
System landscape
Electronic referrals enter through an approved health interface. A clinician sets disposition. The patient administration and scheduling systems own bookings. The communications provider reports delivery.
Proposed architecture
Ingest referral receipts through the service’s supported interface, match the patient using approved identifiers and preserve the clinician’s triage disposition. Build a scheduling request containing clinic, appointment type, authorised time window, site and resource requirements. Query the authoritative scheduling platform, reserve an eligible slot where supported, offer it through the approved channel and write confirmation back to the patient administration system.
- Referral interfaceReferral, patient identity and triage disposition
- Booking integrationMatch eligible slots to required resources
- Patient administrationSystem of record for confirmed appointment
- CommunicationsOffer, reply and delivery acknowledgement
- Source recordsElectronic referral and clinical disposition
- ProcessingMatch session, site, resources and patient preference
- Decision ownerBooking team resolves identity or capacity exceptions
- Operational outputConfirmed appointment, reminders and outcome
Existing platforms and practical interfaces
NSW Health documents HealthLink electronic referrals from general practice systems into its electronic Referral Management System for participating outpatient clinics. The Royal Melbourne Hospital separately documents an SMS waitlist audit with specialty-specific responses and a recovery path for an incorrect reply. These are distinct Australian workflows. A new implementation must establish which referral, PAS, scheduling and messaging interfaces the particular health service permits.
Operating the service across sites
For a network rollout, agree clinic-specific resource templates and a shared definition of ready-to-book. Keep site-specific escalation contacts and local preparation rules. Start with a specialty that has a stable session template, then test a specialty with shared equipment or interpreters before enabling unattended appointment confirmation. Use secure messaging or approved FHIR resources only where the vendor supports the required operation.
Reliability and operating controls
Clinical urgency and suitability remain with the treating service. Offers expire without removing a patient from care. Confirm eligibility again before writing a booking. Where the scheduling interface cannot hold a slot, perform an immediate availability check at commit and recover from a conflict. Provide a staff-assisted path for changed contact details, interpreters and people unable to use digital channels.
Illustrative operating scenario
A specialist cancels an afternoon session at one site. The scheduler identifies affected bookings and retains each patient’s clinical priority and support needs. A comparable slot opens at another site, but one patient requires an interpreter who is unavailable there. That offer goes to a suitable patient while the booking team retains an owned task for the first patient.
Delivery boundaries
The integration scope covers administrative intake and booking within the health service’s supported interfaces. Clinicians own triage and care decisions. The service’s privacy, clinical governance and platform teams own data access and release approval.
Expected business impact
Booking staff could spend fewer calls resolving routine offers, recover eligible slots after cancellations and see which patients require assistance. Compare time to booking and failed notices by clinic and channel.
Acceptance test and handover
Measure time from ready-to-book to confirmed appointment, slots recovered after cancellation, duplicate bookings, failed notices and staff touches per completed booking. Review results by clinic and communication channel. An improvement achieved by dropping people who cannot use SMS is a failure.
Test a reply after expiry, two simultaneous acceptances, a changed referral, a cancelled clinic session, duplicate referrals and failed message delivery. Confirm that each slot has at most one accepted booking and each patient retains a visible next action. Give booking staff a recovery queue, a daily capacity report and a way to continue during a messaging outage.
Industry evidence
NSW Health · Electronic referrals and participating outpatient clinics
Royal Melbourne Hospital · Specialist clinics waitlist audit
Victorian Department of Health · Minimum information for specialist referrals