Integrations & data · Practice guide

Give problems between suppliers a clear coordinator

Illustrative situation

Two vendors each say their system is working and the clinic is left coordinating an unresolved failure. A failure involving two suppliers can leave the practice carrying messages between them. Agree a coordination owner and what evidence each party needs before an incident occurs. The business should have a clear route even when the cause is uncertain.

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

Define joint support responsibilities and the evidence needed for handover between suppliers. The business should have an accountable coordination owner even when diagnosis spans several systems.

An example to discuss with your team

Rehearse a fictional failure whose cause is initially uncertain.

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

Rehearse a fictional issue neither supplier can initially locate. Who gathers references, requests the next investigation and updates the practice? Confirm actual support scope and contacts. Clear coordination helps prevent each supplier's local success report being mistaken for resolution of the shared problem.

Agree the working process

Prepare a responsibility map for the connected journey, including the contacts and support scope of each supplier. The coordinator does not need to perform every technical investigation, but should know who owns the next action and what evidence is needed for a useful handover. Agree how references, timestamps and observed behaviour are shared through approved channels without circulating unnecessary personal information. Use a fictional failure whose cause is initially unclear. Ask each supplier what it would investigate and what it needs from the other side.

The practice should receive a joined-up update about the affected service rather than two separate statements that each product appears healthy. Include differing support hours and unavailable contacts in the discussion. A workable coordination route must account for those limits. After an incident, review delays caused by missing information or unclear responsibility and improve the handover instructions. This reduces the burden on the practice to translate technical conversations between providers during every shared problem.

How to check the result

Track incidents delayed by unclear supplier ownership.

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.