NURS 8512 Week 9 DNP Project Drift Audit Example

Side by Side Against the Approved Problem: A Drift Audit of Six Project Documents for a Rural Alcohol Screening Project

Student Name

College of Nursing, Walden University

NURS 8512: DNP Project and Practicum I

Instructor Name

Month Day, Year

Side by Side Against the Approved Problem: A Drift Audit of Six Project Documents for a Rural Alcohol Screening Project

Why Audit for Drift

By the ninth week, six project documents exist, each drafted at a different moment: the milestone map, the purpose and aims, the evidence grid, the synthesis, the setting and stakeholder section and the evaluation plan. Small differences in wording accumulate across documents written weeks apart, and a reader of the assembled proposal will notice them before the author does. Discussions of DNP projects have observed that scope and focus can shift over the life of a project in ways no one explicitly decided (Dols et al., 2017). This audit compares every document phrase by phrase against the approved problem statement and records each point where a term, population or measure has shifted, with the correction made. Reporting guidance for improvement work also asks that aims, methods and measures be described consistently, so that readers can follow what was done (Ogrinc et al., 2016).

Method

The approved problem statement, reproduced in the Week 1 map, served as the reference. Its key terms were listed: adults; annual visits; screened; validated instrument; screen positive; brief intervention; offer of referral; documented. Each document was then read with the list beside it, and every appearance of each concept was recorded with its exact wording. A difference was classified as intentional refinement, when a later document deliberately narrowed or specified a term and said so, or as drift, when wording changed without a decision. Each drift was corrected in the document where it appeared, and each refinement was checked to confirm it had been carried back into earlier documents. The two discussion posts were read as well, since they record decisions such as the scope agreement, but they were not corrected, because they are records of what was said at the time.

Findings

Table 1 records every difference found.

Table 1

Drift Audit Log

Four drifts, four refinements and one risk of confusion were found; drifts were corrected, and refinements were carried back into earlier documents.

Patterns in the Drift

Three patterns stand out. First, most refinements came from the evaluation plan, the last document written, which had to define terms precisely enough to count them: the instrument, the age range, the positive thresholds and the referral criterion. The earlier documents had left those terms open, which was reasonable when they were written but meant that, until this audit, the aims and the evaluation plan described slightly different projects.

Second, drift crept in through near-synonyms. Tool for instrument looks harmless, but the problem statement's word signals a validated measure, and a reader could take tool to include a checklist the clinic invented. Third, the documents describing how the change would work, the synthesis and the setting section, introduced method terms such as warm handoff that could be mistaken for measures. None of these was an error of fact; each was a place where a reader could reasonably have counted something different from what the project intends.

The Most Consequential Drift

The drift with the largest consequence was the same-visit requirement. Aim 2 says brief intervention will be documented at the same visit as a positive screen; the evaluation plan's measure, as first written, counted brief intervention documented at any time. Had the difference gone unnoticed, the implementation course could have reported a higher brief intervention rate than the aim describes, by counting follow-up calls days later. The measure now matches the aim. The example shows why an audit reads measures, not just prose: the numbers the project reports are defined in the measure table, and a mismatch there changes what the project claims.

Preventing Further Drift

Two practices will limit drift in the assembled proposal and beyond. A one-page glossary of defined terms, taken from the evaluation plan, will sit at the front of the proposal, and every section will use those terms exactly. And the implementation course's reports will quote the aims and measure definitions from the glossary rather than restating them. The glossary becomes the reference for later documents in the way the problem statement was for this term, and a short audit against it will be repeated before the final report.

The audit also changed how the remaining documents are written. The proposal assembly in week 10 will begin by pasting the glossary and the aims into a working copy and writing each section with them open. Each section will then be checked against the glossary before it is added. This takes perhaps twenty minutes per section, far less than finding and fixing the same differences in a twenty-five page document after assembly. The fidelity checklist in the evaluation plan offers a parallel: just as the project will check that a brief intervention contains its four elements, the author will check that each section uses the defined terms (Carroll et al., 2007).

References

Carroll, C., Patterson, M., Wood, S., Booth, A., Rick, J., & Balain, S. (2007). A conceptual framework for implementation fidelity. Implementation Science, 2, Article 40. https://doi.org/10.1186/1748-5908-2-40

Dols, J. D., Hernández, C., & Miles, H. (2017). The DNP project: Quandaries for nursing scholars. Nursing Outlook, 65(1), 84-93. https://doi.org/10.1016/j.outlook.2016.07.009

Ogrinc, G., Davies, L., Goodman, D., Batalden, P., Davidoff, F., & Stevens, D. (2016). SQUIRE 2.0 (Standards for QUality Improvement Reporting Excellence): Revised publication guidelines from a detailed consensus process. BMJ Quality & Safety, 25(12), 986-992. https://doi.org/10.1136/bmjqs-2015-004411