C807 is Healthcare Compliance, listed at WGU as HIM 3215 and worth three competency units. The catalog places it squarely in the coding professional's world: compliance plans, noncompliance issues, and managing internal and external audits. That framing matters, because it tells you the perspective every answer should take. You are not writing as a lawyer or as an executive. You are writing as the person who has to run a coding operation that can withstand review, catch its own errors before somebody else does, and prove what it did.
Error, pattern, abuse, fraud
The distinction that carries this course is between an honest mistake and something worse, and it is a spectrum rather than a switch. A single miscoded record is an error. The same error repeated across a hundred records is a pattern, which suggests a process or training problem. Billing that consistently produces higher payment without documentation support is abuse. Knowingly submitting claims for services not provided or not documented is fraud, and intent is what separates it from everything upstream.
Students weaken their answers by jumping to the strongest word. Writing that a coding discrepancy constitutes fraud, without evidence of intent, is both inaccurate and professionally reckless. The correct answer usually describes what was found, what pattern it forms, what could explain it innocently, what would need to be true for it to be deliberate, and what the organization does next while that is determined.
The reverse mistake matters too. A pattern discovered and then not acted on is a serious problem regardless of how it started, because the obligation to investigate and to return overpayments does not depend on whether the original error was innocent. Compliance writing that describes a finding and stops has left the most important half unsaid.
Turning the aspects into a compliance deliverable
Your scored aspects live in the Course of Study, not the catalog, and in this subject they usually split between building something, such as a plan or an audit protocol, and responding to something, such as a finding or a scenario. Sort them before drafting, because the two call for different formats: a plan is structured and enumerated, a response is analytic and sequential.
The word budget, worked. Take a 1,700 word deliverable with eight scored aspects. Reserve 110 for a paragraph establishing the organization and the coding operation, leaving 1,590, or about 198 per aspect flat. Plan aspects can run lean at 150 because they are enumerated: element, what it contains, who owns it, what proves it. Response aspects need 280, since each one must state the finding, quantify it, explain the possible causes, and describe the corrective action. Four plan aspects at 150 and four response aspects at 280 comes to 1,720, so trim the framing paragraph and one plan aspect slightly rather than shortening a response.
Draft the corrective action content before the plan content. Corrective action is specific and it will remind you which plan elements actually matter, whereas plans drafted first tend to list every element with equal weight.
A coding audit protocol that stands up
Where a template is supplied, use it. Where it is not, these are the decisions an audit protocol has to make explicit, and each one tends to correspond to something scored.
| Decision | What you specify | Why a reviewer asks |
|---|---|---|
| Scope | Which service lines, which coders, which period | An audit with no boundary cannot be repeated |
| Sample | Size, selection method, random or focused, and why | Focused samples find problems, random samples estimate rates |
| Standard | The coding guideline, edition and effective date used | Guidelines change, and results depend on which version applied |
| Reviewer | Credential, independence from the work being reviewed | Self review is not an audit |
| Error definition | What counts as an error, and how disagreements resolve | Without it, two reviewers produce two different rates |
| Findings | Rate, financial effect, and the pattern behind them | A list of individual errors is data, not a finding |
| Corrective action | Education, process change, rebilling, refund, escalation | The aspect that separates a report from a program |
| Follow up | Re-audit date, threshold for further action | Proves the correction worked rather than assuming it |
The error definition row is the one that rescues student work. Coding disputes are common and reasonable people disagree, so an audit that defines what an error is and how disagreements are resolved is immediately more credible than one that reports a rate as though it were objective.
Evidence craft in compliance work
Compliance is an evidence discipline, and writing it well is mostly a matter of being specific about proof.
- Pair every element of a compliance plan with an artifact: written standard, training record, audit report, disclosure log, minutes of a committee.
- Cite official guidance for coding rules and enforcement expectations, and name the version or year, since both change.
- Quantify findings. An error rate of 9 percent on a sample of 60 records with a stated financial effect is a finding. Several errors were noted is not.
- Describe monitoring separately from auditing. Monitoring is ongoing and internal, auditing is periodic and independent, and rubrics often score them separately.
- Address the nonretaliation and reporting path explicitly. A program in which staff cannot safely report a concern is a program that will not detect anything.
- Use APA and cite at the claim, including guidance documents and manuals.
One sentence lifts an audit response substantially: naming what the organization will do about payments already received. Repayment obligations attach to identified overpayments, and a response that quantifies the exposure and describes the refund or disclosure route shows you understand what compliance is for.
What separates Competent from a submission sent back
Three returns recur. The plan with no artifacts, where every element is described and nothing would prove it operates. The audit with no method, where a rate is reported without a sample, a standard or an error definition. And the response that ends at education, which is the default corrective action and rarely sufficient on its own when the cause was a system or a policy.
Work that passes on the first read reads like something an organization would file. Scope and sample stated. Standard named with its version. Error definition given. Findings quantified with a financial effect. Corrective action matched to cause, including process change where education alone would not fix it. Follow up scheduled. And a clear statement of when a matter moves beyond the coding department to compliance leadership or counsel.
A returned performance assessment can be revised and resubmitted at WGU with no grade penalty, so what a return actually costs is a slot in the evaluator queue. In this course the rebuild is usually the method section, which is short to write and easy to omit under time pressure.
Where a proctored objective assessment accompanies this course, our involvement is preparation only: study plan, drilled distinctions, practice items and an honest readiness call. We never sit or assist during a proctored assessment and never ask for portal credentials.
Six mistakes that cost time in C807
- Calling an error fraud. Intent is the dividing line, and asserting it without evidence is both wrong and unprofessional.
- Audits with no sample method. Random and focused samples answer different questions, and the choice must be stated.
- Education as the only corrective action. If the cause was a template, an edit or a policy, training will not fix it.
- Findings without financial effect. Quantifying exposure is what turns a finding into something leadership acts on.
- Silence on repayment. Identified overpayments carry obligations, and a response that ignores them is incomplete.
- No follow up audit. A correction with no re-audit is an assumption, and the assumption is usually the thing being scored.
How we work this course with you
Send the task directions and your rubric and you get an audit protocol skeleton with every decision named, a plan template with an artifact column so no element is left unproven, a corrective action framework matched to cause type, and a section plan with word counts. On review we check for the three details that most often decide the score: sample method, error definition and a corrective action that fits the cause you identified. Where a task also asks you to write as the compliance voice inside a coding department, we help you set the tone, which is neither accusatory nor apologetic but simply factual about what was found and what happens next.
Questions C807 students ask
What sample size should a coding audit use?
How do I write about a compliance problem I found at work?
Who should the compliance officer report to?
Writing the C807 plan or audit?
Send the HIM 3215 directions. You get an audit protocol skeleton and a corrective action framework back.
Where C807 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.