HIM 215 Module 7 Project Two Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 215 Module 7 Project Two sample designs the coding audit program a hospital would use to find and fix errors before payers do. It is written for SNHU HIM 215 (HIM-215), a BS Health Information Management course that ends by turning coding knowledge into quality control. The composite 220-bed regional hospital agreed with its external auditor on 91% of MS-DRGs last year, faces rising sepsis denials and has never audited outpatient visit levels. The plan sets objectives, defines random and focused samples, explains how accuracy is scored and errors categorized, protects reviewer independence, describes a reconciliation and rebilling process that meets the 60-day overpayment rule and adds education, reporting and a timeline. Research on coding accuracy supports each design choice.

CourseHIM 215 Coding & Classification Systems
ModuleModule 7
Paper typeundergraduate coding quality audit plan for a hospital
LengthAbout 1,150 words, 7 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramBS Health Information Management
UpdatedSeptember 2026

Free sample paper for HIM 215 Module 7

1

Project Two: Catching Errors Before the Payer Does, a Coding Quality Audit Plan for Glenwood Regional Hospital

[Student Name]

Southern New Hampshire University

HIM 215: Coding & Classification Systems

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

What this page is doingThe title states the plan's purpose from the hospital's point of view.
2

Project Two: Catching Errors Before the Payer Does, a Coding Quality Audit Plan for Glenwood Regional Hospital

Purpose and Scope

This plan establishes a coding quality audit program for Glenwood Regional Hospital covering inpatient ICD-10-CM, ICD-10-PCS and MS-DRG assignment and outpatient ICD-10-CM, CPT and HCPCS coding, including office visit levels and modifiers. Its purpose is to measure accuracy, identify patterns, correct claims in both directions and target education. It applies to all fifteen staff coders and to the two clinical documentation specialists whose queries shape coded data.

What this page is doingThe plan's purpose and scope are defined.
3

Where Glenwood Stands

The last external audit agreed with Glenwood's MS-DRG assignment on 91% of 200 sampled inpatient cases. About 23% of sepsis claims submitted last year were denied on clinical validation grounds, and fewer than half of those denials were overturned on appeal. Outpatient visit levels have never been audited, although physicians' distribution of established patient visits has shifted toward 99214 and 99215 over three years. Discharged charts wait an average of 5.8 days for final coding against a four-day target.

What this page is doingCurrent performance is summarized.
4

Objectives

Within twelve months, the program aims to raise MS-DRG agreement to at least 95%, reach code-level accuracy of at least 95% for inpatient diagnoses and procedures, reach at least 90% agreement on outpatient visit levels, reduce sepsis denials by a third through pre-bill review and achieve full compliance with query practice standards in a quarterly query audit. Accuracy targets apply to errors in both directions.

What this page is doingMeasurable objectives are set.
5

Why Audits Matter

Research supports routine auditing. Burns et al. (2012) found wide variation in discharge coding accuracy across studies, which suggests that local processes strongly affect results. O'Malley et al. (2005) listed a hospital's own checking routines among the forces that raise or lower accuracy. Cheng et al. (2009) used a blind re-coding audit of 752 surgical discharges to reveal discrepancies that changed payment groups, many traceable to documentation, and showed how audit findings can direct improvement.

What this page is doingResearch on audits is summarized.
6

Types of Review

The program combines two timings and two selection methods. Pre-bill reviews examine charts before claims are sent, which prevents errors from reaching payers and avoids rebilling. Retrospective reviews examine paid claims to measure accuracy over time. Random samples give an unbiased estimate of overall accuracy, while focused samples target case types known to carry high risk. Using both avoids the trap of measuring only problem areas or only easy cases.

What this page is doingReview timing and selection methods are explained.
7

Inpatient Sampling

Each month, the audit team will randomly select 30 inpatient discharges, about 3% of volume, stratified so every coder contributes at least two charts. A focused pre-bill sample of 20 more charts will target sepsis, respiratory failure, heart failure with a documented acute exacerbation, malnutrition reported as a complication and cases where a single secondary diagnosis moved the MS-DRG to a higher level. Findings from the focused sample are reported separately so they do not distort the overall accuracy rate.

What this page is doingThe inpatient sampling plan is defined.
8

Outpatient Sampling

For outpatient coding, five charts per coder will be selected at random each month from emergency, clinic and outpatient surgery encounters. A separate provider review will examine ten established patient visits per physician each year, with more frequent review for physicians whose share of the two highest levels is well above peers. Modifier 25 and 59 claims will be sampled quarterly, since these modifiers bypass edits.

What this page is doingThe outpatient sampling plan is defined.
9

How Accuracy Is Scored

Reviewers re-code each chart independently, without seeing the original codes, following the blind approach Cheng and colleagues used, and then compare. Code-level accuracy is the share of codes that match, counting added and missing codes as errors. MS-DRG accuracy is the share of cases whose group did not change. Each discrepancy is assigned to a category and marked for financial direction: overpayment, underpayment or no payment effect.

Table 1. Error Categories

CategoryExamples
Principal diagnosis selectionSymptom sequenced over confirmed diagnosis; sepsis sequencing
Secondary diagnosis added or omittedUnsupported MCC added; supported CC missed
Procedure codingWrong root operation, approach or device
Present-on-admission indicatorN assigned to a condition present at admission
Outpatient level or modifierVisit level not supported; modifier 25 without separate service
Query practiceLeading query; missing clinical indicators

Note. Categories adapted by the author for Glenwood's audit database.

What this page is doingScoring rules are explained and error categories listed in Table 1.
10

Reviewer Qualifications and Independence

Internal reviewers must hold a coding credential appropriate to the setting and have at least three years of experience. No one reviews their own work. The coding quality lead reports to the HIM director, not to revenue cycle leadership, to keep audits focused on accuracy. An outside firm will audit a sample of 100 inpatient and 100 outpatient cases each year, including a check on the internal reviewers' own accuracy.

What this page is doingReviewer standards and independence are set.
11

Reconciliation and Correction

Each discrepancy goes back to the original coder, who may agree or submit a written rebuttal with guideline references within five business days. The coding quality lead resolves disagreements, consulting official guidance when needed. For retrospective findings, corrected claims are resubmitted whether the correction raises or lowers payment. When an overpayment is identified, federal law gives the hospital 60 days from identification to report the money and pay it back, so confirmed overpayments are sent to the compliance office within two business days of final resolution.

What this page is doingThe reconciliation process and the 60-day rule are described.
12

Education and Feedback

Audit results drive education rather than punishment. Each coder receives a monthly report showing accuracy and error categories. Patterns across coders prompt short group sessions, for example on sepsis sequencing or PCS approaches. Patterns tied to documentation, such as unspecified heart failure, go to the clinical documentation specialists and physician advisors for provider education. Coders whose accuracy stays below 90% for two quarters receive a focused improvement plan with additional review.

What this page is doingThe feedback and education loop is described.
13

Reporting

The coding quality lead will produce a monthly dashboard with overall and coder-level accuracy, MS-DRG agreement, error categories, financial effects in both directions and sepsis denial rates. A quarterly summary will go to the compliance committee. Rhee et al. (2017) showed how documentation and coding changes can alter what data appear to show, so the dashboard will also track the share of discharges coded with sepsis to watch for unexplained shifts.

What this page is doingReporting to leaders and the compliance committee is described.
14

Timeline

The program will launch in phases over six months so tools and staff are ready before full sampling begins.

Table 2. Implementation Timeline

MonthActivity
1Approve policy; build audit database and worksheet
2Train reviewers; pilot inpatient random sample
3Begin focused sepsis pre-bill review
4Add outpatient coder sample and modifier review
5Begin provider visit-level review
6First quarterly report to compliance committee

Note. Timeline approved by the HIM director.

What this page is doingThe implementation timeline is shown in Table 2.
15

Evaluating the Program

After one year, the program will be judged on whether objectives were met, whether external audit results agree with internal findings and whether errors in targeted categories declined. If internal and external accuracy rates differ by more than three percentage points, the sampling or scoring method will be reviewed.

What this page is doingCriteria for evaluating the program are set.
16

Conclusion

A structured audit program gives Glenwood a reliable measure of coding accuracy, catches high-risk errors before billing and turns findings into targeted education. By combining random and focused samples, blind re-coding, reviewer independence and prompt correction in both directions, the plan protects revenue and compliance while strengthening the data the hospital and its patients depend on.

What this page is doingThe conclusion summarizes the plan's value.
17

References

Burns, E. M., Rigby, E., Mamidanna, R., Bottle, A., Aylin, P., Ziprin, P., & Faiz, O. D. (2012). Systematic review of discharge coding accuracy. Journal of Public Health, 34(1), 138-148. https://doi.org/10.1093/pubmed/fdr054

Cheng, P., Gilchrist, A., Robinson, K. M., & Paul, L. (2009). The risk and consequences of clinical miscoding due to inadequate medical documentation: A case study of the impact on health services funding. Health Information Management Journal, 38(1), 35-46. https://doi.org/10.1177/183335830903800105

O'Malley, K. J., Cook, K. F., Price, M. D., Wildes, K. R., Hurdle, J. F., & Ashton, C. M. (2005). Measuring diagnoses: ICD code accuracy. Health Services Research, 40(5, Pt. 2), 1620-1639. https://doi.org/10.1111/j.1475-6773.2005.00444.x

Rhee, C., Dantes, R., Epstein, L., Murphy, D. J., Seymour, C. W., Iwashyna, T. J., Kadri, S. S., Angus, D. C., Danner, R. L., Fiore, A. E., Jernigan, J. A., Martin, G. S., Septimus, E., Warren, D. K., Karcz, A., Chan, C., Menchaca, J. T., Wang, R., Gruber, S., & Klompas, M. (2017). Incidence and trends of sepsis in US hospitals using clinical vs claims data, 2009-2014. JAMA, 318(13), 1241-1249. https://doi.org/10.1001/jama.2017.13836

What the HIM 215 Module 7 instructions ask for

HIM 215 Project Two typically asks you to design a coding quality or compliance audit for a healthcare organization. Most versions land between 1,500 and 2,000 words and draw on three or more peer-reviewed articles in APA 7. Describe current performance, set measurable objectives and explain both how charts will be selected and how accuracy will be scored. Address reviewer qualifications and independence, reconciliation with coders, correction of claims in both directions, education, reporting and a timeline, and note legal requirements such as the rule for returning overpayments. HIM 215 graders notice clean headings in HIM 215 papers. HIM 215 names and dates need checking before HIM 215 submission. HIM 215 prompts vary by term, so recheck HIM 215 directions.

How this HIM 215 Module 7 project two example is built

The plan defines scope across inpatient and outpatient coding, reports 91% MS-DRG agreement, 23% sepsis denials and no visit-level audits and sets objectives. Burns, O'Malley and Cheng support auditing. It combines pre-bill and retrospective, random and focused reviews, with monthly inpatient and outpatient samples. Blind re-coding, an error category table, reviewer independence, rebuttals, correction in both directions and the 60-day overpayment rule follow, then education, a dashboard that watches sepsis coding shifts noted by Rhee and colleagues, a timeline and evaluation criteria. HIM 215 students can reuse this structure for HIM 215 work. HIM 215 claims here trace to cited HIM 215 sources. HIM 215 readers can adapt each section to HIM 215 data.

Where the HIM 215 Module 7 rubric puts the points

Audit plans in HIM 215 are commonly graded on clarity of objectives, soundness of sampling, rigor of scoring methods, reviewer independence, correction and compliance processes, education and reporting, feasibility and APA 7 mechanics. The strongest plans separate random from focused findings, count errors in both directions, include a rebuttal process and link audit results to documentation education. Graders reward attention to legal obligations, such as returning overpayments promptly. Plans that also say how the program itself will be judged after a year, and what would trigger a change in method, show mature thinking about quality control. HIM 215 marks favor careful formatting across HIM 215 sections. HIM 215 citations keep every HIM 215 argument credible. HIM 215 instructors weigh evidence heavily in HIM 215 grading.

HIM 215 Module 7 help: the mistakes that cost points

Audit plans lose points when they sample only problem cases, score only payment-changing errors, let coders audit themselves or ignore underpayments. Another frequent gap is failing to explain what happens after an error is found. Set objectives, define samples, score blind, protect independence, correct both directions, educate and report. If your prompt asks for a specific audit tool, sample size formula or payer focus, send it with your HIM 215 notes so the plan matches. Current audit results or denial data, even rough figures, help set realistic objectives. HIM 215 drafts start well from a HIM 215 outline. HIM 215 feedback already received guides HIM 215 revisions. HIM 215 rubrics posted in Brightspace clarify HIM 215 expectations.

Get HIM 215 Module 7 written to your instructions

Send the HIM 215 Project Two prompt and what you know about the organization. The plan will set objectives, define random and focused samples, explain blind scoring and error categories, protect reviewer independence and describe correction, education and reporting, within 24 to 48 hours, free the first time. 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 215 papers and related BS Health Information Management samples

HIM 215 Module 7 questions, answered

Where can I find a free HIM 215 Module 7 Project Two sample?

You can read HIM 215 Project Two in full here: a hospital coding audit plan with objectives, sampling, scoring, reconciliation and reporting.

What is the difference between random and focused coding audits?

Random samples estimate overall accuracy; focused samples target high-risk case types and should be reported separately.

What is blind re-coding?

A reviewer codes the chart without seeing the original codes, then compares, reducing bias toward agreement.

How quickly must overpayments be returned?

Federal law requires identified overpayments to be reported and returned within 60 days.

Should audits count underpayments?

Yes. Accuracy means errors in both directions, and underpayments misstate patient severity in data.