HIM 690 Module 3 Progress Report Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 690 Module 3 Progress Report sample shows how a capstone student reports on data collection while the work is still under way. It was written for SNHU HIM 690 (HIM-690), where the third module asks MS Health Information Management candidates to report progress honestly, including problems and changes. The composite study, at an academic hospital in Tulsa, re-abstracts records to check how well admission flags on four tracked complications match the chart. At the midpoint, 214 of 318 records are complete. The report gives reliability for each batch, explains two exclusions, shows why each record is taking longer than planned, describes a decision rule that had to be clarified and how it was handled without biasing earlier work, and closes with next steps and a specific request to the project's sponsors.

CourseHIM 690 Health Information Management Capstone
ModuleModule 3
Paper typegraduate capstone progress report on data collection and reliability
LengthAbout 1,020 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMS Health Information Management
UpdatedOctober 2026

Free sample paper for HIM 690 Module 3

1

Midpoint: A Progress Report on Data Collection for the Cimarron Heights Flag Accuracy Capstone

[Student Name]

Southern New Hampshire University

HIM 690: Health Information Management Capstone

Module Three Progress Report

[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 marks the report's place in the project.
2

Midpoint: A Progress Report on Data Collection for the Cimarron Heights Flag Accuracy Capstone

This report covers the first six weeks of data collection for the Tulsa capstone that is comparing coded admission flags with a blinded second reading of each chart. It is written for the capstone advisor and the two sponsors, the hospital's nursing chief and its HIM director. It reports what has been completed, how reliable the work has been, what has gone wrong and what comes next.

What this page is doingThe audience and purpose are stated first.
3

Progress Against Plan

Two of three abstraction batches are finished. Of the 318 records in the sample, 214 have been abstracted, against a plan of 212 by the end of week six, so the count is on track. The breakdown by complication is 54 pressure wound records, 54 catheter infection records, 54 venous clot records and 52 fall injury records. Two records were excluded. In one, the patient was transferred from another hospital and the transfer documents were never scanned into the chart, so the condition at arrival could not be judged from the record at all. In the other, the coded condition had been entered on the wrong patient's account and corrected after billing, which made the original flag meaningless for the study. Both exclusions meet the exclusion rule for records missing essential documentation, and both were logged with reasons. One replacement record was drawn at random for the first; the second came from the fall stratum, which has no spares, so falls will finish at 77 records. The sample remains balanced enough across the four strata to describe each one separately as planned.

What this page is doingCounts are reported against the plan, with exclusions explained.
4

Reliability

Every tenth record in each batch was abstracted by both coders. Agreement in batch one was 31 of 33 records, kappa 0.86, and in batch two 32 of 34, kappa 0.88. McHugh (2012) places values from 0.80 to 0.90 in the strong range and cautions that percent agreement alone overstates reliability, which is why kappa is reported for each batch rather than a single overall figure. Both batches cleared the proposal's minimum of 0.80, so abstraction did not need to pause. The four disagreements were reviewed by the coding quality lead, and three were resolved by applying the written rules; the fourth led to the rule clarification described below.

What this page is doingReliability is reported per batch against the preset threshold.
5

A Rule Clarification

In batch two, the coders disagreed about a patient whose pressure wound was described in the emergency department note as a red area on the sacrum, then staged by the wound nurse on day two as a deep tissue injury. One coder judged the wound present on arrival; the other judged it clinically undetermined. The written rule covered deep tissue injuries first documented after day one but not a red area documented at arrival and staged later. With the advisor's approval, the rule was clarified: an area at the same site documented at arrival, even without a stage, counts as present on admission if the later staging confirms a pressure injury there. To avoid applying the clarification unevenly, both coders re-reviewed every pressure wound record already abstracted, 54 in all; the clarification changed the abstracted flag in three records, and those changes are logged.

What this page is doingA mid-study change is handled transparently and applied backward.
6

Time and Workload

Abstraction is taking about 31 minutes per record against the 25 minutes planned. Almost all of the extra time goes to scanned outside records, such as nursing home transfer forms, which are stored as image files and must be read page by page. At the current pace, batch three will take one week longer than scheduled. The reserve week held in the charter will absorb this, so the overall schedule does not change, but there is no further buffer.

Two options for regaining time were considered and rejected. Skipping the scanned outside records would have been faster but would have biased the results, because those records are exactly where evidence of conditions present on arrival tends to sit for patients from facilities. Adding a third abstractor would have required new training and a new reliability check partway through the study. Absorbing the delay in the reserve week was the least risky choice.

What this page is doingThe delay is quantified and its cause identified.
7

Data Quality Checks

Following the verification approach described by Kahn et al. (2016), the writer runs three checks on the abstraction file each week: every required field is present, every coded value is one of the allowed choices and no assessment time falls before the admission time or after discharge. The checks found two blank fields and one impossible time in batch one, all corrected from the source records within a day, and none in batch two. A plausibility review compared the share of records with a documented 24-hour skin assessment across units. One unit's share, 92%, was well above the others, which range from 61% to 74%; a spot check confirmed that the unit uses a different admission template that requires the assessment, which is a finding worth carrying into the analysis rather than an error. Weiskopf and Weng (2013) recommend combining several assessment methods, and the weekly checks provide that alongside the double abstraction.

What this page is doingWeekly verification and plausibility checks are described with results.
8

Early Observations

The study's analysis has not begun, and early counts should not be over-read. Still, two patterns are visible enough to shape the interview phase, which the charter allowed to begin early. Disagreement appears more frequent among pressure wound records than among the other three complications, and many disagreements involve patients admitted from long-term care facilities. Interviews will therefore include the two units admitting the most such patients.

These patterns will be tested, not assumed, once all records are in; if they fade in the full data, the interviews will still be useful for understanding how flags are set, but the report will say plainly that the early impression did not hold.

What this page is doingEarly patterns are used only to plan interviews, with caution.
9

Next Steps and Request

Batch three begins Monday and should finish in two and a half weeks. Interviews start next week with four coders and four nurses. One request goes to the sponsors: the chief nursing officer is asked to release two night-shift nurses for 30-minute interviews during paid time, since recruitment has so far drawn only day-shift staff and the study's early patterns point to night admissions.

What this page is doingThe report ends with a concrete ask.
10

References

Kahn, M. G., Callahan, T. J., Barnard, J., Bauck, A. E., Brown, J., Davidson, B. N., Estiri, H., Goerg, C., Holve, E., Johnson, S. G., Liaw, S.-T., Hamilton-Lopez, M., Meeker, D., Ong, T. C., Ryan, P., Shang, N., Weiskopf, N. G., Weng, C., Zozus, M. N., & Schilling, L. (2016). A harmonized data quality assessment terminology and framework for the secondary use of electronic health record data. eGEMs, 4(1), Article 1244. https://doi.org/10.13063/2327-9214.1244

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 690 Module 3 instructions ask for

HIM 690's third module asks for a progress report on your capstone. Most reports run three to four pages in APA 7 and are addressed to your advisor and sponsors. Compare progress with the plan in numbers, such as records completed or participants recruited. Report reliability or quality checks with the measure your proposal promised, for each batch or stage. Explain any exclusions, delays or problems and what caused them. Describe any rule or method changes, who approved them and how you applied them fairly to work already done. Note early observations only if they guide later steps, and label them as preliminary. Close with next steps and any specific help you need from sponsors.

How this HIM 690 Module 3 progress report example is built

Cimarron Heights Medical Center's report shows 214 of 318 records abstracted against a plan of 212. Two exclusions are explained, an unscanned transfer packet and a condition charted on the wrong account, leaving falls at 77. Batch kappas of 0.86 and 0.88, read against McHugh's ranges, clear the 0.80 bar. A disagreement over a red sacral area staged on day two prompts an approved rule clarification, applied backward to all 54 earlier wound records, changing three. Abstraction runs 31 minutes per record instead of 25, absorbed by the reserve week. Weekly checks follow Kahn and colleagues and Weiskopf and Weng. The HIM 690 report closes asking for night-shift nurses to be released for interviews.

Where the HIM 690 Module 3 rubric puts the points

In HIM 690, progress reports are generally graded on accurate comparison with the plan, reliability or quality measures reported as promised, honest explanation of exclusions, delays and changes, fair handling of any mid-study change, cautious treatment of early observations and clear next steps. Reports that score highest show that the student is managing the project, catching problems early and documenting decisions, rather than simply reporting activity. Graders value concise tables or counts, explicit links to the charter and proposal and a specific request when help is needed. Professional tone for a sponsor audience and correct APA 7 citations for any methods sources complete the stronger reports.

HIM 690 Module 3 help: the mistakes that cost points

Progress reports in this course lose points by reporting effort instead of results, hiding exclusions or delays, changing a rule without applying it to earlier work, overinterpreting early numbers or ending without next steps. Some forget the reliability measure they promised. If your capstone is an operational project, such as an implementation or a policy rollout, send the prompt and your charter so the report compares progress with your own milestones. Bring your actual counts, even if they are behind plan, because an honest report scores better than a polished one. Our HIM 690 progress reports measure against the plan, explain every deviation and end with a clear ask.

Get HIM 690 Module 3 written to your instructions

Send the HIM 690 Module 3 prompt, your charter and where your data collection stands. The report will compare progress with plan in numbers, report reliability as promised, explain exclusions, delays and any rule changes, treat early patterns cautiously and close with next steps and a request, returned in one to two days, free for a first order. 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 690 papers and related MS Health Information Management samples

HIM 690 Module 3 questions, answered

Where can I find a free HIM 690 Module 3 Progress Report sample?

This page carries the complete HIM 690 Module 3 progress report from a flag accuracy capstone at its midpoint, with batch reliability, exclusions, a rule clarification and next steps.

What should a capstone progress report include?

Progress against plan in numbers, reliability or quality measures, explanations of exclusions and delays, any method changes and how they were applied, next steps and requests for help.

How should a rule change during data collection be handled?

Get approval, document the change and the reason and re-review earlier records under the clarified rule so the rule is applied evenly.

Should early results appear in a progress report?

Only as preliminary patterns that guide the next steps, such as interview sampling, and clearly labeled as not yet analyzed.

What if my capstone is behind schedule?

Say so with numbers, explain the cause and show how reserve time or a scope adjustment will absorb the delay.