Integrations & data · Practice guide

Find records missing between connected systems

Illustrative situation

Both systems appear healthy but several records never arrived at their intended destination. Both systems can be available while individual records are missing between them. Periodically compare what should have arrived with what actually arrived, over a clearly defined period and using agreed references.

Healthcare booking calendars on two connected screens with blue and orange appointment cards.
Make the handover between tools clear for the team using them.

What this means for your practice

Compare the results expected over an agreed period with what actually arrived. A green availability indicator shows a different thing from a complete transfer of the required work.

An example to discuss with your team

Remove one fictional event from the test set and run the agreed comparison. Check that the missing result is identified for review.

Healthcare data integration connecting two applications through a field-mapping board.
Agree what each field means and which system owns it.
Healthcare data validation separating matched records from an exception tray.
Make rejected or uncertain records visible for review.

Questions to take to your supplier

Remove a fictional event from a test transfer set and run the comparison. Does the gap appear with enough detail for its owner to investigate? Agree how resolved differences are recorded. Availability and complete handover answer different questions and both may matter to the practice.

Agree the working process

Define the period and the expected records to compare, with stable references that both sides can explain. Availability checks show whether systems respond; this comparison asks whether the work expected in a period actually reached its destination. Agree how late arrivals, repeated events and authorised exclusions are handled so ordinary differences do not create a permanently noisy list. Ask the supplier to remove one fictional transfer from a test set and show how the gap is identified. Then resolve it and confirm the evidence remains connected to the original item.

Give uncertain matches an owner rather than forcing a count to balance through assumptions. The receiving team should be able to understand which items need review and why. Keep the comparison method current when new sources or event types are added. During reporting, distinguish unresolved gaps from reviewed differences with an accepted explanation. That makes the result useful for prioritising work instead of presenting every mismatch as equally urgent.

How to check the result

Count unmatched events awaiting a documented resolution.

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 integrations & data services or discuss your project.

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