FQHC Root Cause Analysis Guide: From Problem to Corrective Action

Why hospital RCA guides miss FQHC problems

Most published RCA guidance was written for hospitals and built around rare sentinel events: a wrong-site procedure, an inpatient fall. Health center quality teams deal with something different. Their hardest problems are slow and chronic: referrals that never close, abnormal results nobody acts on, screening rates that stay flat for years, and workflows that break every time a provider or medical assistant leaves.

Those problems rarely have a single dramatic cause. They come from handoffs, EHR configuration, staffing gaps, and measurement definitions working against each other. An RCA built for ambulatory care has to look at all of them at once.

When to run an RCA, and when to skip straight to PDSA

Not every gap needs a formal RCA. If the cause is obvious and the fix is cheap to test, run a PDSA cycle. An RCA earns its time when the same problem keeps coming back, when a previous fix didn't hold, or when an event caused or nearly caused patient harm.

• A measure has been flat or declining for several reporting periods despite effort
• A safety event or near miss occurred (a missed abnormal result, a lost referral)
• A previous PDSA was adopted but performance slid back
• Staff disagree about why something is failing

Step 1: Define a specific, measurable problem

Write the problem as a gap, not a complaint. "Our lab follow-up is bad" can't be analyzed. "38% of abnormal A1c results from Q2 had no documented follow-up within 14 days" can.

• Name the measure or process and the review period
• State the baseline with its data source
• Note what triggered the review (data trend, event report, audit)

Step 2: Assemble the right team

Include the people who actually do the work: front desk, MAs, nurses, referral coordinators, the provider, and whoever owns EHR reporting. A facilitator keeps the session on systems rather than people. Leadership should sponsor the RCA but not dominate the discussion.

Step 3: Map the process as it really runs

Walk the workflow step by step, as it happens on a busy Tuesday, not as the policy says it happens. Most root causes show up at handoffs: between the lab interface and the inbox, between the provider and the care coordinator, between one site and another.

Step 4: Find causes with a fishbone and 5 Whys

The MeasureWise worksheet uses six categories so nothing gets skipped:

• People: roles, staffing, training, communication
• Process: workflow, handoffs, standard work
• Technology: EHR, tools, equipment, alerts
• Environment: space, workload, timing, interruptions
• Policy: rules, procedures, governance
• Measurement: definitions, data capture, feedback

For each contributing cause, ask "why?" until the answer is something your team can change. Stop when you reach a system issue. If the chain ends in "the MA forgot," keep going: why was forgetting possible?

Step 5: Confirm root causes with data

A fishbone generates hypotheses, not conclusions. Before you commit resources, check the top candidates against a chart pull, an EHR report, or a few days of direct observation. Causes that explain most of the gap get action first.

Step 6: Turn causes into measurable corrective actions

Each confirmed root cause needs an action with an owner, a due date, and a measure that will show whether it worked. Prefer system-level fixes (a standing order, an EHR work queue, a redesigned handoff) over retraining and reminders, which tend to fade.

Each action then becomes a PDSA cycle: test it small, study the result, and decide to adopt, adapt, or abandon. That way the RCA leads to change you can prove instead of a report that sits in a binder.

Illustrative example: missed abnormal-lab follow-up

Keeping RCA records as QI documentation

A completed RCA worksheet, the data you used to confirm causes, and the PDSA cycles that followed are useful evidence of an active quality improvement program. Health centers should check the current HRSA Health Center Program Compliance Manual (Chapter 10, Quality Improvement/Assurance) for what their own QI/QA program must cover.

MeasureWise helps you organize this documentation. It does not certify compliance, and neither does any worksheet.