Terms to Avoid When Documenting a Practice Incident in Pharmacy
How a practice incident is documented matters just as much as what is documented.
Across Canada, Continuous Quality Improvement (CQI) programs, such as CQI+ in Alberta, CIRCL in British Columbia, AIMS in Ontario, and similar frameworks in other provinces, emphasize learning, system improvement, and patient safety. Language that assigns blame, implies intent, or creates ambiguity can undermine these goals and weaken safety culture.
This article outlines common terms to avoid when documenting practice incidents and close calls, and explains why choosing the right language supports better learning, stronger CQI, and safer patient care.
Why Language Matters in CQI Documentation
Incident documentation is not a legal judgment or performance evaluation. Its purpose is to:
- Understand what happened
- Identify contributing system factors
- Prevent recurrence
- Support continuous improvement
Certain words carry unintended meanings that shift focus away from systems and toward individual blame. Over time, this discourages reporting, limits learning, and weakens safety culture.
Using clear, neutral, and consistent language helps pharmacies meet CQI expectations while fostering openness and trust.
Key Terms to Avoid and Why
1. “At-risk behaviour”
Use instead: Noncompliant behaviour
“At-risk behaviour” is vague and subjective. The preferred term is noncompliant behaviour, which refers to actions that are not consistent with approved policies and procedures.
This wording:
- Describes what occurred without judgment
- Focuses on alignment with procedures
- Allows analysis of why the procedure was not followed
In most cases, noncompliant behaviour reflects system pressures rather than intentional actions.
2. “Blame”
Assigning blame to an individual fails to recognize the complexity of healthcare systems. Medication incidents rarely have a single cause.
Blame-based language:
- Discourages reporting
- Oversimplifies events
- Prevents identification of system contributors
CQI programs across provinces emphasize learning, not blame.
3. “Error” (when attached to anything other than “human”)
Only humans make errors. Terms such as:
- Medication error
- System error
- Organizational error
oversimplify what actually occurred.
Preferred approach:
- Describe the event or outcome
- Identify contributing factors
- Avoid labeling the incident itself as an “error”
This keeps the focus on understanding, not labeling.
4. “Fault”
“Fault” implies defect or blameworthiness. Its use can unintentionally assign responsibility to an individual before analysis is complete.
CQI documentation should describe:
- What happened
- Under what conditions
- Why the system allowed it to occur
Avoiding “fault” supports objective analysis.
5. “Near miss”
This term is widely used but often misunderstood.
Literally, a “near miss” means something almost missed its target, which implies harm occurred. In pharmacy practice, the event usually did not reach the patient.
Preferred term: Close call
“Close call” clearly communicates that:
- The event was identified in time
- No harm reached the patient
- Learning is still required
This term is widely accepted in pharmacy CQI programs.
6. “Negligence”
Negligence is a legal term and should be reserved for court proceedings and legal determinations.
Including it in CQI documentation:
- Is inappropriate
- Discourages reporting
- Shifts focus away from system learning
CQI documentation should never attempt to determine legal responsibility.
7. “No-harm event” or “No-harm incident”
These terms are ambiguous. They may refer to:
- An event that did not reach the patient (a close call), or
- An event that reached the patient but caused no detectable harm
Ambiguity weakens data quality and learning. Use clear descriptions instead:
- Close call, or
- Practice incident with no observed harm
8. “Preventable”
“Preventable” implies certainty and choice that may not exist. It can unintentionally suggest negligence or inevitability.
A better approach is to ask:
- What conditions contributed?
- What changes might reduce future risk?
This keeps analysis constructive and realistic.
9. “Punish”
Punitive language has a chilling effect on reporting.
Preferred term: Discipline, used only when appropriate and separate from CQI documentation.
CQI processes should remain distinct from performance management.
10. “Reckless” or “Recklessness”
Like negligence, these are legal terms and should be avoided in CQI documentation.
Their use prematurely assigns intent and discourages open reporting.
11. “Risk” attached to behaviour terms
For example, “at-risk behaviour”.
This phrasing is subjective and often redundant. Focus instead on:
- What action occurred
- Whether it aligned with procedures
- What system factors influenced the action
12. “Serious” adverse event or “serious” harm
“Serious” is subjective and varies between providers and patients.
Instead:
- Describe the actual outcome
- Document clinical impact clearly
- Avoid qualitative labels
13. “Unnecessary harm”
“Unnecessary” implies that some harm may be acceptable, which is difficult to justify and interpret.
Stick to objective descriptions of harm and contributing factors.
How Using the Right Language Strengthens Safety Culture
Choosing appropriate terminology:
- Encourages reporting of incidents and close calls
- Improves quality of analysis
- Aligns with CQI expectations nationally
- Reinforces a just and learning-focused culture
Language sets the tone for how safety is experienced in the pharmacy.
How PhIX Supports Clear, Consistent Documentation
PhIX (Pharmacy Incident Exchange) is designed to support high-quality, just-culture-aligned documentation across Canada.
PhIX Features and Capabilities
- Structured incident and close call reporting
Uses neutral, standardized prompts to guide documentation. - Preferred terminology built into workflows
Encourages use of “close call” and system-focused language. - Contributing factor classification
Shifts focus from individuals to systems. - CQI meeting integration
Supports consistent discussion using appropriate terminology. - Trend analysis and dashboards
Helps identify patterns without assigning blame. - Role-based access
Enables team participation while maintaining professional oversight. - Province-aligned flexibility
Supports CQI+, CIRCL, AIMS, and other provincial CQI frameworks.
PhIX helps pharmacies document incidents in a way that supports learning, compliance, and safety culture.
Key Takeaway
In pharmacy CQI, words matter.
Avoiding blame-laden, ambiguous, or legal terminology helps ensure that practice incident documentation remains focused on learning and system improvement. Clear, neutral language supports reporting, strengthens safety culture, and helps pharmacies meet CQI expectations across Canada.
Choosing the right words is one of the simplest and most powerful ways to improve patient safety.
