9.1 Managing the Disruptive Practitioner and Behavioral Programs

Managing the Disruptive Practitioner and Behavioral Programs

Domain 3 of the CPHRM content outline asks the risk manager to promote, in partnership with Patient Safety and Medical Staff departments, programs that address provider and staff behavioral issues that are culturally, legally and psychologically sound and non-discriminatory. That task statement contains the entire exam framing. The risk manager promotes and partners. The risk manager does not summon a surgeon into an office and suspend privileges. Answer choices that seat the risk manager in the disciplinarian's chair are wrong no matter how egregious the behavior described in the stem.

Disruptive Behavior Is a Patient Safety Hazard

The single most important conceptual move in this topic is to stop treating disruptive conduct as bad manners and start treating it as a latent system hazard. The Joint Commission's Sentinel Event Alert on behaviors that undermine a culture of safety (Alert 40, July 2008) tied intimidating and disruptive behavior to medication errors, communication breakdown, preventable adverse outcomes, poor patient satisfaction, higher cost of care, and the loss of qualified clinicians who leave rather than tolerate it.

The causal mechanism is simple and testable: colleagues stop speaking up. A nurse humiliated once for calling at 2 a.m. hesitates before calling the next time, and the hesitation, not the shouting, is what injures the patient. This is why the correct exam answer treats a pattern of belittling behavior as a safety concern requiring intervention rather than as an interpersonal dispute for the parties to resolve privately.

The Joint Commission converted that alert into Leadership standard LD.03.01.01, effective January 1, 2009. Two elements of performance drive risk management work:

• EP 4 — the organization has a code of conduct that defines acceptable behavior and defines disruptive and inappropriate behavior.
• EP 5 — leaders create and implement a process for managing disruptive and inappropriate behavior.

Notice what the standard requires: a written definition and a working process. An organization with a beautifully drafted code of conduct and no functioning intervention pathway fails the standard and, more importantly, fails the staff who report.

The Behavior Spectrum

Behavior is a continuum, and the intervention must match the point on the continuum:

• Incivility — eye-rolling, sarcasm, dismissive tone, sighing, excluding someone from a discussion. Low intensity, high frequency, cumulatively corrosive.
• Passive disruptive behavior — chronic lateness to procedures, not answering pages, refusing to complete records, silent refusal to follow an agreed protocol. Frequently under-reported because nothing dramatic happens.
• Overt disruptive behavior — yelling, profanity, name-calling, throwing instruments, public humiliation of a subordinate.
• Bullying — repeated, targeted conduct across a power differential.
• Harassment or discrimination based on a protected characteristic — a distinct legal exposure that routes through Human Resources and counsel in parallel with the medical staff process, not through the medical staff process alone.
• Threats or physical violence — an immediate security response under the workplace violence plan. The behavioral program never slows that down.

The Graduated, Documented Intervention Model

The dominant framework, developed at Vanderbilt by Hickson and colleagues and widely adopted as the promoting professionalism pyramid, is a tiered escalation in which nearly everyone is handled at the lowest tier and only a persistent few reach discipline. Each tier is triggered by data, not by whoever complained loudest or most recently.

Two structural requirements make the pyramid work, and both are the risk manager's contribution:

1. A central, coded repository of concerns. Complaints arrive from patients, families, nurses, residents, schedulers, and peers through event reports, grievances, rounding, and surveys. Unless they are coded to the individual and aggregated, nobody can see a pattern and every incident looks like a first offense.
2. Documentation at every tier. Even the informal conversation is logged — that it occurred, when, and by whom — without building a prosecutorial narrative. If the organization eventually restricts privileges, the defense of that action is the paper trail showing graduated, fair, consistent steps.

Three Tracks: Behavior, Competence, and Health

The most heavily tested discriminator in this topic is routing. The same reported episode can belong to any of three separate tracks, and choosing the wrong track is the wrong answer.

Behavior is evaluated separately from clinical competence, but the tracks are permeable in one direction: if review of a behavioral complaint surfaces a competence concern, that concern moves to the peer review track and is evaluated there on its own merits. Do not fold a competence question into a professionalism conversation, and do not let a competence review absorb a conduct problem.

The health track carries its own legal architecture. Joint Commission standard MS.11.01.01 requires the organized medical staff to implement a process to identify and manage matters of individual practitioner health that is separate from actions taken for disciplinary purposes. A suspected impairment is therefore referred, usually to a physician health or well-being committee and often in coordination with a state physician health program, for confidential evaluation, treatment, monitoring, and defined return-to-practice conditions. Americans with Disabilities Act (ADA) obligations attach: a practitioner in treatment or recovery may be a qualified individual with a disability entitled to an individualized assessment and consideration of reasonable accommodation. The organization may still act where the individual poses a direct threat to health or safety that accommodation cannot eliminate. The risk manager never diagnoses; the risk manager routes.

Consistency Is the Legal Defense

The blueprint's words non-discriminatory and culturally, legally and psychologically sound are not decoration. The program must be applied identically to the system's highest-admitting cardiologist and to the newest hospitalist. Selective enforcement — tolerating the rainmaker while disciplining a low-volume physician for the same conduct — is the fact pattern that converts a defensible corrective action into a lawsuit alleging breach of bylaws, discrimination, retaliation, or restraint of trade. Cultural soundness also means recognizing that norms of directness, eye contact, and hierarchy differ across cultures, so a code of conduct must describe observable behavior and its effect on care rather than personality, accent, or style.

Corrective Action, Fair Hearing, and HCQIA Immunity

When escalation reaches formal corrective action, the medical staff bylaws, not the employee handbook, control the process for members of the medical staff. Once an action becomes adverse and reportable — classically a restriction or suspension of clinical privileges lasting more than 30 days, or a resignation while under investigation — the bylaws' fair hearing plan is triggered: written notice of the action and the grounds, a stated period in which to request a hearing, a hearing before an impartial panel, the right to representation and to present and challenge evidence, a written decision with reasons, and an appeal to the governing body.

The Health Care Quality Improvement Act (HCQIA) of 1986 grants qualified immunity from damages for a professional review action taken:

1. in the reasonable belief that the action furthers quality health care;
2. after a reasonable effort to obtain the facts of the matter;
3. after adequate notice and hearing procedures, or such other procedures as are fair to the practitioner under the circumstances; and
4. in the reasonable belief that the action was warranted by the facts known after that effort.

The statute supplies a rebuttable presumption that these standards were met, which is exactly why sloppy process — acting on one unverified complaint, skipping notice, letting a competitor chair the panel — is how organizations lose immunity they would otherwise have had. A precautionary or summary suspension is available where failure to act may result in imminent danger to a patient, but it must be followed immediately by the required process, never substituted for it. Reportability to the National Practitioner Data Bank (NPDB) is what gives these procedural rights their consequence; the query and report mechanics are covered in the NPDB section of this guide.

Scenario

An operating room nurse files the fourth event report in eight months describing the same orthopedic surgeon berating circulating nurses during room turnover. Two informal conversations have already occurred. The surgeon is the highest-volume orthopedist in the system, and the service line director asks the risk manager to let it go until after the joint replacement service contract is signed.

The risk manager's correct action is to advise that the code-of-conduct process proceed exactly as it would for any other practitioner, deliver the aggregated professionalism data to the medical staff leader who owns the next tier, document the referral and the request to defer, and escalate that request through the appropriate leadership and compliance channel. The revenue argument is precisely the fact a plaintiff or a later claimant would use to prove the program was discriminatory and unenforced.

Exam Traps

• Trap: the risk manager disciplines. Corrective action belongs to the medical staff and the governing body under the bylaws. The risk manager convenes, documents, advises, and escalates.
• Trap: skipping tiers. Jumping from a single incident to summary suspension is defensible only for imminent danger, not for rudeness.
• Trap: treating impairment as misconduct. Suspected impairment routes to a health process separate from discipline, with ADA obligations attached.
• Trap: zero-tolerance language. A code of conduct promising immediate termination for any single incident is unenforceable and will be contradicted by the organization's own graduated practice.
• Trap: reporting behavior itself to the NPDB. The NPDB captures reportable professional review actions affecting privileges, not complaints or coaching conversations.
• Trap: no documentation of the low tiers. Without a record of the informal and awareness steps, a later privilege restriction looks arbitrary and loses the presumption of fair process.