HIM 675 Module 9 Final Project Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 675 Module 9 Final Project sample is a complete research proposal, ready for a review board and for the capstone that will carry it out. It was prepared for SNHU HIM 675 (HIM-675), where the course ends with MS Health Information Management learners joining their milestones into one revised proposal. The composite study asks how accurately a 340-bed Tulsa teaching hospital flags four hospital-acquired conditions as present on admission and whether a missing admission assessment predicts errors. The proposal opens with an abstract, then condenses the problem and questions, the evidence and framework, an explanatory sequential design with 320 stratified records, a reliability-tested abstraction tool, an analysis plan matched to each question, a small interview phase, ethics and privacy protections, a timeline, a budget and a plan for sharing results.

CourseHIM 675 Research Methods and Evaluation
ModuleModule 9
Paper typegraduate research proposal on present-on-admission flag accuracy
LengthAbout 1,040 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMS Health Information Management
UpdatedOctober 2026

Free sample paper for HIM 675 Module 9

1

Final Project: Present on Arrival? A Research Proposal to Measure and Explain Errors in Admission Flags at a Tulsa Teaching Hospital

[Student Name]

Southern New Hampshire University

HIM 675: Research Methods and Evaluation

Final Project

[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.

What this page is doingThe title states the study's question and its two aims.
2

Final Project: Present on Arrival? A Research Proposal to Measure and Explain Errors in Admission Flags at a Tulsa Teaching Hospital

Abstract

Present-on-admission flags decide whether a condition on an inpatient claim counts as a hospital complication. At the composite Tulsa teaching hospital in this proposal, an audit found more than a third of coded pressure injuries flagged as present on admission without supporting documentation. This study will measure how often coded flags agree with blinded re-abstraction for four hospital-acquired conditions, whether errors lean toward over- or under-reporting and whether the absence of a structured admission assessment predicts disagreement. An explanatory sequential design pairs a review of 320 stratified records from fiscal 2026 with interviews of eight coders and nurses. Results will guide documentation templates, coding practice and the accuracy of the hospital's reported safety data.

What this page is doingAn abstract lets a reviewer grasp the study in one paragraph.
3

Problem and Questions

Nobody at the hospital can yet say how often these flags are right, which way they miss or which documentation habits travel with the misses. If flags are wrong, the hospital's safety rates, regulatory reports and some payments are wrong with them. The study asks three questions. What proportion of coded flags for pressure injuries, catheter-associated urinary infections, venous thromboembolism and fall injuries agree with re-abstraction? Among disagreements, do over-reports outnumber under-reports, as predicted for pressure injuries? And is the lack of a structured skin and risk assessment within 24 hours associated with greater odds of disagreement once condition, admission source, unit and coder experience are taken into account?

What this page is doingThe problem and questions are restated compactly.
4

Rationale From the Literature

Earlier research makes the case that the flag is consequential and fallible. In a statewide audit, coded flags matched the chart in about three of every four records, with errors in both directions and different patterns by hospital type (Goldman et al., 2011). Applying flags to one system's patient safety indicators lowered nearly every rate, sometimes sharply, showing how much the flag changes what a hospital appears to achieve (Bahl et al., 2008). In the vocabulary Weiskopf and Weng (2013) offer for record quality, a flag error is usually a failure of completeness at admission that becomes a failure of correctness on the claim. What remains unknown, and what this study adds, is current, condition-specific evidence for nursing-sensitive conditions and a test of the documentation link.

What this page is doingThe rationale condenses the synthesis without repeating it.
5

Framework

The study follows each flag along four steps: the patient's condition on arrival, what clinicians record in the first day, what the coder sees and decides and the value that reaches the claim. The outcome compares the last step with the first as reconstructed by re-abstraction. Documentation at the second step is the main explanatory variable, and admission source, unit, condition and coder experience act as controls. The framework's blind spot, conditions present at arrival that no one ever recorded, is acknowledged as a limit on detecting under-reporting.

What this page is doingThe framework appears in brief, with its blind spot.
6

Design and Sample

The explanatory sequential design runs a quantitative record review first and uses its results to choose interviewees and topics, integrating both strands in the interpretation as Fetters et al. (2013) recommend. Eligible records are fiscal 2026 adult discharges with one of the four conditions as a secondary diagnosis. To estimate agreement within five percentage points at 95% confidence, assuming about 75% agreement, roughly 289 records are needed; 320 will be drawn at random, 80 per condition, to allow for unusable records and to describe each condition.

What this page is doingDesign and sample are summarized with the calculation.
7

Instrument and Data Collection

Each sampled chart will be re-read by one of two credentialed coders new to those records with a structured tool, blinded to the coded flag. The tool's rules were reviewed by a wound care nurse and two coding experts, and two pilot rounds raised interrater kappa from about 0.80 to about 0.89, within the range McHugh (2012) describes as strong. One record in ten will be double-abstracted throughout, with a third reviewer settling disagreements and abstraction pausing if kappa drops below 0.80.

What this page is doingReliability evidence is reported, not promised.
8

Analysis

Agreement will be reported as a weighted proportion with a 95% confidence interval, overall and by condition. An exact binomial test will compare over- and under-reports. Logistic regression will estimate adjusted odds of disagreement for records without a 24-hour assessment; with about 80 expected disagreements and six predictor terms, the model meets the guidance of roughly ten events per variable from Peduzzi et al. (1996). Interviews with four coders and four nurses from the units with most disagreement will be analyzed thematically, following Braun and Clarke (2006), and a second analyst will check coding on two transcripts.

What this page is doingEach question has its test, and model adequacy is checked.
9

Ethics and Privacy

Because reading records poses minimal risk, the study will seek expedited review board approval with a waiver of HIPAA authorization, since contacting several hundred former patients is impracticable and identifiers will be protected. Study numbers replace record numbers, the linking key sits in a separate encrypted file and identifiers are destroyed after analysis. Abstractors collect only the tool's fields. Interviewees give written consent and are never identified to supervisors. A plain-language summary of findings will be posted for the community whose records were used.

What this page is doingProtections go beyond minimum compliance.
10

Timeline and Budget

The study runs seven months: board review in month one, abstraction in months two to four, analysis in month five, interviews in month six and integration and writing in month seven. Table 1 lists the budget, which consists mainly of staff time.

Table 1. Study Budget

ItemBasisCost
AbstractionTwo coders, about 160 hours each at $44 per hour$14,080
Double abstraction and reviewsAbout 40 hours$1,760
Interview transcriptionEight interviews$960
Statistical consultationTen hours$1,500
Total$18,300

Note. Staff time is charged at fully loaded internal rates; software is already licensed.

What this page is doingA small, itemized budget supports feasibility.
11

Dissemination and Use

Findings will go first to the quality, coding and nursing leaders who must act on them, then to the review board and the community summary, and finally to a regional health information conference. If missing admission assessments prove to be a strong predictor, the hospital's planned redesign of nursing templates can make the assessment a required step, and coding policy can direct queries when it is absent. The capstone will carry out this plan.

What this page is doingResults are tied to specific decisions.
12

Conclusion

This proposal asks a narrow question with broad consequences: whether a one-character field on the claim tells the truth about harm in the hospital. It answers with a design matched to the question, a tested gold standard, an analysis plan sized to the data and protections for the patients whose records make the study possible.

What this page is doingThe proposal closes on its central question.
13

References

Bahl, V., Thompson, M. A., Kau, T.-Y., Hu, H. M., & Campbell, D. A. (2008). Do the AHRQ patient safety indicators flag conditions that are present at the time of hospital admission? Medical Care, 46(5), 516-522. https://doi.org/10.1097/MLR.0b013e31815f537f

Braun, V., & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77-101. https://doi.org/10.1191/1478088706qp063oa

Fetters, M. D., Curry, L. A., & Creswell, J. W. (2013). Achieving integration in mixed methods designs: Principles and practices. Health Services Research, 48(6pt2), 2134-2156. https://doi.org/10.1111/1475-6773.12117

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

Peduzzi, P., Concato, J., Kemper, E., Holford, T. R., & Feinstein, A. R. (1996). A simulation study of the number of events per variable in logistic regression analysis. Journal of Clinical Epidemiology, 49(12), 1373-1379. https://doi.org/10.1016/S0895-4356(96)00236-3

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 9 instructions ask for

HIM 675 ends in Module Nine with a complete research proposal built from your three milestones and revised using instructor feedback. Most guidelines expect eight to twelve pages in APA 7 plus tables. Include an abstract, a concise problem statement with research questions and hypotheses, a rationale grounded in the literature, the conceptual framework, design and sampling with the size calculation, the instrument with reliability evidence, an analysis plan for each question, ethics and privacy protections, a timeline, a budget and a dissemination plan. Condense rather than paste the milestones. Make sure questions, variables and analyses match exactly, since reviewers check alignment first, and write so a review board or capstone committee could approve it as it stands.

How this HIM 675 Module 9 final project example is built

Cimarron Heights Medical Center's proposal opens with an abstract summarizing a 37% pressure injury flag problem and the three questions. The rationale condenses Goldman and colleagues' statewide audit, Bahl and colleagues' safety indicator shifts and Weiskopf and Weng's data quality dimensions. A four-step framework names its blind spot. The design follows Fetters and colleagues, the sample of 320 rests on a 289-record calculation and pilot kappa of about 0.89 meets McHugh's strong range. Logistic regression is checked against Peduzzi and colleagues, interviews follow Braun and Clarke, and ethics include a HIPAA waiver and a community summary. Table 1's $18,300 budget and a dissemination plan close the HIM 675 proposal.

Where the HIM 675 Module 9 rubric puts the points

Graders of the HIM 675 final proposal generally weigh alignment among problem, questions, framework, variables and analysis; the quality of the rationale; a design and sample that fit the questions with a shown calculation; an instrument with evidence of validity and reliability; an analysis plan matched to each question; thorough ethics and privacy protections; feasibility shown through timeline and budget; and a clear plan for using results. The highest ratings go to proposals that could be submitted to a review board with minor edits. Concise writing that condenses milestones, consistent figures across sections and correct APA 7 formatting, including an abstract, distinguish strong work from assembled drafts.

HIM 675 Module 9 help: the mistakes that cost points

Final proposals in this course often lose points by stitching milestones together without revision, leaving numbers that disagree between sections, omitting the abstract, timeline or budget, or describing analysis that no longer matches revised questions. Some also skip how results will be used. If your proposal studies a different HIM problem or uses a survey, a quasi-experimental design or secondary data, pass along all three milestone drafts, your instructor's notes on them and the final directions, and the proposal will grow from that material. Point out any questions your instructor asked you to change. Our HIM 675 proposals condense each milestone, align every question with its analysis and read as ready for a review board.

Get HIM 675 Module 9 written to your instructions

Share the HIM 675 final directions, your milestone drafts and whatever feedback they received. The proposal will add an abstract, condense and align every section from problem to analysis, keep figures consistent and finish with ethics, timeline, budget and a plan for using results, returned in 24 to 48 hours and free for a first request. 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 9 questions, answered

Where can I find a free HIM 675 Module 9 Final Project sample?

This page shows the complete HIM 675 final project, a research proposal on present-on-admission flag accuracy with abstract, framework, design, sample, analysis, ethics, timeline and budget.

What sections does an HIM 675 research proposal need?

Typically an abstract, problem and questions, literature rationale, framework, design and sample, instrument, analysis plan, ethics and privacy, timeline, budget and dissemination.

Should the final proposal repeat the milestones?

No. Condense and revise them using instructor feedback so that the proposal reads as one document with consistent figures and aligned questions and analyses.

Does a student research proposal need a budget?

Many guidelines ask for one. Even a small budget of staff hours and services shows the study is feasible.

How does the HIM 675 proposal connect to the capstone?

The proposal is usually the plan the capstone carries out, so it should be specific enough to implement without redesign.