Preventable by design: how real-time interaction checks protect patients

Some clinical risks are exotic and rare. Medication error is neither. It is common, extensively studied, and — more than almost any other harm in medicine — a function of how the work is organised rather than of who is doing it.

This article describes what a prescribing check does at the moment a prescription is written: what it reads, what it stops, and what it records afterwards. On what a prescriber must verify before signing, the reference that binds is the clinician's own. What follows is the software's behaviour.

Two documents that moved the field

The framing that treats medication error as a system property rather than a personal failing rests on two well-known pieces of work, and both are worth reading in the original rather than in a vendor's paraphrase.

Both conclusions point the same way. If the error is systemic, the intervention has to sit inside the workflow that produces it — at the moment of prescribing, not in an audit read three months later.

What the check actually reads

A prescribing check is only as good as the list underneath it. In Doctopass, drug–drug and drug–allergy checks run against the patient's own record, cross-referenced through RxNorm and the Tunisian formulary, on every prescription. The allergy safety block sits beside it. Both start on Pro.

That dependency is the whole argument for consolidation. A checker reading one of four scattered records is a checker that will miss the allergy noted on paper last spring, or the medicine a specialist added between visits — which is why the cost of a fragmented record is a patient-safety question before it is an administrative one, and why medication adherence depends on the same single list.

Blocking, and the override that is logged

A dangerous combination blocks. That is the first half of the mechanism and the easier half to build. The second half is the override: where the prescriber judges the combination correct for this patient, the decision is recorded with their stated reason, next to the block that preceded it.

Both halves are load-bearing. A barrier that cannot be crossed stops care. A barrier crossed with no written reason is a decision nobody can explain a year later. The behaviour is set out in full in interaction checks that block, and it follows the same rule as every other AI output on the platform: the software proposes, the doctor decides, and nothing is written until a doctor signs.

Where that written reason ends up is the second gate in the table below. The full audit trail — every read and every write of patient data, with who and when — is on Pro and Premium. Audit log search with the investigation interface is Premium only. On Pro the reason is still recorded and still available to the responsible doctor; what Premium buys is the ability to go looking across a year of overrides rather than opening one consultation at a time.

The gate is worth printing rather than describing. Essential carries the record and digital prescriptions but no interaction checking at all; the checker and the allergy block start at Pro. We would rather write that limit down than let it be discovered after signature.

What we will not publish

We will not publish a list of combinations that ought to stop a prescription, and we will not tell a doctor what to verify before writing one. Clinical judgement is the prescriber's, and the reference that binds them is theirs. A vendor issuing a rule on a professional body's behalf is how a practice ends up defending a protocol it inherited from a brochure.

Nor will we publish an error rate you should expect, or a percentage of harm the software removes. We have no measurement of your practice, and a figure borrowed from another health system and rescaled is not evidence, it is decoration.

Frequently asked

Can I override a block?

Yes, and the override is the designed path rather than a workaround. Where you judge the combination right for this patient, you proceed and the system logs your reason alongside the alert. The clinical decision stays yours; what changes is that it becomes explicable later.

What does the checker read?

The patient's own medication list and recorded allergies, cross-referenced through RxNorm and the Tunisian formulary. It does not read a record held in another system, which is the practical reason a consolidated file matters more than any single alert.

Which plan carries it?

Pro, at 159 DT. Essential, at 69 DT, carries the record, the calendar and digital prescriptions without the AI safety layer; Premium, at 269 DT, adds audit log search and the investigation interface above the full trail. Per doctor, per month, billed annually, after a fourteen-day trial — the full comparison sits on the pricing page.

A safety net you can walk through is decoration. One that catches you at the exact moment you would have fallen, and writes down what you decided next, is worth the rare interruption. To watch a real prescription hit a block and see what the trail records, request a 30-minute demo.