A request that touches everyone
A patient has moved city and wants their stored embryos and notes moved to a clinic nearer home. The request arrives as an email. Admin asks for a written request. The lab needs details from the receiving clinic. Consent paperwork needs checking. The receiving clinic sends its own forms. A specialist courier needs booking on a date both labs can accept. Finance checks the storage account. Meanwhile the patient emails every week asking for an update.
Incoming transfers are just as involved, only in reverse. Each one is handled from an email thread and a notebook.
Why transfers drag
- Many steps across admin, the lab, finance and the other clinic.
- No checklist, so each transfer is run from memory.
- Paperwork arrives in pieces from the patient and the other clinic.
- Courier dates depend on two labs agreeing.
- Patients cannot see progress, so they chase.
Transfers are infrequent enough that nobody does them every day, but frequent enough to take real time. That is the classic pattern for a process that lives in one experienced person's head.
What slow transfers cost
Patients feel held back from treatment elsewhere, and their frustration is aimed at your clinic. Staff time goes into repeated emails. A missing document found late can push the courier date back. And inconsistent handling makes it harder to show that each transfer followed your procedures.
| Transfer step | Email-based | Tracked request flow |
|---|---|---|
| Patient request | Email, sometimes informal | Structured request with identity check |
| Paperwork | Pieces across threads | Checklist with uploads |
| Other clinic's details | Emailed back and forth | Captured in the request record |
| Courier | Booked by phone, date in notes | Booking and date recorded, both labs notified |
| Patient updates | When they chase | Status messages at each stage |
There is also the other clinic to think about. Clinics receiving material from you judge your organisation by how smoothly the transfer goes, and many of them refer patients or share donors with you. A transfer handled clearly and promptly is part of a good working relationship.
How we build the request flow
- Patients and other clinics submit transfer requests through a form that captures what is being transferred and where.
- Each request generates the checklist of steps your procedures require for that type of transfer, with an owner for each: admin, lab, finance, clinical sign-off.
- Paperwork from the patient and the other clinic is uploaded against the request and marked as received and checked by a person.
- Finance steps, such as checking a storage account, appear as tasks.
- The agreed courier booking, date and contacts are recorded, and both labs receive the details.
- The patient receives status updates as steps are completed, in wording your team writes.
- Completed transfers keep their full record for future reference.
The flow tracks tasks and documents. Every authorisation, lab procedure and handover is carried out by your staff under your procedures and your regulator's requirements.
What your team gets
A clear list of transfers in progress, with each step's owner and status. Patients get updates without having to chase. Paperwork is in one place when the lab needs it. Anyone on the team can pick up a transfer if the usual person is away.
When questions come up later, the complete record of each transfer is there: who asked, what was checked, who signed off and when the courier collected.
Recognise this?
- Transfers are run from email threads.
- Patients chase for updates on transfers.
- Paperwork arrives in pieces and is hard to find.
- Only one person really knows how to run a transfer.
- Courier dates slip because a document is missing.