Healthcare
Referral tracking between clinics
A GP refers a patient to a specialist clinic. The clinic accepts or declines, books the appointment, and sends the outcome letter back. Both sides see where every referral is, and a referral with no response in five days is escalated.
Automatically generated draft
Written by machine against our own engineering playbook. The company is invented; the decisions are the ones we would make on a real build. A reviewed blueprint goes further — nine sections, agreed line by line, and it is what the build is tested against.
Section 01 · What has to work
A secure referral lifecycle tracker that moves patient cases from GP submission to specialist clinic completion with mandatory five-day escalation loops.
Section 03 · Screens
Every screen, and what it is for.
- ›GP Dashboard — GPs create and track referral statuses, with real-time urgency filters loading under 100ms.
- ›Clinic Triage — Clinic staff review incoming queue, instantly accepting or declining cases with one click.
- ›Appointment Booker — Clinic schedulers assign calendar slots, instantly notifying the referring GP.
- ›Outcome Viewer — Specialists upload letter attachments, immediately closing the referral loop for the GP.
Anything not on this list is not in version one. That is what keeps a fixed price fixed.
Section 04 · The data model
What it stores, and who can read a row.
referral
id uuid, patient_name text, gp_id uuid, clinic_id uuid, status enum(submitted,accepted,declined,booked,completed,escalated), clinical_notes text, deadline_at timestamptz, created_at timestamptz
Access · GPs read own clinic referrals; clinic staff read assigned clinic referrals.
appointment
id uuid, referral_id uuid, scheduled_for timestamptz, location text, status enum(scheduled,completed,cancelled), created_at timestamptz
Access · GPs and clinic staff read appointments linked to their accessible referrals.
letter
id uuid, referral_id uuid, file_url text, uploaded_by uuid, created_at timestamptz
Access · GPs and clinic staff read letters attached to their accessible referrals.
Those access rules belong in the database, not in the screens. Someone who edits the address bar still cannot read a row that is not theirs — and the test that proves it blocks delivery if it fails.
Section 05 · States
submitted → accepted → booked → completed | declined | escalated
Most scope arguments three weeks into a build are really arguments about a state nobody named at the start.
Section 06 · Where this breaks
What bites products like this one.
Background jobs failing to flag five-day unread referrals leave urgent cases stuck without escalation.
Run database-level cron triggers updating status to escalated when deadline_at passes without acceptance.
Large PDF outcome letters uploaded on slow clinic connections time out and fail.
Implement direct-to-storage signed URL uploads bypassing the application server entirely.
Section 08 · Deliberately left out
What version one does not do.
- ×Automated SMS patient appointment reminders — adds SMS gateway complexity; build email notifications first.
- ×Two-way calendar sync with external clinic PMS systems — requires custom API connectors; manual slot booking suffices for v1.
This is the section that protects the date, and the only place in the document where somebody says no. It is also why clients trust the rest of it.
Still open
What we would ask before quoting.
- Do clinics require multi-tenant role permissions (receptionist vs specialist), or can all clinic users access the full queue?
- How should the five-day escalation rule handle weekends and public holidays?
Your product, not this one
Get this written for what you are actually building.
Describe it in a sentence and the generator returns the same sections for your own product. Free, no email, nothing saved to a list.
Next step
Find out if your idea fits in 10 working days.
Tell us what you want to build. We reply the same day with a straight yes, no, or here is what we would cut.