Referral intake
Record patient reference, service, referral type, received date, source, owner and summary.
New care-coordination range
Local product demonstratorMeridian Access & Referrals
Track referral completeness, ownership, contact attempts, waitlist status and recorded appointment offers in a visible worklist.
From intake to the next human decision.
Access helps teams see where a referral is in its administrative journey and what information or action is still needed. A service can record intake, keep contact history, identify incomplete records and track a locally recorded offer or outcome. Clinical priority is separately entered and confirmed by authorised staff.
What the AI does. What people decide.
The actual assistance
This implementation uses explicit workflow state and completeness fields. A model does not assign urgency, determine eligibility, choose a treatment or accept a referral. Intake can originate from a reviewed Voice workflow, but the source label in the form is not evidence that an external connector is running.
Human ownership
Administrative coordination only. No autonomous clinical triage, eligibility decision, external referral transmission or live appointment booking is provided.
Features in the current workspace.
Source classification
Label manual, voice, patient-app, e-Referral Service or other-system origins as applicable; labels do not execute integrations.
Information gaps
Record missing required items and track incomplete or returned referrals for follow-up.
Review and queue stages
Filter received, incomplete, ready-for-review, accepted, waitlisted, booked and closed states.
Human clinical priority
Allow an authorised person to record priority with an explicit confirmation; no model chooses it.
Contact history
Record contact attempts and outcomes, retain who acted and when, and maintain the next contact due date.
Appointment-offer tracking
Record offered slot details and their local outcomes without claiming a live booking was made.
Worklist measures
Show open referrals, incomplete records, waiting-for-review items, overdue contact and waitlisted work.
Transitions handoffs
Referral gaps, ready-for-review state and contact dates can become tasks in the shared coordination queue.
From first input to a reviewed next step.
- 01
Record intake
Capture the referral’s administrative context.
- 02
Check completeness
Identify missing items and the next contact date.
- 03
Assign review
A named person reviews the referral and any priority.
- 04
Coordinate access
Record contacts, offers and stage changes.
- 05
Close the loop
Retain the local outcome and any further handoff.
How the product works.
| Area | Mechanism and scope |
|---|---|
| Explicit states | The Access routes validate referral fields and stage changes and persist the local record. |
| Activity records | Contact and slot-offer events retain actor/time metadata alongside the referral. |
| Priority confirmation | Clinical priority is a human-entered field with an explicit staff confirmation path. |
| Connector boundary | NHS e-RS, BaRS and live scheduling require separately approved interfaces; choosing a source label does not connect them. |
Product evidence and source notes
Content checked against the v25.2.0 source and visible local workspace on 30 October 2026. This is a product description and interface inspection, not an end-to-end deployment or clinical validation.
routes/access.py; static/access.js; RELEASE_NOTES_v24.7.0.md
Review assurance scopeQuestions about Access & Referrals.
Does choosing NHS e-Referral Service connect to e-RS?
No. It records the declared origin. A live integration requires its own approved implementation.
Can it set referral priority automatically?
No. The current workflow requires authorised staff to enter and confirm clinical priority.