Integrations & data · Practice guide

Correct information where it is maintained

Illustrative situation

Staff fix an incorrect value in a report but the error returns after the next source refresh. Fixing an error in a report can hide it temporarily while leaving the source untouched. The next update then brings the same problem back. Identify where the information is maintained and use the authorised correction route.

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

Correct the value through the approved process in its main record, then verify the change reaches connected tools. A tidy display should not hide information that remains wrong at the source.

An example to discuss with your team

Correct a fictional source value and follow it through the next refresh.

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

Change a fictional value in its main record and follow the next update through connected systems. Ask how staff see whether the correction arrived. Keep local display changes distinct from source corrections so a tidy report does not conceal information still wrong elsewhere.

Agree the working process

Locate the system where the disputed value is actually maintained and identify who is authorised to correct it. A report or receiving screen may be a copy rather than the place where a lasting change should be made. Ask the supplier to explain how an approved source correction reaches the other relevant tools and what happens if an update fails. Use a fictional example and follow it through the next normal refresh. Inspect the receiving record and any report that relies on it, not just the edited source.

Keep temporary display adjustments distinguishable from a resolved source problem. Otherwise the next refresh can make the issue appear to return unexpectedly. Record the reason and relevant approval for meaningful corrections under the organisation's process. Review repeated reappearances with both source and receiving owners. They may reveal an unclear main record, a second system overwriting the change or a missing update, each of which needs a different remedy.

How to check the result

Count errors repeatedly reintroduced from an unchanged source.

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.