Patients rarely describe diversion in those terms, but they routinely describe its effects. A complaint that pain was never relieved despite a documented administration, a report that medication went missing from a bedside drawer or a home supply, or repeated frustration over an early refill denial are all patient-side descriptions of a dose that may not have reached the person it was intended for. Taken individually, each complaint has an ordinary clinical or administrative explanation, and most of them are exactly that. Captured in a structured log and reviewed in aggregate, however, they become one of the few diversion signals that originates entirely outside the dispensing record. When several such complaints cluster around a single staff member, a shift, or a single care area, that pattern warrants a documented review.
Building the Complaint Capture Workflow
Most organizations already collect patient complaints somewhere — a patient relations system, a nursing unit log, a pharmacy call record, or a prescriber’s note. The problem is not collection; it is that complaints are resolved individually and then closed, with no mechanism that allows the twelfth complaint to be read alongside the first eleven. Converting complaints into a diversion control requires three structural changes.
First, define the complaint categories that carry diversion relevance and tag them explicitly: analgesia reported as ineffective despite a documented dose, patient-reported missing medication, and early refill or early request denials that generate a complaint. Second, capture the operational context at intake — date and time, care area or pharmacy location, the medication involved, and the staff member who administered or dispensed the dose. A complaint with no associated administration event cannot be clustered later. Third, assign a single owner, typically the diversion prevention coordinator or a designated pharmacy leader, who reviews the tagged complaint set on a fixed cadence rather than reacting to each entry in isolation.
What the Clusters Look Like
The signal is concentration, not volume. A patient who reports poor pain control is unremarkable; a nurse or technician who appears in the administration record for a disproportionate share of such reports, relative to their share of controlled substance administrations, is a pattern. Specific configurations worth escalating include:
- Ineffective-analgesia reports concentrated on one administering staff member across multiple patients, particularly when the same patients report adequate relief from doses given by other staff.
- Patient-reported missing doses from a bedside supply, a home delivery, or a dispensed quantity that recur in one care area or on one shift.
- Complaints about early refill denials where the pharmacy record shows a fill history inconsistent with the quantity the patient states they received.
- Complaints that coincide with other monitoring signals — automated dispensing cabinet override activity, unwitnessed waste, discrepancy resolutions, or count variances involving the same individual.
- A rise in complaints following a schedule or assignment change that moved a specific staff member into a new unit or shift.
A complaint cluster is a reason to look, not a conclusion. Substitution, tampering, understaffing, inadequate prescribing, poor patient education, and pharmacy workflow failures all produce similar complaint profiles, and the review must be capable of reaching those findings as readily as a diversion finding.
Documentation Standards
Document the complaint in the patient’s own terms and separate observation from inference. Record what the patient reported, when, which medication and dose were involved, and what the administration or dispensing record shows — and stop there. Do not record a suspicion of diversion, a staff name characterized as a suspect, or a conclusion in the patient-facing complaint record. Analytical work belongs in the diversion program’s investigation file, maintained separately with controlled access under your organization’s peer review or compliance framework.
Every review cycle should produce a record even when nothing is found. A log entry showing that the tagged complaint set was reviewed on a given date, by whom, and with what disposition is what demonstrates that the control operates. Reviews that leave no trace are indistinguishable from reviews that never happened. Retain the review records with your other monitoring output; see the policy templates for a documentation structure you can adapt.
Example Review Workflow
- Extract the tagged complaints for the review period, grouped by care area and by administering or dispensing staff member.
- Normalize the counts against each individual’s controlled substance activity for the same period, so that high-volume staff are not flagged simply for being high-volume.
- Cross-reference any outlier against existing surveillance data — override rates, waste documentation, discrepancy history, and access records for the relevant storage locations.
- Reconcile the specific complaint events against the administration record, the waste record, and the medication order to determine whether the documented dose is consistent with what the patient describes.
- Escalate or close with a written disposition. If the review supports a reasonable suspicion of diversion, route it through your established investigation pathway, involving human resources, security, risk management, and counsel as your policy directs.
- Feed the result back. Where the cause proves to be a workflow or education failure rather than diversion, correct the process and note the correction in the review record.
Regulatory Grounding
21 CFR 1301.71(a) obligates every DEA registrant to provide effective controls and procedures to guard against theft and diversion of controlled substances. That obligation is not limited to physical security; it extends to the monitoring processes a registrant uses to detect loss. A complaint stream that repeatedly describes medication not reaching patients, and that the registrant does not review, is difficult to reconcile with a claim of effective controls.
If a review establishes that controlled substances were in fact diverted, 21 CFR 1301.76(b) requires notification to the DEA Field Division Office upon discovery of a theft or significant loss, with completion of DEA Form 106. The DEA Form 106 guide covers the significant-loss determination in detail. Records generated by the review, including reconciliation against dispensing and administration data, should be retained consistently with the recordkeeping requirements at 21 CFR 1304.21. Where the complaint concerns an outpatient prescription pattern rather than an internal administration, the corresponding responsibility standard at 21 CFR 1306.04(a) may also be implicated in how the pharmacy responds.
Frequently Asked Questions
Q: Isn’t it unfair to track complaints against individual staff members?
A: Tracking is not accusation. The same administration data is already attributable to individuals in the medical record, and diversion surveillance routinely normalizes activity by individual. What protects staff is the discipline of the process: normalize against workload, require corroborating signals before escalation, keep analysis out of the patient-facing complaint record, and document dispositions that clear individuals as carefully as those that do not.
Q: How many complaints constitute a cluster?
A: There is no defensible universal threshold, and adopting an arbitrary number invites both false alarms and missed signals. Set your trigger relative to your own baseline — an individual whose tagged complaint rate is materially above peers performing comparable work, sustained across more than one review period, is a reasonable starting definition. Document whatever threshold you adopt in policy so that reviews are applied consistently.
Q: What if the patient is suspected of drug-seeking behavior?
A: Treat that as a separate question. A patient with a substance use disorder can still be the victim of a diverted dose, and dismissing the complaint on that basis is exactly the failure mode diversion relies on. Evaluate the complaint against the administration and dispensing record on its own merits, and address the patient’s clinical needs through the appropriate care pathway.
The DivertGuard diversion prevention checklist includes complaint-based surveillance among its monitoring criteria, and running it on a fixed schedule gives you a documented record that the control is in place and reviewed.