The Clock That Started Before You Knew

Part of Pharmacovigilance and Drug Safety (PV) Training: The Reporting Clock.

About 2 minutes. Free, in your language, no account needed.

Inheriting a case with days already gone

You open a case on Wednesday. Reading it, you find the event was described in an email to a medical information mailbox the previous Thursday. Six of your fifteen days are already spent.

This is common, and how you handle it defines the difference between a safety function that works and one that looks tidy.

What to do first

Establish day zero and record it as what it actually was. Then work to the deadline that follows from it, not the one that would follow from your own awareness.

If the remaining time is not enough, escalate immediately. A deadline about to be missed is a management problem the moment it is known, not at the moment it is missed.

Do not re-date the case

The temptation is to treat the date the case reached the safety database as day zero, because that is when the process you control began. This is wrong, and it is wrong in a way that is discoverable: the original email carries a timestamp, and an inspector reading both will see it.

A late report submitted with an honest day zero is a compliance finding with an explanation. A report dated to conceal lateness is a different category of problem entirely.

Fixing the cause, not the case

Every case that arrives with days already gone points at a route into the company that is not forwarding quickly enough. Record where it came from. The pattern across cases is what lets somebody fix the route.

That is the practical value of recording the source function honestly on every late case: it converts an individual embarrassment into the evidence needed to change a process.