Full context
Snapshot model
Each referral carries a full snapshot — chief complaint, vitals, draft Rx, attached labs, recent visits.
Referrals A referral is a clinical handoff,
A referral is a clinical handoff,
not a phone number.
Structured snapshots, need-info loops, status lifecycle. The receiving doctor sees what you saw. The patient sees the status. Nothing falls through the cracks because nothing relies on a phone call.
Snapshot model · 5-state lifecycle · In + out of network
Capabilities
What a real referral does.
Eight things that set apart a structured referral from a sticky note. Built with GPs and specialists who got tired of WhatsApp screenshots.
Live
In-network send
To another doctor on MediSero+, the referral lands in their inbox. No paper, no phone call, no screenshots.
PDF + email
Out-of-network
PDF + signed link to a non-MediSero doctor. They can view + reply via email; your timeline updates either way.
5 states
Status lifecycle
Sent → need-info → visit-required → accepted → completed. Both sides see the same state.
Round-trip
Need-info loop
Receiving doctor can ask for missing info before accepting. Round-trips happen in the app, not over WhatsApp.
Always visible
Patient kept in loop
Patient sees the referral in their app — who, when, why, status. No more "did the doctor refer me yet?"
Conversion
Referral analytics
Conversion rate, time-to-accept, top specialists you refer to. Build a feedback loop.
Logged
Audit + consent
Patient consent captured before the snapshot leaves. Every send/view/edit logged.
Lifecycle
Five states. Both sides agree.
The sending doctor, the receiving doctor, and the patient all see the same status at the same time. No phone tag.
01
Sent
Doctor A creates the referral with a snapshot. It lands in Doctor B's inbox (in-network) or as a signed-link email (out-of-network).
02
Need-info
Doctor B asks for missing context — "any prior ECG?", "BP trend over 30 days?". Doctor A replies with attachments. No phone call.
03
Visit-required
Patient must be seen first. Doctor B requests a visit; the patient gets a notification with a booking link.
04
Accepted
Doctor B accepts. They're now responsible for the next step. Doctor A's view shows the patient as referred-out + accepted.
05
Completed
Doctor B saw the patient; reply summary + advice attached. Visible to Doctor A and the patient. Loop closed.
Use cases
Four shapes of referral.
Same model, different surfaces. Internal, external, lab/imaging, hospital — all run on the snapshot + lifecycle pattern.
Internal referrals
Multi-doctor clinic: GP → cardiologist down the hall. Same workspace, instant.
External referrals
Solo GP → specialist in another city. PDF + signed link if they're not on MediSero.
Lab/imaging orders
Treat as a referral to the lab. Status updates when the report comes back.
Hospital admissions
Send a structured admission packet — vitals, current Rx, allergies, recent visits.
My old workflow: take a screenshot of the EHR, open WhatsApp, send to the cardiologist, hope he saw it. New workflow: tap Refer, pick the doctor, sign. He gets vitals, ECG, Rx, my note. He acks in 12 minutes. Patient knows he's coming.
FAQ
Referral questions, answered.
What if the doctor I'm referring to isn't on MediSero?
They get a signed-link email with the snapshot as a viewable HTML page + a downloadable PDF. They can reply via email, and the reply lands back in your timeline. Your patient sees the same state on their end.
How does need-info work?
When the receiving doctor opens the referral, they can mark it as need-info with a list of asks ("prior ECG", "fasting glucose"). You get a notification; you reply by attaching files or notes; status moves to accepted (or back to need-info if more is missing).
Does the patient know they've been referred?
Yes — the referral shows up in their patient app with status, who they've been referred to, and what they should bring. No more "did the doctor send the referral yet?"
Can I keep referrals private from the patient?
Some clinical scenarios (e.g. mental health, sensitive screening) allow you to mark the referral as doctor-only. The patient sees they've been referred, but not the snapshot contents — only the receiving doctor can.
How is consent captured?
Before the snapshot leaves your clinic, the patient must consent (verbal or in-app tap). The consent is logged with timestamp, doctor ID, scope of data shared. Audit-ready for DPDP Act 2023.
Make every referral a structured one.
14 days free. In-network is one tap. Out-of-network is signed PDF — both work the same way.