The short answer
Documents are frequently the weakest part of a record system: stored separately, indexed poorly and never reconciled against what was expected.
A missing document usually looks identical to one that was never sent, and nobody investigates the difference.
Where documents get lost
| Failure | Why it is invisible |
|---|---|
| Stored outside the record | Nobody looks there |
| Attached to the wrong patient | Appears filed correctly |
| Received but not filed | Sits in a queue indefinitely |
| Expected and never arrived | Absence is not detected |
| Filed with no useful index | Present but unfindable |
The fourth row is the dangerous one. Somebody is waiting for a result that nobody knows failed to arrive.
Reconcile expected against received
- Record what was requested and when.
- Record what arrived and match it.
- Flag anything outstanding beyond a sensible period.
- Give the list to someone whose job includes clearing it.
- Escalate the ones that stay outstanding.
This single loop catches the most serious document failure there is, and it is straightforward to build once requests are recorded.
Index enough to find things
- Patient, reliably and verified
- Document type
- Date of the content, not the date it was filed
- Source or sender
- Whether it has been reviewed and by whom
The date distinction matters. A letter written in March and filed in June sorts wrongly if only the filing date is recorded, and clinicians read the most recent first.
Confirm before filing
Automatic matching of an incoming document to a patient is useful and occasionally wrong, and a document on the wrong record is a serious error.
Where matching is not certain, require confirmation. The small amount of manual checking is much cheaper than the incident.