| Course | HIM 440 Management of Health Information Services |
|---|---|
| Module | Module 5 |
| Paper type | undergraduate milestone presenting a process improvement plan |
| Length | About 1,030 words, 6 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | BS Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM 440 Module 5
Final Project Milestone Two: From 5.6 Days to 3.0, a Process Improvement Plan for Unbilled Accounts at Kettle Creek
[Student Name]
Southern New Hampshire University
HIM 440: Management of Health Information Services
Final Project Milestone Two
[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.
Final Project Milestone Two: From 5.6 Days to 3.0, a Process Improvement Plan for Unbilled Accounts at Kettle Creek
The Module Four redesign showed that Kettle Creek Medical Center's unbilled accounts are a flow problem, with 42 minutes of work spread over 6.1 days. A redesign on paper does not change anything by itself. This milestone presents the plan for making the change: what the team aims to achieve, which drivers it will work on, how changes will be tested in small cycles, how progress will be measured and who is responsible for each part.
Aim Statement
Within twelve months, Kettle Creek will reduce unbilled days awaiting coding or documentation from 5.6 to 3.0 and, within six months, keep delinquent records below the hospital's accreditation threshold every month, while holding principal diagnosis coding accuracy at or above 95%. The accuracy condition is part of the aim so that speed is never bought with errors.
Driver Diagram
Working backward from the aim, the team listed what has to be true for unbilled days to fall and then what could make each of those things true. Table 1 summarizes the team's diagram. Five primary drivers came from the process map: documentation complete at discharge, documents available immediately, coding work sequenced well, questions answered quickly and enough trained coders.
Table 1. Driver Diagram for the Aim
| Primary driver | Secondary driver | Change idea |
|---|---|---|
| Documentation complete at discharge | Discharge summaries done promptly | 24-hour discharge summary rule with physician-level feedback |
| Documents available immediately | Paper scanned at the source | Unit clerks scan at discharge |
| Coding work sequenced well | Charts released only when complete; value and age considered | Hold-until-complete rule; prioritized queue |
| Questions answered quickly | Queries reach physicians who respond | Escalation at 24 and 48 hours; physician advisor calls |
| Enough trained coders | Vacancies filled; turnover reduced | Market pay review; monthly team meetings; coder career ladder |
Note. Developed by the planning team from the Module Four process map.
Testing Changes in Small Cycles
No change idea spreads until it has survived small plan-do-study-act tests. Taylor et al. (2014) reviewed published uses of the method in health care and found that many projects reported a single large change labeled as a cycle, with few documenting a series of small, linked tests or the data used to learn from them. The team will avoid that pattern by starting small, predicting results before each test and writing down what was learned. Table 2 shows the first four cycles.
Table 2. First Four Plan-Do-Study-Act Cycles
| Cycle | Test | Scale and length | Prediction | Measure |
|---|---|---|---|---|
| 1 | Unit clerk scans discharge documents | One medical unit, one week | Scanning wait under 0.3 days | Wait time; scanning errors |
| 2 | Hold-until-complete coding queue | Inpatient medicine charts, two weeks | Charts opened twice fall below 15% | Reopen rate; coding wait |
| 3 | Query escalation at 24 and 48 hours | Hospitalist group, three weeks | Median response under 1 day | Query response time |
| 4 | Weekly discharge summary feedback by physician | Two surgical services, four weeks | Summaries within 24 hours rise above 80% | Share completed in 24 hours |
Note. Cycles planned by the team; later cycles will depend on results.
Feedback to Physicians
Two drivers depend on physicians. Across the randomized studies Ivers et al. (2012) brought together on performance feedback, they reported average gains that were modest, yet noticeably bigger for clinicians who started well below standard and for feedback that arrived more than once, from someone the clinician respected, with an explicit goal and steps to reach it. Kettle Creek's design borrows each of those features: each physician will receive a weekly list of their incomplete records and open queries, the hospitalist chair of the medical records committee will present monthly results by service and every report will show the target alongside the physician's own numbers.
Measures
Measurement comes in three layers. At the top sit unbilled days, the monthly delinquency rate and principal diagnosis accuracy. Process measures include scanning wait, how often a coder must reopen a chart, median query response time and the share of discharge summaries completed within 24 hours. Balancing measures watch for harm elsewhere: scanning errors on the units, coder overtime hours, physician complaints to the medical staff office and claim denials for coding reasons. Benneyan et al. (2003) describe how statistical process control helps separate real improvement from normal variation, so outcome and process measures will be plotted on control charts, and a change will be judged successful only when the charts show a sustained shift.
Roles and Communication
The coding manager leads cycles two and three, the scanning supervisor and a unit manager lead cycle one and the physician advisor leads cycle four. The director owns the overall plan and reports to the sponsor monthly. A single page with the aim, the current charts and the next tests will be posted in the department and shared with patient financial services and the medical records committee each month, so every group sees the same numbers.
Risks to the Plan
The plan could stall in three places. Unit clerks may not have time to scan during busy discharge periods, so cycle one includes a count of discharges per shift and a fallback to central scanning when a unit exceeds a set number. Physicians may treat weekly lists as another nuisance; the physician advisor will ask the medical executive committee to endorse the feedback before cycle four begins. And vacancies could undo gains if two more coders leave; the market pay review and career ladder are being pursued in parallel, outside the test cycles, because they depend on human resources and budget decisions rather than on department process.
Holding the Gains
Improvements fade when attention moves on. Changes that succeed will be written into department procedures and job descriptions, the unit clerk scanning task will be added to unit orientation, and the discharge summary rule will be proposed for the medical staff rules. Control charts will continue after the project ends, with a trigger for review if a measure crosses its control limit two months in a row.
Conclusion
This plan converts Kettle Creek's redesign into a sequence of small, measured tests aimed at cutting unbilled days to 3.0 and keeping delinquency under the threshold without sacrificing accuracy. A driver diagram ties each change to the aim, plan-do-study-act cycles test changes before they spread, feedback follows the evidence and balancing measures watch for harm. The final project will place this plan within a three-year strategy for the department.
References
Benneyan, J. C., Lloyd, R. C., & Plsek, P. E. (2003). Statistical process control as a tool for research and healthcare improvement. Quality and Safety in Health Care, 12(6), 458-464. https://doi.org/10.1136/qhc.12.6.458
Ivers, N., Jamtvedt, G., Flottorp, S., Young, J. M., Odgaard-Jensen, J., French, S. D., O'Brien, M. A., Johansen, M., Grimshaw, J., & Oxman, A. D. (2012). Audit and feedback: Effects on professional practice and healthcare outcomes. Cochrane Database of Systematic Reviews, (6), Article CD000259. https://doi.org/10.1002/14651858.CD000259.pub3
Taylor, M. J., McNicholas, C., Nicolay, C., Darzi, A., Bell, D., & Reed, J. E. (2014). Systematic review of the application of the plan-do-study-act method to improve quality in healthcare. BMJ Quality & Safety, 23(4), 290-298. https://doi.org/10.1136/bmjqs-2013-001862
What the HIM 440 Module 5 instructions ask for
HIM 440 Final Project Milestone Two asks for a process improvement plan built on your earlier analysis. In most HIM 440 sections, three to five pages in APA 7 with tables and scholarly support will do. Your aim needs a number, a deadline and a quality condition, such as accuracy that must not fall. Use a driver diagram or similar tool to connect the aim to its drivers and change ideas, then plan small tests of change, each with a written prediction, using plan-do-study-act or a similar method. Define outcome, process and balancing measures and how you will judge change over time. Assign roles, describe how results will be communicated and explain how gains will be sustained after the project ends.
How this HIM 440 Module 5 final project milestone two example is built
Kettle Creek's plan aims to cut unbilled days from 5.6 to 3.0 in twelve months and keep delinquency below the accreditation threshold in six, while holding coding accuracy at 95%. A driver diagram links five drivers to change ideas such as scanning at discharge and a hold-until-complete queue. Taylor and colleagues' warnings shape four small tests, each with a prediction, and Ivers and colleagues guide weekly physician feedback. Outcome, process and balancing measures, including scanning errors and coder overtime, are tracked on control charts following Benneyan and colleagues. Roles, a one-page monthly report and steps to write successful changes into procedures complete the HIM 440 plan. A short section names the risks that could stall the plan.
Where the HIM 440 Module 5 rubric puts the points
Process improvement milestones in HIM 440 are often scored on a clear aim, a logical link between drivers and changes, small tests of change with predictions, a complete set of measures including balancing measures, appropriate analysis of data over time, defined roles, communication and sustainability and APA 7 mechanics. Top plans show they understand improvement methods well enough to avoid common misuse, such as calling a single large rollout a cycle. Graders reward aims that protect quality and feedback designs grounded in evidence. A plan that already names who will lead each test shows readiness for implementation rather than a paper exercise. Named risks with fallbacks strengthen any plan.
HIM 440 Module 5 help: the mistakes that cost points
Improvement plans in HIM 440 slip when the aim lacks a number or date, when change ideas are not tied to drivers, when a single big change is called a PDSA cycle or when balancing measures are missing. Some drafts also skip how gains will be sustained. If your course case targets a different process, such as release of information turnaround or record completion, send the case facts and your Milestone One so the plan uses your benchmarks and baseline. Add any instructor feedback you received. HIM 440 samples we prepare follow this order: aim, driver diagram, test cycles, feedback design, measures, roles, sustainability and conclusion.
Get HIM 440 Module 5 written to your instructions
Share the HIM 440 Milestone Two guidelines with your Milestone One benchmarks. The plan will set a measurable aim, build a driver diagram, sequence small tests of change with predictions and spell out what will be measured at the outcome, process and balancing levels, finished within 24 to 48 hours with the first sample 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 440 papers and related BS Health Information Management samples
- HIM 440 Module 1 Discussion: The HIM Manager's Role in Leading Change
- HIM 440 Module 2 Current Issues Short Paper: Staffing, Relationships, Productivity and Compliance
- HIM 440 Module 3 Final Project Milestone One: Initiation, Preparation and Performance Benchmarks
- HIM 440 Module 4 Work Redesign Short Paper: Process Maps and Lean Methods for Coding and Scanning
- HIM 422 Module 4 Final Project Milestone Two: Financial and Nonfinancial Impacts of the Anthem Breach
- HIM 350 Module 1 Discussion: How Technology Changed Care Conversations After 2020
- HIM 200 Module 1 Discussion: Why Health Information Technology Matters: From Paper to Digital
- HIM 400 Module 6 Data Sharing Short Paper: Exchange, Patient Access and Information Blocking
HIM 440 Module 5 questions, answered
Where can I find a free HIM 440 Module 5 Final Project Milestone Two sample?
The whole HIM 440 Module 5 milestone is here: an improvement plan with an aim, a driver diagram, four PDSA cycles and measures for unbilled accounts.
What is a driver diagram?
A tool that links an improvement aim to the factors that drive it and to specific change ideas for each factor.
What makes a PDSA cycle well done?
A small test with a stated prediction, data collected during the test and a documented lesson that shapes the next cycle.
What are balancing measures?
Measures that watch for unintended harm elsewhere in the system, such as scanning errors or overtime caused by a change.
How can improvements be sustained?
By writing successful changes into procedures and job descriptions and continuing to monitor measures on control charts.