Why Conflict Highlighting Is a Clinical Safety Feature
When local guidelines disagree with national guidance, patients are at risk. Automatic conflict detection can help.
One of the most dangerous scenarios in clinical practice is when a local trust guideline contradicts national guidance — and the clinician doesn't know.
A Real-World Example
Consider a trust VTE protocol that still recommends 14 days of thromboprophylaxis after hip replacement, while NICE NG89 now recommends 28 days. A junior doctor following the local protocol in good faith would be providing sub-optimal care.
How Conflicts Arise
Guidelines become outdated for several reasons:
- Update lag — trusts may take months to align with NICE updates
- Local variation — some trusts intentionally deviate based on local audit data
- Version control failures — old PDFs circulating on shared drives
Automatic Conflict Detection
Torr Health compares evidence across three tiers:
- Local trust guidelines — your institution's protocols
- National guidance — NICE, SIGN, BNF
- Primary evidence — recent systematic reviews and RCTs
When these sources disagree, an amber "Conflict detected" callout appears with side-by-side comparison and a "Clarify locally" prompt.
The Safety Case
Automatic conflict highlighting isn't just a nice feature — it's a clinical safety mechanism that can prevent guideline-mediated harm.
Ask Torr Health about this topic
Get evidence-based answers with citations from NICE, PubMed, and your trust's guidelines.
Try Torr Health free