Integrations & data · Practical guide

Count genuine widget openings rather than internal redraws

A widget stays open while internal updates repeatedly fire an event labelled opened.

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 to change

Define the user-visible transition that deserves a count. Framework redraws, state updates and genuine reopenings are different occurrences, even if they share code. Ask the developer to compare one opening, a harmless internal update and a close-and-reopen sequence. The report should then reflect the agreed meaning consistently. Keep the test focused on observed event counts so the owner can accept the result without needing to understand the framework lifecycle.

A worked example

Illustrative example

Illustrative test: One opening plus two internal redraws remains one opening event; reopening adds another. A help widget opens once, updates its internal list twice and then closes. The report should not call all three displays separate openings if its definition concerns the visitor opening the panel. The supplier compares that sequence with a deliberate close-and-reopen. Your practice reviews the visible actions and expected counts together, allowing a meaningful reopening to remain measured while technical redraws stop inflating the same headline.

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.

What this means for your practice

A booking or help panel can update internally while remaining open. If each update records another Opened event, the report exaggerates engagement. Define the visible action you want to measure, then ask the supplier to compare three cases: opening once, changing something inside the open panel, and closing then reopening it. The practice can judge that distinction without understanding the software framework. The final count should follow the agreed user action consistently. Suppressing every later event is not necessarily the answer, because a genuine reopening may matter to the question being measured. Keep the definition with the report so future changes preserve its meaning.

How to check the result

Counts correspond to the defined visible transitions across the comparison cases.

A mistake to avoid

Suppressing every later event can hide legitimate repeated interaction.

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.