IRT Commandment #10
Thou Shall Not Have Hard Stops
Through experience gained from the early days of IVRS, this principle has largely been adopted. Yet there are still those who continue to insist on hard stops, grinding transactions to a halt and requiring human intervention before the system will proceed.
In theory, hard stops can appear disciplined. In practice, they often create friction at the exact moment care must move forward.
My experience has been that hard stops are almost always overridden when a patient is physically on site. It is in that moment that sponsors recognize the difference between the theoretical world of a written protocol and the real world in which sites and patients operate. This leads to panic and scrambling to override the system or initiate a manual intervention.
That tension is not new. It simply seems to be continually unrecognized.
The Protocol vs. The Patient
Sometimes visits occur outside of defined windows. Sometimes dosing must happen despite imperfect timing. Sometimes real life does not align neatly with system logic.
Not allowing a patient to be treated because a system refuses to proceed is not discipline. It is rigidity, and in the wrong moment, it can be unethical.
This is not an argument for ignoring the protocol. It is an acknowledgment that clinical care does not always unfold in perfect alignment with theoretical design.
Alignment with Earlier Commandments
Commandment #1 reminds us that IRT should serve its primary purposes. Overextending system control beyond those purposes creates unnecessary barriers.
Commandment #3 reminds us to respect what the system records versus what occurs in the clinical environment. A transaction date and a visit date may differ. That does not make one wrong.
Commandment #9 reminds us that there is often a patient waiting. Systems are used by sites in service of real people.
Hard stops ignore all three principles.
They assume that control is more important than care.
Control Without Paralysis
Systems should guide.
They should warn.
They should document.
But they should not prevent appropriate clinical action from occurring.
If a visit falls outside a window, the system can capture it.
If an exception occurs, the system can document it.
If follow-up is needed, governance processes can address it.
The Takeaway
There is a difference between protecting protocol integrity and impeding patient care.
Design systems that guide and record.
Avoid designs that paralyze.
Because when the patient is sitting in the room, theory gives way to reality.
And reality must prevail.