What to change
Define whether the measure represents accepted submissions or confirmation views. If it represents submissions, ask the developer to connect the event to that occurrence and explain how revisits are treated. Use fictional test activity and record both the receiving system's acceptance and the analytics output. The acceptance case must include reload, back navigation and a genuinely separate submission so a fix does not accidentally suppress legitimate later activity.
A worked example
Illustrative example
Illustrative test: One accepted request with two reloads yields one completion; a separate accepted request adds another.
How to check the result
Observed events match the defined submission occurrences across all tested cases.
A mistake to avoid
Repeated analytics events alone do not establish duplicate patients.
Your action checklist
Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.
Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.
Further reading
These primary sources provide additional context for the project decisions above.
Related decisions
Turn the brief into a working service
Kay & Co. can help you scope the work, design the experience and deliver the right solution for your organisation.
Explore integrations & data services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.