What to change
An event name is a dependency shared by configuration, reports and any downstream exports. Before combining old and new observations, ask whether the underlying definition also changed. If the meaning is equivalent, document the mapping and transition. If it is different, retain separate measures and explain the break. Validate a current fictional event against the dashboard's actual selection rule, not merely against a debugger that displays all incoming names.
A worked example
Illustrative example
Illustrative test: A test event appears in the intended current measure with the documented meaning. An event named enquiry_sent may replace an older label while the dashboard still selects the former name. The measurement owner first confirms whether both definitions mean accepted receipt. If so, the transition can be mapped transparently; if not, the reporting break remains explicit. A current fictional occurrence is checked in the actual dashboard, ensuring the revised selection works rather than simply appearing in a developer's all-events view.
What this means for your practice
A dashboard may still look for an old event name after the website starts using a new one. That can resemble a sudden fall in activity even when the action continues. Ask the measurement owner to compare the old and new definitions, not just their names. If they measure the same thing, document the transition and update the report's selection. If the meaning changed, keep the measures separate and explain the break. A current fictional event should appear in the intended dashboard, not only a technical debug view. The practice needs continuity of meaning, rather than a smooth-looking chart assembled from unlike actions.
How to check the result
The report explains the transition without disguising a definition change as business performance.
A mistake to avoid
Combining similarly named events can join fundamentally different actions.
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.