Integrations & data · Practice guide

Show which work is affected by a connection problem

Illustrative situation

A monitoring dashboard lists connector status but does not tell reception which enquiries are affected. A list of green or red connections does not tell reception which enquiries need attention. Connect the monitoring view to the work affected so staff can make useful decisions without diagnosing the underlying technology.

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

Connect technical status to the actual workflow and make ownership visible. Operations staff need an understandable affected-work view while suppliers retain the detail needed to diagnose failures.

An example to discuss with your team

Pause a test connection and ask the responsible business owner to identify which work is affected and who should respond.

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

Pause a test connection and ask the operational owner to identify the affected items and next action. The supplier should retain diagnostic detail separately. A visible support route and owner help avoid the delay between noticing a red status and realising who needs to respond.

Agree the working process

Decide what an operational owner needs to know when a connection has a problem. Name the affected process, show the unresolved work or meaningful count and provide the appropriate next action. A receptionist should not have to interpret a connector name to discover that booking requests are delayed. Ask the supplier to retain diagnostic detail for technical support without making it the only available view. Include the age of waiting work where it helps prioritise review and distinguish current failures from already resolved events.

Rehearse a fault with the usual owner unavailable so the backup can use the same information. Agree how staff know someone has accepted responsibility and when they will receive an update. Review alerts and dashboard states that repeatedly cause confusion. The objective is a shared picture of business impact, not simply a more colourful technical screen. Useful monitoring helps the team choose a fallback or contact the right supplier while investigation proceeds.

How to check the result

Measure time from detection to an owned response.

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.