| Course | NURS 8211 Data Collection and Analysis for Evidence-Based Practice |
|---|---|
| Week | Week 5 |
| Paper type | Chart abstraction tool |
| Length | About 1,040 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Nursing Practice (DNP) |
| Updated | September 2026 |
Free sample paper for NURS 8211 Week 5
One Page, Between Admissions: A Chart Abstraction Tool and Protocol for Auditing Teach-Back Documentation on a Heart Failure Unit
Student Name
College of Nursing, Walden University
NURS 8211: Data Collection and Analysis for Evidence-Based Practice
Instructor Name
Month Day, Year
One Page, Between Admissions: A Chart Abstraction Tool and Protocol for Auditing Teach-Back Documentation on a Heart Failure Unit
Purpose and Design Constraints
The teach-back project on the composite heart failure unit needs a monthly audit of discharge charts to confirm what the navigator report shows and to capture information the report cannot, such as whether re-teaching was documented. Charge nurses will do the abstraction between admissions and other duties, which means the tool must be quick, unambiguous and tolerant of interruption. A tool that is precise but takes twenty minutes a chart will not be completed.
Retrospective chart review is often criticized for weak methods, including undefined variables, untrained abstractors and no check on agreement between reviewers (Gilbert et al., 1996). Guidance on chart review recommends a standardized form, explicit definitions and decision rules, abstractor training and a pilot to test the form before use (Vassar & Holzmann, 2013). This tool follows that guidance within the limits of a working unit. It has three parts: a one-page form, a protocol of decision rules and a record of the pilot that changed three of those rules.
Part 1: The Form
The form fits on one page and uses coded fields throughout, so that answers are marked, not written. Table 1 shows its fields.
Table 1
Teach-Back Chart Abstraction Form
| Field | Code options | Where to look |
|---|---|---|
| 1. Project code | Assigned from the monthly list | Audit list |
| 2. Eligible (discharged home, not hospice or facility) | 1 = yes; 0 = no, stop here | Discharge disposition |
| 3. Teach-back section opened | 1 = yes; 0 = no; 9 = cannot tell | Navigator audit trail |
| 4. Weight rule: patient response recorded | 1 = correct first time; 2 = correct after re-teaching; 3 = not correct at discharge; 0 = not recorded | Teach-back fields |
| 5. Fluid limit: patient response recorded | Same codes as field 4 | Teach-back fields |
| 6. When to call: patient response recorded | Same codes as field 4 | Teach-back fields |
| 7. Teaching given to | 1 = patient; 2 = caregiver; 3 = both; 0 = not recorded | Teach-back fields or note |
| 8. Interpreter used, if language other than English | 1 = yes; 0 = no; 8 = not applicable | Note or interpreter log |
| 9. Teach-back text copied from an earlier note | 1 = yes; 0 = no; 9 = cannot tell | Compare with admission note |
| 10. Minutes to abstract | Number | Abstractor's estimate |
Codes 9 (cannot tell) and 8 (not applicable) are kept separate from 0 (not recorded) so that missing documentation is not confused with a question that does not apply.
Part 2: Decision Rules
The protocol gives a rule for every case that abstractors found ambiguous in the pilot or that the project team expected. The main rules are:
Rule A. More than one discharge in the month. Abstract only the first eligible discharge for each patient in the month, so that frequent readmissions do not count twice.
Rule B. Response recorded in free text rather than the field. If the note states what the patient said about the rule, code it as if it were in the field. If the note says only that teaching was done, code 0.
Rule C. Caregiver answered instead of the patient. Code the response as given and mark field 7 as caregiver. Do not code the patient's own understanding as correct.
Rule D. Patient discharged against medical advice. Code field 2 as eligible if discharged home, and code fields 4 to 6 as documented; do not exclude these patients, since excluding them would hide a group at high risk.
Rule E. Interrupted abstraction. Write the field number reached on the form before leaving, and resume from that field. Do not start the chart again.
Rule F. Copied text. Mark field 9 as yes only if the teach-back wording matches an earlier note word for word, including the patient's quoted responses. Similar content in different words is not copied.
Part 3: The Pilot and the Three Rules It Tightened
The form was piloted on twelve charts from the month before relaunch. Two charge nurses abstracted the same charts independently, and their codes were compared field by field. Agreement was good on most fields but poor on three, and the disagreements traced to three rules that were too loose.
Field 4 to 6 codes. The first draft had only correct, not correct and not recorded. Abstractors disagreed on patients who answered wrongly and then correctly after re-teaching; one coded these correct and the other not correct. Code 2, correct after re-teaching, was added. This matters to the project, since re-teaching is part of teach-back, and a patient who needs it has still learned the rule.
Rule B. The first version said to code free-text responses as recorded. Abstractors disagreed on notes that said the patient verbalized understanding. The rule now requires the note to state what the patient said, since verbalized understanding describes the patient's agreement, not a teach-back.
Rule F. The first version asked abstractors to mark copied text if the note looked similar. Agreement was poor. The rule now requires word-for-word matching, which is slower but consistent.
After the changes, the two charge nurses abstracted six new charts and agreed on all fields. A formal agreement statistic such as kappa would be more informative with a larger sample (McHugh, 2012). The protocol therefore requires a second abstractor to code two charts each month, so that agreement can be tracked over time and the rules revisited if it drops.
Time and Feasibility
Field 10 records minutes per chart. In the pilot, the median time was about six minutes after abstractors had done three or four charts, which the unit council judged manageable for ten charts a month spread across four charge nurses. If abstraction time rises, the first field to drop would be field 9, which is the slowest and least central to the project's question.
Training
Each charge nurse will receive a thirty-minute session covering the form, the rules and two practice charts with answers. New abstractors will code two charts alongside an experienced abstractor before working alone. A laminated copy of the rules will be kept with the forms, since abstractors are likely to be interrupted and will need to look rules up quickly.
References
Gilbert, E. H., Lowenstein, S. R., Koziol-McLain, J., Barta, D. C., & Steiner, J. (1996). Chart reviews in emergency medicine research: Where are the methods? Annals of Emergency Medicine, 27(3), 305-308. https://doi.org/10.1016/S0196-0644(96)70264-0
McHugh, M. L. (2012). Interrater reliability: The kappa statistic. Biochemia Medica, 22(3), 276-282. https://doi.org/10.11613/BM.2012.031
Vassar, M., & Holzmann, M. (2013). The retrospective chart review: Important methodological considerations. Journal of Educational Evaluation for Health Professions, 10, Article 12. https://doi.org/10.3352/jeehp.2013.10.12
The Walden NURS 8211 Week 5 instructions
Instrument assignments in this course generally ask you to build a tool for collecting your project's data and to show that it can be used reliably. Expect a paper of several pages that includes the tool itself. Design for the people who will use it and the conditions they work in. Use coded fields, and separate missing information from questions that do not apply. Write decision rules for ambiguous cases. Pilot the tool with two abstractors, compare their answers and revise the rules that caused disagreement. Report time per record. Describe training and a plan for checking agreement over time, and say which field you would drop first if the tool proves too slow.
Inside the NURS 8211 Week 5 example
The opening section explains why tolerance of interruption shaped the design and cites Gilbert and colleagues and Vassar and Holzmann. Table 1 shows ten fields with codes and where to look, including response codes for correct first time, correct after re-teaching and not correct. The decision rules section gives rules A to F. The pilot section explains three changes: adding a re-teaching code, requiring the patient's words rather than verbalized understanding and requiring word-for-word matching for copied text. A second round of six charts showed full agreement, and a monthly double-coding plan follows, citing McHugh. Sections on time and training close the paper. The paper also names the field that would be dropped first if abstraction took too long.
Where the marks sit in the NURS 8211 Week 5 rubric
Abstraction tools are usually graded on clarity of fields, completeness of decision rules, evidence of piloting, attention to reliability and feasibility for the intended users. Field clarity rewards coded options and separate codes for missing and not applicable. Decision rules earn credit when they address real ambiguities. Pilot evidence is highly valued, especially when it led to specific changes. Reliability credit rewards a plan to compare abstractors over time. Feasibility is judged on time per chart and fit with the users' workload. Accurate APA citations and sound sources round out the score. Graders often reward tools that record what the pilot changed.
Common NURS 8211 Week 5 mistakes, and how to avoid them
Abstraction tools lose marks when fields invite free text that no two abstractors will code the same way. Another common loss is a single missing code that merges not documented with not applicable. Some tools include no decision rules, so every ambiguous chart is a judgment call. Others are never piloted. Use coded fields, separate kinds of missing data, write rules for ambiguous cases, pilot with two people and revise. The desk can draft a tool and protocol for your own project. Pull three real charts, with identifiers covered, and try your draft on them before submitting, since the first attempt usually reveals a missing rule.
Get a NURS 8211 Week 5 example written to your instructions
Send the Week 5 prompt and rubric plus your measures and their definitions. You receive a one-page form, a protocol with a data dictionary and decision rules for the ambiguous cases your setting is likely to produce, and a suggested pilot design. Your first sample is free, returned within 24-48 hours.
More NURS 8211 papers and DNP samples
- NURS 8211 Week 1: Practice Data Post
- NURS 8211 Week 2: Indicator Validity Post
- NURS 8211 Week 3: Question-to-Measure Map
- NURS 8211 Week 4: Data Extraction Plan
- NURS 8211 Week 6: Missing Data and Bias Post
- NURS 8211 Week 7: Level-Matched Data Displays
- NURS 8211 Week 8: SPC Analysis Writeup
- NURS 8211 Week 9: Small-Sample Limits Post
- NURS 8211 Week 10: Unit Council Data Briefing
- NURS 8211 Week 11: Final Data Report
- NURS 8250 Week 5: Concept Analysis Paper
- NURS 8210 Week 5: Socio-Technical Analysis Paper
- NURS 8301 Week 5: QI Framework Selection Paper
- NURS 8114 Week 5: Framework Selection Paper
NURS 8211 Week 5 questions, answered
How many charts should the pilot include?
Enough to surface disagreements, which is usually a small set rather than a statistically chosen sample. The example reports its pilot as a handful of charts coded independently by two people, and it counts success as finding and fixing ambiguous fields, not as reaching an agreement figure. If your rubric asks for an agreement figure, the sample identifies a suitable statistic and shows how it would be calculated.
Can the abstraction be done by staff nurses?
It can, and the example assumes charge nurses will do it between other work, which is why burden is part of the design. Short forms, clear rules and a sampled rather than complete audit make that realistic. Some organizations prefer a quality department abstractor. Your protocol should say who abstracts and how they are trained, since graders look for that detail.
Where can I find a free NURS 8211 Week 5 sample paper?
The complete tool, with its ten-field form, six decision rules and pilot record, is posted here free of charge. A tool for your own project can be requested.
What did the pilot change in the NURS 8211 Week 5 tool?
It added a code for correct after re-teaching, required notes to state what the patient said rather than that they verbalized understanding and required word-for-word matching before marking text as copied.
How long does each chart take in the NURS 8211 Week 5 example?
About six minutes once abstractors had done a few charts, which the unit council judged manageable for ten charts a month shared among four charge nurses.