CPHQ Practice Questions

A process measure evaluates the steps or activities in the delivery of care. In this case, medication reconciliation is a process. Measuring the rate of discrepancies directly assesses whether that process is being performed correctly. An outcome measure would be the result of the process, such as adverse drug events after discharge. A structure measure would relate to the resources or setting, such as having a pharmacist available for discharge counseling. An experience measure would capture the patient's perception of the process.

At-risk behavior is a choice where the risk is not recognized or is mistakenly believed to be justified. It often involves taking shortcuts and can become normalized over time. Bypassing a required safety check due to pressure is a classic example. The individual isn't intending harm (distinguishing it from reckless behavior) but is making a risky choice. The fact that it has become common points to a system issue that needs coaching and management. The similar packaging scenario is human error. Intentionally skipping a known, critical safety step like a timeout is reckless behavior. Falsifying documentation is also reckless.

The 'Plan' phase is for preparation. This involves clearly defining the objective of the test, developing a plan for carrying it out (who, what, where, when), and, crucially, making predictions or hypotheses about what the team expects to happen. This prediction is vital for learning during the 'Study' phase. Data collection occurs in the 'Do' phase, analysis in the 'Study' phase, and large-scale implementation in the 'Act' phase.

This is true. Federal laws like the Health Care Quality Improvement Act (HCQIA) and various state statutes provide legal protection (privilege and confidentiality) for the work of designated peer review and quality improvement committees. This protection is intended to encourage candid and thorough review of care to improve quality, without fear that the discussions and documents will be used against the providers or organization in a lawsuit.

Human factors engineering focuses on designing systems and processes that make it easy for people to do the right thing and hard to do the wrong thing. Standardizing and simplifying processes, like using pre-packaged kits, is a core principle. This design choice reduces cognitive load, minimizes the chance of selecting the wrong item, and builds safety into the system itself. Relying on memory (posters) or punitive policies are weak interventions that do not address underlying system vulnerabilities.

A key data visualization principle is to choose the right chart for the data. Pie charts are best used to show parts of a whole, where the total sums to 100%. They are notoriously poor for comparing the magnitude of different categories, as the human eye struggles to accurately compare angles and areas. A horizontal or vertical bar chart would be a much more effective way to display and compare the counts of these different infection types.

Deference to expertise means that in a critical situation, authority shifts to the person with the most expertise on the specific issue, regardless of their rank. A secure messaging feature that bypasses the traditional hierarchy to raise concerns empowers frontline staff (who may have the most immediate knowledge of a patient's condition) to communicate directly with decision-makers. This flattens the communication structure and ensures the right information gets to the right people quickly, which is a core tenet of this HRO principle. Rigid access controls and standardized order sets do not promote this principle, and an audit trail is a reactive tool.

A u-chart is the most appropriate choice because it is used to monitor the rate of defects per unit when the subgroup size (the denominator) varies. In this scenario, the 'defect' is a CLABSI and the 'unit' is 1,000 central line days. Since the number of central line days changes each month, the subgroup size is not constant, making the u-chart the correct tool. A p-chart is for proportions of defective items, not rates of defects. A c-chart is for the count of defects when the area of opportunity is constant. An X-bar and R chart is for continuous variable data.

Failure Mode and Effects Analysis (FMEA) is a proactive risk assessment tool used to identify potential failures in a process before they occur. It involves mapping the process, identifying potential failure modes, determining their effects, and prioritizing them for action based on severity, occurrence, and detection. Root Cause Analysis (RCA) and Fishbone diagrams are reactive tools used after an event has occurred to find the cause. A Pareto chart is used to prioritize known problems based on frequency.