HIM 600 Module 6 Auditing Short Paper Example

Reviewed by Delia Ravenscroft, MSN, RN

This HIM 600 Module 6 Auditing Short Paper sample sets out how a medical practice decides what to audit, how many claims to pull and what to do with the results. It was written for SNHU HIM 600 (HIM-600), where the sixth module asks MS Health Information Management students to design auditing and monitoring that fits an organization's risks. The composite setting is a 38-physician orthopedic and spine group in Boise whose first record review found nearly half of sampled claims unsupported. The paper scores eight billing areas by likelihood and impact, separates prospective reviews from retrospective ones, sets probe samples of ten claims per clinician, explains when a probe must give way to a statistically valid sample, adds outlier screens on visit levels and billed hours and describes how results reach the compliance committee.

CourseHIM 600 Managing Compliance
ModuleModule 6
Paper typegraduate short paper on risk-based auditing and sampling for coding compliance
LengthAbout 1,060 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMS Health Information Management
UpdatedOctober 2026

Free sample paper for HIM 600 Module 6

1

Looking Where the Risk Is: Audits, Samples and Screens for Sawtooth Bone and Joint

[Student Name]

Southern New Hampshire University

HIM 600: Managing Compliance

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.

What this page is doingThe title states the principle that guides the plan.
2

Looking Where the Risk Is: Audits, Samples and Screens for Sawtooth Bone and Joint

A practice cannot audit everything, and an audit plan that spreads effort evenly will spend most of it where little goes wrong. Sawtooth Bone and Joint, the composite Boise bone and spine practice used throughout this course, has just finished its first record review, in which 18 of 40 level five visits and 11 of 20 modifier 25 injection claims failed. This paper designs the ongoing audit and monitoring plan that follows. It explains how risks are ranked, what kinds of review are used, how many claims are drawn and when, and how results are reported. Federal guidance places continuing risk review, audits and monitoring among the program parts every organization needs and treats them as constant work, not a yearly event (U.S. Department of Health and Human Services, Office of Inspector General [HHS-OIG], 2023).

What this page is doingThe introduction states the problem of limited audit capacity.
3

Ranking the Risks

The compliance committee scored eight billing areas from one to five for likelihood, based on the record review, billing data and staff interviews, and from one to five for impact, based on dollars at stake, the number of patients affected and legal exposure. The product gives a risk score out of 25. Table 1 shows the results. Office visit levels and modifier 25 lead because the review has already shown errors there and both involve thousands of claims a year. MRI referrals score high on impact because a failure of the in-office exception affects every scan billed, even though the likelihood is judged lower. Physical therapy plans of care, brace billing, surgical assistant claims, advanced practice billing and diagnosis specificity follow. The ranking is revisited each year and whenever a new guideline, payer policy or enforcement report changes the picture.

Table 1. Risk Assessment of Eight Billing Areas

AreaLikelihood (1-5)Impact (1-5)ScoreReview type
Office visit levels5420Prospective, then retrospective
Modifier 25 with injections5420Prospective, then retrospective
MRI referral notice and exception2510Retrospective, twice a year
Therapy plan of care certification339Retrospective, twice a year
Brace and splint billing339Retrospective, yearly
Advanced practice billing under physicians339Retrospective, quarterly
Assistant at surgery claims236Retrospective, yearly
Diagnosis specificity and laterality414Monitoring report

Note. Scores set by the compliance committee from the record review, billing data and interviews.

What this page is doingRisks are scored transparently and linked to review types.
4

Prospective and Retrospective Review

The two highest risks start with prospective review, in which a coder checks claims before they are submitted and queries the clinician when documentation does not support the level or modifier selected. Prospective review prevents new errors and gives clinicians immediate feedback, which the record review found to be missing. It is costly, so it runs for each clinician only until that clinician reaches an accuracy rate of 90% on two consecutive monthly samples. Retrospective review, of claims already paid, measures how well the program is working and identifies overpayments that must be returned. Lower-risk areas use retrospective review only, at the frequencies in Table 1.

What this page is doingThe two review types are given distinct purposes.
5

How Many Claims

Sample size depends on the purpose. To learn whether a clinician has a problem, the plan uses a probe of ten claims per clinician per area, chosen at random from the period under review. A probe answers a yes-or-no question and cannot support an estimate of total overpayment. If a clinician's probe shows an error rate above 10%, the review expands to a discovery sample of 30 claims, and if that confirms a pattern, the committee consults counsel about a statistically valid random sample. A statistically valid sample is drawn and analyzed with a documented method, such as the federal RAT-STATS software, so that the result can be extrapolated to the full set of claims with a stated confidence and precision (U.S. Department of Health and Human Services, Office of Inspector General, n.d.). Extrapolation matters when an overpayment must be estimated for refund or disclosure. The plan records every sample's frame, method and seed so that any review can be repeated by an outside auditor.

What this page is doingProbe, discovery and statistical samples are kept distinct.
6

Monitoring Between Audits

Audits are snapshots, so the plan adds monthly monitoring reports that need no record pulls. The first compares each clinician's distribution of office visit levels with the group's and with published specialty distributions, flagging anyone whose share of the highest level is far above peers. The second calculates, for each clinician, the share of injection visits billed with a separate visit and modifier 25. The third estimates billed hours. Fang and Gong (2017) showed that adding up the typical time of the services a physician bills can reveal physicians who bill for more hours than anyone could work, and that the excess pointed toward overbilling. At Sawtooth, any clinician whose implied hours exceed 60 a week in clinic will be reviewed. A flag is not a finding; it directs the next probe.

What this page is doingMonitoring uses data to direct audits.
7

Reporting and Independence

The committee sees results at each monthly meeting, and the managing partners see them twice a year, by clinician and by area, with accuracy rates, dollars at issue and actions taken. Clinicians receive their own results privately with the records reviewed, so they can learn from specific notes. Each year an outside coding firm will audit a random sample of 100 claims across the practice, both to check the internal coders' work and because an independent review is more persuasive to payers and regulators than a practice grading itself.

What this page is doingReporting flows to leaders and clinicians, with an external check.
8

Limits and Safeguards

The plan has limits that the committee should keep in view. Risk scores rest on judgment, so two reasonable people could rank therapy and brace billing differently, and an area that scores low may simply never have been examined. To guard against that, one low-ranked area will receive an unplanned probe each year. Internal coders also know the clinicians they review, which can soften findings, and that is one reason the outside audit matters. Finally, audit results can feel like accusations. Framing each result as accuracy feedback, sharing the specific notes and recognizing clinicians who improve will make it more likely that physicians treat the audits as help rather than surveillance.

What this page is doingThe paper names its own weaknesses and how they are handled.
9

Conclusion

This plan aims audit effort at the areas where Sawtooth's own evidence shows risk, uses the cheapest method that answers each question and escalates only when the data warrant it. It also creates a record that the practice looked, measured and acted, which is the best defense a practice can have when questions come from outside.

What this page is doingThe conclusion restates the plan's logic.
10

References

Fang, H., & Gong, Q. (2017). Detecting potential overbilling in Medicare reimbursement via hours worked. American Economic Review, 107(2), 562-591. https://doi.org/10.1257/aer.20160349

U.S. Department of Health and Human Services, Office of Inspector General. (2023). General compliance program guidance. https://oig.hhs.gov/compliance/general-compliance-program-guidance/

U.S. Department of Health and Human Services, Office of Inspector General. (n.d.). RAT-STATS statistical software. https://oig.hhs.gov/compliance/rat-stats/

What the HIM 600 Module 6 instructions ask for

The HIM 600 sixth module centers on auditing and monitoring, usually through a short paper of three to four pages in APA 7. You are asked to explain how an organization identifies and ranks its compliance risks, which kinds of audit it uses, how samples are selected and sized and how results are reported and acted on. Ground the plan in your organization or the course case, ideally in findings you already have. Distinguish audits, which review records, from monitoring, which tracks data continuously. Explain the difference between a probe sample and a statistically valid sample and when each is appropriate. Describe who sees results, how clinicians receive feedback and whether any review is done by someone outside the organization.

How this HIM 600 Module 6 auditing short paper example is built

Sawtooth Bone and Joint's committee scores eight billing areas for likelihood and impact, and Table 1 puts office visit levels and modifier 25 at 20 out of 25, with MRI referrals high on impact alone. Prospective review runs until a clinician reaches 90% accuracy twice in a row, and retrospective review measures progress and finds refunds. Ten-claim probes escalate to 30-claim discovery samples above a 10% error rate, and a statistically valid sample drawn with the federal RAT-STATS tool is used when an overpayment must be estimated. Monthly screens compare visit level distributions, modifier 25 rates and billed hours, following Fang and Gong. The HIM 600 paper ends with an annual outside audit of 100 claims.

Where the HIM 600 Module 6 rubric puts the points

In HIM 600, the auditing paper tends to be graded on a defensible method for ranking risks, appropriate choice between prospective and retrospective review, accurate explanation of sampling and its limits, use of data for ongoing monitoring, a clear reporting structure and attention to independence. Strong papers show the risk assessment itself, not just the conclusion, and they explain why a probe sample cannot support extrapolation. Graders reward escalation rules with numeric thresholds and monitoring measures that a practice could actually produce from its billing system. An external audit element and private, specific feedback to clinicians usually count in the writer's favor. Organized tables and correct APA 7 references complete the work.

HIM 600 Module 6 help: the mistakes that cost points

Auditing papers lose points when they say the organization will audit regularly without saying what, how many or how chosen, when they treat a small sample as proof of a total overpayment or when they never mention monitoring between audits. Others rank risks with no stated method. If your prompt focuses on hospital inpatient coding, a payer audit response, a specific contractor program or a different sampling rule, send it with your earlier milestone findings so the plan fits. A rough count of claims by type in your setting helps size samples sensibly. Our HIM 600 papers show the risk scoring, set numeric escalation thresholds and separate probes from statistical samples.

Get HIM 600 Module 6 written to your instructions

Send the HIM 600 Module 6 prompt, your earlier findings and anything you know about claim volumes in your setting. The paper will score risks with a visible method, pick review types for each, size probe and statistical samples correctly, add data monitoring and set out reporting, finished within one to two days, with no charge for your first. 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 600 papers and related MS Health Information Management samples

HIM 600 Module 6 questions, answered

Where can I find a free HIM 600 Module 6 Auditing Short Paper sample?

This page holds the full HIM 600 Module 6 paper: a risk-scored audit plan for an orthopedic group with probe and statistical samples, monitoring screens and reporting to the compliance committee.

What is the difference between auditing and monitoring?

Auditing reviews a sample of records against rules at a point in time. Monitoring tracks data continuously, such as visit level distributions or modifier rates, to spot changes and direct the next audit.

How many claims should a coding audit include?

It depends on the purpose. A probe of about ten claims per clinician can show whether a problem exists, while estimating a total overpayment requires a statistically valid random sample with a documented method.

What is RAT-STATS?

A free statistical program from the HHS Office of Inspector General used to draw random samples and calculate estimates when claims are reviewed and results must be extrapolated.

Should coding audits be prospective or retrospective?

Both have a role. Prospective review prevents errors before claims go out and gives fast feedback, while retrospective review measures accuracy over time and identifies overpayments to return.