Patient Safety Organizations: National Provider Network and Reference
Patient safety organizations (PSOs) form a federally structured network designed to collect and analyze data about medical errors, near-misses, and adverse events — information that hospitals and clinicians can share without the immediate fear that it will be used against them in litigation. This page catalogs the major national organizations operating in this space, explains how PSO protections work in practice, and maps out when a patient or provider should engage with one versus another type of body. The distinction between a PSO, a patient advocacy organization, and a regulatory body matters more than most people realize, and the differences have real consequences for how safety data flows — and who benefits from it.
Definition and scope
A Patient Safety Organization is a specific legal designation created under the Patient Safety and Quality Improvement Act of 2005 (PSQIA, 42 U.S.C. § 299b-21 et seq.). The Agency for Healthcare Research and Quality (AHRQ) maintains the official list of federally certified PSOs — as of the most recent AHRQ publication, more than 90 organizations held active PSO certification (AHRQ PSO Registry).
The defining feature is legal privilege. When providers submit reports to a verified PSO, that information becomes "patient safety work product" — protected from discovery in civil litigation, disciplinary proceedings, and Freedom of Information Act requests. This privilege is the engine that makes honest error reporting possible. Without it, self-reporting a near-miss is roughly equivalent to writing a confession letter to a plaintiff's attorney.
PSOs are distinct from:
- State health departments, which regulate licensure and have mandatory reporting authority
- The Joint Commission, an accreditation body that inspects facilities but is not a federal PSO
- Patient advocacy organizations, which work on behalf of individual patients navigating care systems (see Key Dimensions and Scopes of Patient Advocacy)
- CMS (Centers for Medicare & Medicaid Services), which administers payment programs and conditions of participation
The scope of PSO activity is national but voluntary on the provider side — no federal law requires a hospital to join a PSO, though several state laws and accreditation standards create indirect pressure to do so.
How it works
Providers who partner with a PSO submit event reports into a Common Formats system — a standardized data structure developed by AHRQ (AHRQ Common Formats) — that allows aggregation across institutions. The PSO analyzes patterns, identifies systemic risks, and shares de-identified findings back with the provider community.
The data flow has three stages:
- Collection — A clinician or risk manager files an internal report of an adverse event or near-miss. That report, once submitted to the PSO, becomes protected work product.
- Analysis — The PSO aggregates data across its member organizations, looking for failure patterns that no single hospital would see in isolation — a particular device model failing under specific conditions, for instance, or a medication dosing error concentrated in one shift structure.
- Feedback — Findings return to providers as safety bulletins, best-practice alerts, or formal recommendations. The PSO also contributes de-identified data to the Network of Patient Safety Databases (NPSD), which AHRQ uses for national-level analysis.
For patients trying to understand how their safety is being protected — or what recourse exists after a harm event — the How It Works section of this site covers the broader patient advocacy ecosystem, including how PSO activity intersects with individual cases.
Common scenarios
Scenario A: Medication error at a member hospital. A nurse administers the wrong dose of an anticoagulant. The patient is not harmed, but the near-miss is documented. Because the hospital partners with a certified PSO, that report is legally shielded. The PSO identifies that three other member facilities reported similar near-misses involving the same electronic health record interface. A system-level alert goes out. One unremarkable night shift event becomes a network-wide safety intervention.
Scenario B: Surgical site infection cluster. A regional hospital network notices a spike in post-operative infections across two facilities. By submitting structured data to their PSO, they can benchmark against de-identified data from 40 other institutions to determine whether their rate is an outlier or consistent with national patterns. The answer changes everything about whether this is a local process failure or a broader equipment issue.
Scenario C: A patient's family after a harm event. A patient dies following a preventable diagnostic delay. The family wants answers. This is where PSO structure creates friction for patients — because PSO data is privileged, it cannot be subpoenaed. Families in this situation often need to engage a patient advocacy resource or consult legal counsel rather than expecting PSO reports to surface in discovery.
Decision boundaries
The central tension in PSO policy is that the same privilege protecting candid error reporting also shields information from patients who were harmed. Understanding which organizations to engage — and for what purpose — requires mapping the landscape clearly.
| Organization type | Primary user | Data access | Legal privilege |
|---|---|---|---|
| Federally verified PSO | Providers / health systems | Aggregated, de-identified | Yes — PSQIA protected |
| State health department | Regulators / public | Mandatory reports, inspections | No |
| The Joint Commission | Accreditation reviewers | Sentinel event data | Partial |
| Patient advocacy org | Individual patients | Case-specific navigation | N/A |
Patients seeking accountability after a harm event should not assume PSO channels will surface useful information — those channels are intentionally insulated from adversarial proceedings. The patient advocacy frequently asked questions page addresses what families can realistically expect from each type of body.
For providers, the decision to join a PSO turns on data volume, specialty focus, and whether a given PSO's analytical feedback loop covers the clinical domains most relevant to their patient population. A large academic medical center may benefit from a PSO that specializes in surgical events; a rural critical-access hospital may prioritize one with strong medication safety infrastructure. AHRQ's verified PSO registry allows filtering by specialty and provides contact information for each certified organization directly at pso.ahrq.gov.