Two people, one record, and a lot of workarounds
A heterosexual couple, a same-sex couple, a single patient using donor sperm, a patient who has treatment with a new partner years later, a couple who separate while embryos are stored. Each is normal in a fertility clinic, and each strains a system designed around one patient.
The admin team deals with the fallout. A letter goes to the wrong partner. A partner has two records because they were registered once as a partner and again as a patient. An invoice is addressed to someone who is no longer a partner. Staff learn to check everything twice.
Why the records get tangled
- The partner is stored as details on the main patient's file rather than as a person in their own right.
- The same person is registered twice, once as partner and later as a patient.
- Links are made for the relationship, not for a treatment episode, so changes over time are hard to show.
- Separation and new partners are recorded in free-text notes.
- Letters and invoices pull addresses from whichever record happens to be linked.
Donors add another layer. A known donor may also be, or later become, a patient, and a donor's details must stay separate from recipients' records under your policies. When the system has no clean way to represent people and their roles, staff invent their own conventions, and each one differs slightly from the last.
What tangled records cost
Wrongly addressed letters are a confidentiality incident, not just an annoyance. Duplicate records mean paperwork is split between files. Billing goes wrong when accounts are tied to the wrong person. And staff spend time making manual checks the system should support.
| Situation | Common workaround | With proper linking |
|---|---|---|
| New partner years later | Overwrite the old partner details | New episode linked to a new person |
| Partner becomes a patient | Second record created | Existing person record reused |
| Couple separate | Note on the file | Separate contact and billing per person |
| Letters about shared matters | Addressed from one file | Sent to each person according to your policy |
How we fix it
- We review how your clinic management system stores partners and where its limits are.
- Where the system allows, we build a person-based linking model on top of it: each individual has one record, and people are linked through a treatment episode.
- A duplicate check runs on new registrations and on a schedule, proposing possible duplicates for a person to review.
- Letters and invoices are generated from the episode, so each goes to the correct individual using that person's own contact details.
- Changes in relationship status are recorded in structured fields, with the date, and affect who receives what from then on.
- A clean-up queue works through existing tangles, with staff confirming each merge or split.
Merging records is never automatic. The system proposes. A person checks and confirms, and anything clinical is referred to your clinicians.
The result day to day
Admin staff stop double checking every letter. Duplicate records are caught at registration. When circumstances change, the records show it clearly, and communication and billing follow automatically.
Reporting improves as a side effect. When each person exists once, counts of patients, partners and donors stop double counting, and questions such as 'how many patients returned for treatment with a new partner?' can be answered without a manual trawl through notes.
Recognise these problems?
- The same person has more than one record.
- Letters have gone to a former partner.
- Partner details are overwritten when a patient has a new partner.
- Billing is tied to the wrong person in a couple.
- Separation and consent changes are stored in notes.