Morbidity and Mortality (M&M) Conference: Structure and Peer Review Protection

A morbidity and mortality (M&M) conference is a recurring, structured clinical meeting — typically organized by department or service — where a care team reviews deaths, complications, and unanticipated outcomes to identify systems and practice improvements. With roots in early-20th-century surgical practice, M&M conferences are now a standard fixture across nearly all clinical specialties, not just surgery.

Page checked against current source material in August 2026. The legal-protection section below is deliberately general: peer-review privilege is a matter of state law, its scope varies substantially by state, and it interacts with a separate federal privilege (covered on our Patient Safety Organization page) in ways that depend on how a specific institution has structured its process. Confirm the applicable rule with institutional legal counsel before relying on it.

What an M&M Conference Is For

The core premise of a well-run M&M conference is systems-based learning rather than individual blame: the goal is to identify what about the process — communication, handoffs, equipment, staffing, protocol design — allowed an adverse outcome to occur, not to single out the clinician who was present when it happened. This distinguishes M&M from a disciplinary or credentialing action, even though both may sometimes be informed by the same underlying case.

How a Well-Structured M&M Conference Works

Practices vary by institution and specialty, but a functioning M&M process typically includes:

• Defined case-selection criteria. Most departments review all deaths and a defined set of complications or unanticipated outcomes, rather than leaving selection to informal judgment. Some cases discussed at M&M separately meet the criteria for a sentinel event review — the two processes can be coordinated, but M&M discussion does not substitute for a required comprehensive systematic analysis when one is triggered.
• A consistent presentation format. A structured case summary — history, decision points, outcome, and a systems-focused discussion of contributing factors — keeps the conversation oriented toward process improvement rather than narrative or anecdote.
• Multidisciplinary attendance where the case involved more than one service, so contributing factors outside the presenting department’s control are actually visible in the discussion.
• Documented action items with an owner and a follow-up mechanism. A frequently cited weakness of M&M programs is that recommendations are made and never tracked to completion — closing that loop, ideally through the same quality/patient-safety infrastructure that tracks other corrective actions, is what turns M&M from a discussion into an improvement program.
• Careful separation of documentation types. Minutes, case summaries, and analysis material generated for the conference should be handled consistently with however the institution intends to claim legal protection for them (see below) — informally mixing protected and unprotected material is a common, avoidable exposure.

The Peer Review Protection Question

Most U.S. states have a peer-review privilege statute that protects the proceedings and records of a properly constituted peer-review committee from discovery in civil litigation, on the policy theory that clinicians will speak candidly about errors only if that candor cannot later be used against them or the institution. That is the general shape of the protection — the specifics are genuinely state-dependent, and getting this wrong is exactly the kind of overconfident claim that causes real harm:

• Scope varies significantly by state. What counts as a “properly constituted” peer-review committee, what categories of records and communications the privilege reaches, and what exceptions apply (for example, in some states, cases involving alleged gross negligence, or where the statutory formation and documentation requirements were not followed) differ from state to state. A protection that applies cleanly in one state may be narrower, or subject to more exceptions, in another.
• The privilege generally protects the committee’s own work product, not the underlying facts. In most states, the underlying medical record and information that exists independently of the peer-review process (for example, a fact a witness would testify to regardless of the M&M discussion) typically remains discoverable even where the committee’s deliberations and internal analysis are protected. Simply discussing a fact at M&M does not retroactively immunize it.
• The label “M&M conference” does not, by itself, create the protection. Courts generally look at whether the committee was properly constituted and documented under the specific state statute — its charter, its formal designation as a peer-review body under medical staff bylaws, and its actual conduct — not simply at what the meeting was called.

A separate, federal layer of protection is available if M&M-related material is deliberately created within a documented patient safety evaluation system for reporting to a listed Patient Safety Organization under PSQIA. That federal privilege is real but bounded in its own right, and — like state peer-review privilege — depends on how the specific material was created and documented, not on the name of the meeting where it was discussed. The two protections are not automatically overlapping, and an institution should not assume that state peer-review protection and federal PSQIA privilege cover exactly the same material.

Practical Guidance for a Patient Safety or Quality Office

• Confirm the M&M conference is formally constituted as a peer-review committee under your medical staff bylaws and applicable state statute — informal departmental case discussions do not automatically qualify.
• Keep peer-review-protected M&M material (minutes, internal analysis) documented and stored consistently with your institution’s legal guidance on what qualifies for the privilege in your state, separate from routine operational notes.
• Track action items centrally through your patient-safety/quality program rather than leaving follow-through to individual departments, so recommendations that come out of M&M are actually implemented and their effectiveness measured.
• Coordinate, but do not conflate, M&M review with sentinel-event RCA and PSO-reporting processes when a case triggers more than one — each has its own requirements and, where applicable, its own legal protection.

Frequently Asked Questions

Is what’s said at an M&M conference automatically protected from a lawsuit?

Not automatically. Protection generally depends on the M&M conference being properly constituted as a peer-review committee under your state’s specific statute, and on how the material was created and documented — not simply on holding a meeting under that name. State law varies substantially; confirm your institution’s specific protection with legal counsel.

Can M&M minutes be subpoenaed?

It depends on the state and on whether the committee and its documentation meet that state’s statutory requirements for peer-review protection, and on any exceptions that state’s law recognizes. This is not a uniform national answer.

Is an M&M conference required for hospital accreditation?

Accreditation standards generally expect ongoing peer review and case-based quality improvement activity, but the specific format, frequency, and name of that activity (M&M conference versus another structured peer-review mechanism) is set by institutional policy and medical staff bylaws rather than by a single named accreditation requirement.

Who should attend?

Attendance norms vary by specialty and institution, but a functioning M&M program typically includes the clinical team involved in the case, relevant department leadership, and — for cases that cross service lines — representation from every service involved, so systems factors outside a single department’s control are actually surfaced.

See the Patient Safety & Infection Prevention hub, and related coverage of sentinel events and Patient Safety Organization reporting and privilege.