Software & apps · Practice guide

Spot duplicate referrals without guessing identity

Illustrative situation

The same referral arrives through a portal and by email, creating two parallel administrative tasks. Duplicate referrals mean duplicate calls, repeated checking and conflicting updates. A similar name is not enough to conclude that two submissions are the same person or request. Give an authorised colleague enough information to make that decision and leave uncertain cases separate until they are checked.

Healthcare scheduling software, planning board and organised folders in a blue, white and orange office.
Choose software around the work your team needs to do.

What this means for your practice

Flag possible duplicates for authorised review using the organisation's identity rules. Do not automatically merge uncertain records based on a similar name alone.

An example to discuss with your team

Create two fictional records with similar names; the reviewer must be able to keep them separate.

Healthcare software workflow connecting task cards, a checklist and a database.
Map the work and the information it depends on.
Healthcare software testing with normal paths and a separate exception route.
Test the exceptions as well as the normal workflow.

What to ask before you choose

Ask the supplier to demonstrate one referral arriving by email and through a portal, followed by a different person with a similar name. The reviewer should see the source and reference of each submission. If records are combined, the reason and original submissions should remain traceable, so the team can explain the decision later.

Give the reviewer a clear comparison

A duplicate warning should help an authorised person compare the arrivals, including their sources, references and timing. It should not encourage them to resolve the warning simply to clear a queue. Explain the practice's identity-checking process to the supplier and agree who is allowed to make a decision.

Use examples that could be confused: the same referral resent with a missing attachment, two separate requests from one person and different people with similar names. The reviewer needs to be able to keep records separate when the relationship is uncertain. If two submissions are confirmed as the same request, retain enough history to explain what happened and where each original can be found. Check what happens to any tasks already assigned before the duplicate was noticed. Otherwise a combined record can still leave two colleagues contacting the sender independently, even though the warning itself has disappeared.

How to check the result

Track duplicate tasks discovered after work has already started.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore software & apps services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.