CPHQ (Healthcare Quality) II

What this covers

• Selecting and running an improvement methodology end to end: PDSA cycles, Lean waste identification, and Six Sigma DMAIC phases, including which one fits a given problem statement
• Building and interpreting quality tools — process maps and value stream maps, fishbone diagrams, Pareto analysis, driver diagrams, and prioritization matrices
• Reading run charts and Shewhart control charts: choosing p, u, XmR or c charts by data type, applying run rules, and distinguishing signal from noise
• Measure construction and data integrity: numerator/denominator specification, rate vs. ratio vs. proportion, risk adjustment, sampling, and benchmarking against internal, competitive, and national comparators
• Patient safety methods: retrospective root cause analysis with corrective action plans, prospective FMEA with RPN scoring, event reporting taxonomies, and just culture decision logic
• Accreditation and regulatory readiness: CMS Conditions of Participation, tracer methodology, mock survey preparation, and closing evidence-of-compliance gaps

Where learners get stuck

Treating every point that looks high or low on a control chart as a problem to fix

Everyday reporting culture trains people to react to month-over-month movement. Learners carry that habit into control charts and start investigating common cause variation, which wastes effort and often makes the process worse. The fix is drilling the specific run rules until 'is this a special cause?' becomes a test rather than a gut call.

Using RCA and FMEA interchangeably

Both produce a cause-and-effect diagram and an action list, so they feel like the same exercise. But RCA is retrospective and event-triggered while FMEA is prospective and process-triggered, and exam items usually hinge on that timing distinction plus the scoring step (RPN) that only FMEA has.

Comparing raw rates between units or hospitals without checking the denominator or case mix

Percentages feel self-normalizing, so learners assume a 4% rate is a 4% rate. Denominator definitions, exclusion criteria, and patient acuity differ enough that unadjusted comparisons routinely reverse once risk adjustment is applied — a common trap in both scenario questions and real committee meetings.

What a session looks like

A typical session runs 25–45 minutes of spoken back-and-forth. You bring a domain or a set of practice questions you got wrong; the tutor works one scenario at a time, asking you to state the measure, name the tool, or justify the chart type before confirming. Expect to be interrupted with 'what's your denominator?' or 'is that common or special cause?' Numeric work — RPN scores, control limits, sigma level, sample sizes — is done step by step aloud. Sessions usually close with a short recall check on the terms and thresholds that came up.

Helpful to know first

• The foundational CPHQ material: quality management structures, leadership and governance, strategic planning, and core terminology
• Comfort with percentages, averages, and simple ratios; standard deviation is introduced during the module rather than assumed
• Basic familiarity with how a hospital, clinic, or payer organization is structured (departments, committees, medical staff, licensure vs. accreditation)
• No coding or statistical software required — charts are described and interpreted verbally

Questions

How is this different from the first CPHQ topic?

The first module covers organizational leadership, quality program structure, strategy, and training/communication. This one covers the analytic and operational domains: improvement methodologies, data and measurement, patient safety, and accreditation/regulatory compliance. There is minimal overlap, though the leadership vocabulary from the first module is assumed.

Do I need work experience in healthcare to take this?

Not for the tutoring. Certifying bodies set their own eligibility requirements for sitting the exam, which you should check directly with them. Sessions use clinical and administrative scenarios, and the tutor will explain the setting when a scenario assumes workflow knowledge you may not have.

How much math is on this half of the material?

Enough to matter but not enough to require a statistics course. You need to compute and interpret rates, calculate an RPN, read control limits, understand sampling adequacy, and know when data are attribute vs. variable. Sessions practice these by talking through the arithmetic rather than by written problem sets.

How many sessions does this usually take?

It depends on how much of the material is new. Learners working through all four applied domains typically spread it over several weeks, treating each domain as a few sessions. You can also target a single weak area — control charts and measure definitions are the two most commonly requested.