Integrations & data · Practice guide

Plan how incomplete healthcare exchanges will be handled

Illustrative situation

A demonstration sends a complete example successfully but does not test how the interface handles incomplete or unsupported information. A perfect sample demonstrates the easiest case. Real handovers can contain missing details or values the receiving system does not accept. Agree what the receiving team should see and do in those situations.

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

Agree representative examples with the implementation team and the accountable business owners. Test error handling and record relationships as well as successful transfer.

An example to discuss with your team

Submit an authorised fictional example that violates an agreed receiving requirement.

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

Ask the supplier to reject an authorised fictional example deliberately and trace its next step. Related records should remain correctly linked and the exception should have an owner. The practice needs a workable resolution process, not only a technical error returned to the sender.

Agree the working process

Build examples with the receiving team as well as the technical supplier. Ask which missing details prevent the intended work and which can be accepted with an appropriate note or later clarification. Those decisions should follow the organisation's authorised processes rather than be invented by the test script. Include a record that is rejected and another whose related information cannot be linked as expected. The reviewer needs a clear explanation of what happened and who can correct it.

Keep the original exchange reference so resubmission can be understood without creating an unrelated duplicate. Test the correction path after rejection, not only the initial error. The business should see whether staff can resolve a problem using the normal working tools. Record acceptance criteria for both successful and unsuccessful examples. A connection is easier to operate when the team knows how it behaves with imperfect information, and when unresolved exchanges remain visible instead of disappearing from an otherwise successful demonstration.

How to check the result

Count rejected exchanges that still lack an owner and a clear next step towards 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.