A Nursing Home QAPI Project: From Charter to Recheck and Decision

Give the project a decision it can actually answer

CMS’s project-charter worksheet provides an optional structure for scope, goals, timing, roles and resources. It explicitly does not guarantee compliance. For federally certified nursing facilities, 42 CFR 483.75(d) distinguishes implementing actions from measuring success and tracking sustained improvement.

The fictional project below tests a nonurgent documentation handoff. It is an original worked example, not a proposed clinical protocol or a claim of achieved facility outcomes.

The completed charter

A target should be justified by the facility’s actual baseline and priorities. The example uses no invented universal benchmark. The qualified team determines clinical safeguards and any timing needed for real work.

What the pilot found

For each fictional phase, take the first 20 consecutive eligible, distinct nonurgent requests opened at the evening handoff on the same unit. Check ownership at the end of that handoff, reconcile to the underlying request sources, and count duplicate task records separately from the 20 requests. Observe total staff entry time for the same set. These are local example definitions, not clinical timing standards.

The initial sample has fewer ownership gaps, 2/20 rather than 6/20, but more duplicates. Entry time rises by 30 minutes for the 20-request sample, from 2 to 3.5 minutes per request. Staff report entering the same information in both a handoff form and a new task screen. That burden is time spent, not a cash cost estimate or proof of its cause. The team’s decision is to revise the duplicate-entry step and continue a limited test, rather than claim the initial design is ready for every unit.

The later sample shows 3/20 ownership gaps and one duplicate; entry time is 45/20, or 2.25 minutes per request. That is useful learning. Three small selected samples do not prove causation, statistical significance, durable performance or resident benefit. Preserve the selection method and differences in workflow or capture before comparing results.

A decision journal carries more meaning than a green task

The journal records: “Shared acceptance introduced as planned. Initial ownership gap count decreased, but duplicate entry burden increased. Remove redundant creation route, retain source attribution, then recheck the same defined question.”

That entry connects the action to its evidence and reason for revision. A project dashboard saying “training completed” records implementation, but it cannot substitute for the findings above.

Keep source records or authorized references, extraction dates and calculation definitions. If the second sample excludes requests that never reached the shared board, apparent improvement may be a capture failure. Reconcile the board to the underlying request population before concluding that assignment improved.

Link incidents and actions without duplicating them

A reviewed process action may address three separate incidents. Keep the three incident identities and one action identity, with the rationale for their relationship. One incident may also require several actions.

Do not create three copies of the action merely to make each incident screen look complete. Do not mark all related incidents clinically resolved when the configuration task closes. The clinical, infection-prevention and reporting processes retain their own responsibilities.

If an incorrect link is removed, preserve the reason and historical context so an earlier report remains explainable. Data organization should support the actual review, not replace it.

Design the recheck when the action is assigned

Specify the review question, evidence source, population and decision authority alongside the implementation task. Choose the actual timing through the facility’s QAPI process. A recurring calendar reminder is a prompt, not evidence that a recheck occurred.

If a later result worsens, retain it and reopen analysis as appropriate. An unfavorable recheck is useful evidence about sustainability. Hiding it because the project previously closed defeats the purpose of following the change over time.

For regional rollouts, retain site-level observations. A corporate average may conceal that one facility never adopted the workflow or that local roles differ. Expand only under a documented decision that acknowledges those dependencies.

Make the project understandable after leadership changes

Give an incoming or backup leader the charter, three samples and decision journal. The person should be able to explain the original problem, changed workflow, burden finding, current uncertainty and next decision.

Technical access and decision responsibility are separate. The new leader needs the appropriate evidence access and a clear transfer of future responsibility, while prior decisions remain attributable to the people who made them. This supports the continuity addressed in 483.75(f)(2).

The finished artifact is a usable decision record. It can support a measured next step even when the honest answer is that the first attempt needs revision.