What to change
Review the actual outgoing data and ask which reporting purpose requires each parameter. If unintended collection is confirmed, have the authorised technical owner stop the affected collection and remove unnecessary field values at their source. If real information may already have been sent, involve the responsible privacy and analytics owners to assess the scope and the platform's available deletion process. Keep that assessment separate from proving that future events are corrected; a clean test does not establish what happened previously.
A worked example
Illustrative example
Illustrative test: A sample message is absent from the corrected event while its action count remains. The owner separately records whether earlier collection needs investigation, using restricted evidence rather than copying real messages into the test report. During a fictional form test, the phrase used in the message appears in an analytics parameter even though the approved report needs only an action count. The authorised technical owner removes that collection and repeats the test. A separate responsible owner assesses whether earlier real information may have been affected. The clean new result is recorded as proof of future behaviour, not proof that previous collection never occurred.
What this means for your practice
A marketing report may need to know that an enquiry was sent without receiving the message someone typed. Ask your supplier to inspect actual outgoing measurement data using a distinctive fictional phrase. Review which reporting purpose requires each field. If unnecessary collection is confirmed, the authorised technical owner should stop it and verify the corrected action count. Any question about earlier real information needs a separate review by the responsible privacy and analytics owners. A clean new test does not establish what was sent previously, and changing a tag does not remove existing data. Keep investigation evidence restricted rather than copying real messages into a general website report.
How to check the result
The current data sent to analytics matches the documented measurement purpose, and any question about previous collection has an accountable review owner.
A mistake to avoid
Hashing unnecessary text does not justify collecting it, and changing a tag does not remove information already sent.
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.
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.