Three years is long enough for a practice to change its software, for you to move house twice, and for the memory of one frightening evening to soften into a story. The medicine that harmed him has not changed, though, and neither has his vulnerability to it. The task is not recording the reaction; it is building the warning into every doorway he will ever walk through.
A Warning Summary at the Front
Put the warning where a stranger meets it first. The front page of his file should carry a short reaction summary: the medicine's name, what the reaction looked like in him, when it happened, and how it was resolved, written plainly and dated. Not the full clinical record, which sits behind it, but a headline no one has to dig for.
Front placement matters because of how new practices absorb a patient. Registration staff scan what arrives, clinicians read summaries under time pressure, and a warning on page nine of a transferred file competes with everything else in a thick history. The same warning at the front, repeated in your own words on any registration form that asks about past problems, gets read while there is still time to act on it.
Hand It Over at Registration, Every Time
Deliver the summary at registration, before his first appointment, not during it. Walk it in, send it ahead with his records request, or hand it to reception with a sentence spoken out loud: he had a serious reaction to a named medicine three years ago, and it needs to be flagged on his record. Saying it as well as filing it creates a human memory alongside the paper one.
Do this at every new practice without exception: the permanent clinic after a move, the emergency practice you register with at midnight, the referral centre seeing him once. Each new record starts blank about reactions until you fill that space, and emergency settings, where history-taking is fastest, are exactly where an unflagged reaction carries the sharpest risk.
Ask for the Flag, Then Verify It
Ask the clinic explicitly to flag the reaction on their own record for him, in whatever alert system they use, rather than assuming the transferred file does the job. A flag interrupts the clinician at the point of prescribing; a paragraph in a scanned attachment does not.
Then verify. At the first visit, ask whether the flag is showing on his record, or call a few days after registering and ask reception to confirm what the alert says. Verification feels fussy until you imagine the alternative, and practices respect it, because an owner who checks the flag is protecting their team as well as his dog. If you change practices again, the cycle repeats: summary at the front, handover at registration, flag requested, flag confirmed.
Keep the summary current, too, and review it whenever anything else in his file changes, because a warning that names a medicine he no longer encounters while omitting the setting where he was treated invites questions at exactly the moment it should settle them. One page, accurate and dated, is worth more than a folder of anxious annotations. If he reacts to anything else, it joins the same front page, and if a vet ever establishes that a suspicion was unfounded, that correction belongs there as well, so the warning stays credible and precise.
His packet should open with that warning wherever it is carried, and Pet Passport in KinsLe places the reaction summary first, ahead of the routine pages every clinic reads later.