NAHQ CPHQ Course Notes

CPHQ leadership questions are strategic and consultative. Start with the organization's goals, confirm the quality/safety gap with data, engage the people affected, then recommend priorities and resources that are feasible and measurable. Governing bodies retain oversight and accountability; the quality professional supports governance through analysis, facilitation, reporting, education, and improvement expertise. Strong quality culture depends on leadership behavior, open communication, interprofessional teamwork, and a learning-oriented approach to safety.

• Choosing a solution before validating the problem with data.

• If two answers are reasonable, prefer the one tied to strategy, data, stakeholders, and measurable impact.

Performance improvement is about selecting the right problem, team, method, tool, measure, and change strategy. Define the aim and scope before acting. Use Lean for waste and flow, PDSA for rapid iterative testing, and Six Sigma when defects or variation require a data-heavy approach. Use process maps to understand workflow, fishbone diagrams to organize possible causes, and FMEA to identify potential failures before harm occurs. Monitor milestones, team performance, outcomes, and sustainment—not just whether a project was completed.

• Using Six Sigma for every problem.

• Ask what kind of problem exists before choosing a method or tool.

Population health shifts the focus from one patient to a defined group. Combine clinical, cost, equity, and social-determinants data to identify needs and target interventions. Prevention, wellness, and disease management should match the population's risk. Health equity means addressing avoidable barriers and differing needs, not simply giving everyone the same intervention. Care-transition questions focus on coordination, communication, medication/information transfer, follow-up, social barriers, and avoidable utilization.

• Treating population health as individual case management only.

• Start by defining who the population is and what outcome is poor.

Health data analytics questions test whether you can define, collect, validate, display, compare, and interpret data for decisions. Begin with an operational definition and a sound data-collection plan. Match the measure type, denominator, sampling method, statistic, visualization, and benchmark to the question being asked. Structure measures describe capacity, process measures describe what is done, outcome measures describe results, and experience measures describe the patient's perspective. Use run/control charts for time-ordered performance; control charts distinguish common-cause from special-cause variation.

• Comparing rates with different definitions or denominators.

• For any metric, ask: what exactly is the numerator and who belongs in the denominator?

Patient safety questions favor systems thinking, proactive risk reduction, learning, and just culture over individual blame. Technology can improve safety only when it fits the workflow and is monitored for unintended consequences. Incident reporting captures events and near misses; event review and RCA are retrospective and seek underlying system contributors; FMEA/proactive risk assessment looks forward to possible failures before harm occurs. Human factors asks how system design interacts with real human capability.

• Blaming the person closest to the event before analyzing system contributors.

• After an event: report/contain as needed, collect facts, analyze system contributors, then act and measure.

Quality review and accountability connects standards, clinical performance, documentation, patient experience, reporting, confidentiality, and reimbursement. Evaluate performance against the correct requirement and use valid data before concluding that a gap exists. Guidelines support evidence-based decision making; pathways organize expected care; outcomes show results. Quality-based payment links defined measures and reporting to financial consequences. Protect performance and quality records according to applicable organizational policy and legal/regulatory requirements, and disclose only to authorized users.

• Assuming the presence of a policy proves compliance.

• Identify the governing standard before choosing a compliance action.

Regulatory and accreditation questions test whether you can identify the applicable requirement, monitor compliance, correct gaps, and maintain readiness continuously. Statutes and regulations are legal requirements; accreditation standards come from accrediting organizations and are not the same thing as law. Accreditation generally evaluates an organization or program against a broad set of standards, while certification is typically narrower and focused on a defined service, program, or capability. Survey readiness is an everyday state supported by evidence, staff awareness, monitoring, corrective action, and sustainment—not a last-minute inspection project.

• Calling accreditation standards laws or regulations.

• First identify who sets the requirement and whether it is legally mandatory, accreditation-based, or internal.