| Course | HIM 675 Research Methods and Evaluation |
|---|---|
| Module | Module 6 |
| Paper type | graduate short paper on designing and testing a data abstraction instrument |
| Length | About 1,020 words, 6 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | MS Health Information Management |
| Updated | October 2026 |
Free sample paper for HIM 675 Module 6
Same Chart, Same Answer? Designing and Testing the Abstraction Tool Used in the Tulsa Flag Study
[Student Name]
Southern New Hampshire University
HIM 675: Research Methods and Evaluation
Module Six Short Paper
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Same Chart, Same Answer? Designing and Testing the Abstraction Tool Used in the Tulsa Flag Study
A study of whether present-on-admission flags are accurate depends on a gold standard that is itself trustworthy. At Cimarron Heights Medical Center, the composite Tulsa teaching hospital where the study will take place, the gold standard is a blind re-abstraction of each record by a credentialed coder. If two abstractors reading the same chart reach different conclusions, the study's results will reflect abstractor disagreement as much as coding error. This paper describes the abstraction tool, how its content was checked and how its reliability was tested in two pilot rounds before data collection begins.
The Abstraction Tool
The tool is an electronic form with four sections. The first records identifiers: a study number in place of the medical record number, the condition under review and the admission source. The second records the evidence at admission, including whether a structured skin and risk assessment was documented, its date and time, any skin finding, the Braden score and any documentation of the condition in the emergency department, transfer records or physician history within 24 hours. The third records the abstractor's flag, using the same five values as the claim, with a free-text field explaining the evidence relied on. The fourth records process variables: whether the coder queried a clinician and the query's outcome.
Each condition has written decision rules. For pressure injuries, a flag of yes requires documentation of a wound at the same site and of the same or lower stage within 24 hours of admission, using the stage definitions in the revised national staging system (Edsberg et al., 2016). A deep tissue injury first documented on day two or three is treated as clinically undetermined unless a physician states it was present on arrival. For catheter infections, yes requires that the catheter and the infection both preceded admission. For blood clots and fall injuries, the rules rely on imaging dates and incident reports. Abstractors are blinded to the coded flag, following the approach of Goldman et al. (2011).
Content Validity
A tool is valid if it measures what it claims to measure. Before testing reliability, three experts reviewed every field and rule: a certified wound care nurse, the hospital's coding quality lead and a clinical documentation specialist. They rated each rule as essential, useful or unnecessary and suggested changes. Two changes resulted. The wound nurse added the rule about deep tissue injuries, because those injuries often appear after admission even though the damage began before it, and the coding lead asked for a field recording scanned outside records, which coders sometimes miss. The tool also maps to the data quality dimensions described by Weiskopf and Weng (2013), particularly completeness of admission documentation and concordance between the claim and the clinical record, which supports its fit with the study's framework.
Pilot Round One
Two credentialed coders, neither of whom coded the original records, independently abstracted 30 records chosen to include all four conditions. Table 1 shows their flags for the 30 records.
Table 1. Pilot Round One Agreement Between Abstractors (n = 30)
| Abstractor B: yes | Abstractor B: no | Total | |
|---|---|---|---|
| Abstractor A: yes | 12 | 2 | 14 |
| Abstractor A: no | 1 | 15 | 16 |
| Total | 13 | 17 | 30 |
Note. Records with insufficient documentation or clinically undetermined values were analyzed separately; none occurred in round one.
Why Kappa, Not Agreement
The abstractors agreed on 27 of 30 records, or 90%, which sounds excellent. But some agreement would happen by chance. Cohen's kappa adjusts for that. Here, chance agreement is about 50%, calculated from how often each abstractor said yes and no, and kappa equals 0.90 minus 0.50, divided by 1 minus 0.50, or approximately 0.80. McHugh (2012) cautions that raw percent agreement overstates reliability and proposes interpreting kappa from 0.60 to 0.79 as moderate, 0.80 to 0.90 as strong and above 0.90 as almost perfect, noting that health research data often need at least strong agreement. A kappa at the boundary of moderate and strong was not good enough for a gold standard.
The three disagreements were examined together. Two involved deep tissue injuries documented on the second day, and one involved a transfer record scanned into the chart days after admission. All three traced to rules that were unclear, not to careless reading.
Revisions and Round Two
Three rules were rewritten. The deep tissue injury rule now states exactly which documentation counts as a physician statement. The scanned records rule now says that outside records count only if their content describes the patient's condition before arrival, regardless of when they were scanned. A third rule clarified how to treat a pressure injury documented at a different site from the coded one. The abstractors then reviewed 20 new records. They agreed on 19, and kappa rose to about 0.89, within the strong range. The study will proceed with this version of the tool, and a 10% sample of study records will be double-abstracted throughout data collection to confirm that reliability holds.
Training and Drift
Reliability can fade once a study is under way, a problem often called drift. The two abstractors spent two hours in training ahead of the pilot, working through ten practice records with the decision rules and discussing each answer, and they will repeat a short refresher with five new practice records after every hundred study records. Disagreements in the ongoing double-abstraction sample will be resolved by a third reviewer, the coding quality lead, and logged with the rule involved, so that any rule producing repeated disagreement can be clarified and the change dated in the study record. If kappa in any batch falls below 0.80, abstraction will pause until the cause is found. These steps cost a few hours but protect the credibility of every number the study reports. The full set of rules, with the date of each revision, will be attached to the proposal as an appendix so that the committee can judge them directly.
Conclusion
The abstraction tool now has written rules for every condition, expert review behind its content and strong agreement between abstractors after one round of revision. The pilot also taught a lesson about measurement: 90% agreement looked reassuring until chance agreement was removed. The same caution will apply when the study compares coded flags with the gold standard.
References
Edsberg, L. E., Black, J. M., Goldberg, M., McNichol, L., Moore, L., & Sieggreen, M. (2016). Revised National Pressure Ulcer Advisory Panel pressure injury staging system. Journal of Wound, Ostomy and Continence Nursing, 43(6), 585-597. https://doi.org/10.1097/WON.0000000000000281
Goldman, L. E., Chu, P. W., Osmond, D., & Bindman, A. (2011). The accuracy of present-on-admission reporting in administrative data. Health Services Research, 46(6pt1), 1946-1962. https://doi.org/10.1111/j.1475-6773.2011.01300.x
McHugh, M. L. (2012). Interrater reliability: The kappa statistic. Biochemia Medica, 22(3), 276-282. https://doi.org/10.11613/BM.2012.031
Weiskopf, N. G., & Weng, C. (2013). Methods and dimensions of electronic health record data quality assessment: Enabling reuse for clinical research. Journal of the American Medical Informatics Association, 20(1), 144-151. https://doi.org/10.1136/amiajnl-2011-000681
What the HIM 675 Module 6 instructions ask for
Module Six of HIM 675 brings a short paper on your study's data collection instrument, typically three to five pages in APA 7. Describe the instrument, whether an abstraction form, survey or interview guide, field by field or item by item, with the rules that tell a collector how to record each one. Explain how you checked validity, for example through expert review of content. Then describe how you tested reliability, such as a pilot in which two people collect data from the same sources, and report the result with an appropriate statistic. Interpret it against a published standard. If the pilot reveals problems, show how you traced and fixed them, and state how reliability will be monitored during the full study.
How this HIM 675 Module 6 instrument short paper example is built
Cimarron Heights Medical Center's abstraction form has four sections, identifiers, admission evidence, the abstractor's flag and query details, with written rules per condition, including pressure injury stages from Edsberg and colleagues and blinding modeled on Goldman and colleagues. A wound nurse, a coding lead and a documentation specialist review the content, adding a deep tissue injury rule and a scanned-records field, and the tool maps to Weiskopf and Weng's dimensions. Pilot one shows 27 of 30 agreements but kappa near 0.80, interpreted with McHugh's ranges. Three disagreements trace to unclear rules, which are rewritten, and pilot two on 20 records reaches about 0.89. The HIM 675 paper closes with ongoing 10% double abstraction.
Where the HIM 675 Module 6 rubric puts the points
Instrument papers in HIM 675 are usually graded on a clear, complete description of the tool, decision rules specific enough to apply consistently, a credible approach to validity, an appropriate reliability test with correct calculation and interpretation, analysis of disagreements and a plan to maintain reliability during data collection. Papers that do well explain why a chance-corrected statistic such as kappa matters more than raw agreement and cite a recognized interpretation scale. Graders value revisions grounded in specific pilot findings rather than general tinkering. Tables showing the underlying data, precise methodological vocabulary and correct APA 7 citations support the higher marks. Linking the instrument to the conceptual framework shows alignment across the proposal.
HIM 675 Module 6 help: the mistakes that cost points
Instrument papers in this course often lose marks by listing fields without rules, claiming validity without describing how it was checked, reporting percent agreement alone, miscalculating kappa or skipping what happened after a weak pilot. Some also forget to say how the collector is blinded. If your study uses a survey, an interview guide or a coding audit tool instead of a re-abstraction form, send the draft instrument and the prompt, and the paper will describe and test it in the way that fits, including other reliability measures such as Cronbach's alpha. Pilot numbers, even a small set, make the paper concrete. Our HIM 675 instrument papers show the rules, test reliability properly and revise from evidence.
Get HIM 675 Module 6 written to your instructions
Send the HIM 675 Module 6 prompt with your draft instrument and any pilot data. The paper will describe each field and rule, explain how validity was checked, calculate and interpret reliability correctly, trace any disagreements to their causes and plan monitoring during the study, delivered within 24 to 48 hours with the first one free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.
More HIM 675 papers and related MS Health Information Management samples
- HIM 675 Module 1 Discussion: From a Data Problem to a Research Question
- HIM 675 Module 2 Literature Review Short Paper: What Studies Say About Present-on-Admission Accuracy
- HIM 675 Module 3 Final Project Milestone One: The Problem, Purpose and Research Questions
- HIM 675 Module 4 Discussion: Choosing a Design That Fits the Question
- HIM 675 Module 5 Final Project Milestone Two: Literature Synthesis and a Conceptual Framework
- HIM 675 Module 7 Final Project Milestone Three: Design, Sample, Analysis and Ethics
- HIM 675 Module 8 Journal: Reading Strangers' Charts for Research
- HIM 675 Module 9 Final Project: The Research Proposal
- HIM 675 Module 10 Reflection: What Designing Research Taught the Writer
- HIM 560 Module 2 Interoperability Short Paper: Why Records Still Arrive by Fax
- HIM 510 Module 10 Reflection: Growth as a Revenue and Compliance Leader
- HIM 540 Module 9 Final Project: The Information Governance Program
- HIM 530 Module 4 Access Monitoring Short Paper: Insider Snooping and Audit Log Review
HIM 675 Module 6 questions, answered
Where can I find a free HIM 675 Module 6 Instrument Short Paper sample?
The whole HIM 675 Module 6 paper is on this page, describing a record abstraction tool and two pilot rounds of interrater reliability testing with kappa.
Why use kappa instead of percent agreement?
Percent agreement includes agreement that would happen by chance. Kappa removes chance agreement, so it gives a more honest picture of reliability.
What kappa value is acceptable for a research abstraction tool?
One published scale treats 0.80 to 0.90 as strong and above 0.90 as almost perfect, and health research data generally need at least strong agreement.
How do you establish content validity for an abstraction tool?
Ask experts in the clinical area and in coding to review every field and rule, rate their importance and suggest changes before testing reliability.
What should happen if a pilot shows weak reliability?
Examine each disagreement, revise the unclear rules that caused them, retest on new records and plan ongoing double abstraction during the study.