In any surgical facility, things will occasionally go wrong — a clerical error, a delayed result, an infection-control breach, an adverse event. CPSA accreditation doesn't expect perfection. What it expects is a system that catches problems, investigates them, and stops them from happening again — and the evidence that the system works.
This is one of the most revealing parts of a Quality Management System, because it shows whether your facility treats a problem as data to learn from or a thing to bury.
Complaints: the easy one to underestimate
The standard asks for a process to investigate and resolve complaints and feedback from any stakeholder — patients, clinicians, staff — in a timely way, with evidence of investigation and corrective action. A logged complaint with no recorded follow-through is a finding waiting to happen.
Non-conformances and adverse events
The standard wants timely identification, documentation, classification, and control of non-conformances and adverse events. In practice that means:
- A way to capture events from every source they surface — clinician complaints, quality indicators, equipment performance, audits.
- Incident documentation that captures the essentials where applicable: who was involved, witnesses, the procedure, the date and time, what happened and what was done, an analysis of why, and the outcome.
- Clear handling steps — immediate corrective action, notifying the requesting clinician where appropriate, halting services or withholding reports if needed, and a defined authority for resuming service.
- Reporting outward when required — adverse events tied to a device or consumable get reported to the manufacturer and the appropriate authorities.
- A disclosure policy for adverse events that complies with applicable legislation.
- Handling of CPSA Reportable Incidents under the College's specific reporting requirements.
CAPA: where most facilities fall short
This is the heart of it. The standard requires corrective action that includes an investigation into the underlying cause — and, where appropriate, leads to preventive action. Then the changes you make have to be implemented, documented, and monitored to confirm they actually worked.
It helps to keep three ideas distinct:
- Correction — you fix the immediate problem (re-do the count, recall the report).
- Corrective action — you find the root cause and change the process so this specific problem can't recur.
- Preventive action — you look for the same weakness elsewhere and close it before it bites.
The common failures are predictable: incidents get logged but never investigated; "corrective action" is really just a correction; and no one circles back to verify the fix held or to look for trends across events.
What good looks like
- Every event has an owner and a due date, and nothing closes without a root-cause step.
- Corrective actions are verified for effectiveness, not just marked done.
- Events are trended so management can see patterns and act before a one-off becomes a pattern.
- The loop connects back to your documents and training — a real fix usually changes a procedure.
How Zosimos helps
We help facilities design an incident and CAPA process that closes the loop — capture, classify, investigate, act, verify, and trend — mapped to the CPSA reportable-incident requirements so nothing slips. And when spreadsheets and email can't keep up, our Compliance Tracker (launching soon) is built to track corrective and preventive actions, reminders, and follow-through to closure — with the alerts and documentation trail the standard expects — so nothing gets logged and quietly forgotten.
See our CPSA NHSF accreditation support, or get in touch. Next: how to measure quality with indicators and audits.