C815 is Quality and Performance Management and Methods, listed at WGU as HIM 4511 and worth four competency units. The catalog covers quality initiatives in healthcare including human resource management, employee performance and patient safety, all from the health information perspective. That combination is unusual and it is the point. A quality problem in a health information department is almost always partly a process problem and partly a people problem, and a submission that addresses only one of the two leaves aspects unanswered.
Process problem or performance problem
Suppose coding accuracy in a department sits at 88 percent against a target of 95. Two very different investigations follow. If accuracy is uniformly low across all coders, the cause is systemic: guidelines misunderstood, documentation poor, a template producing ambiguous notes, an encoder configured badly, or unrealistic productivity targets forcing speed over care. If accuracy is high for most and low for two individuals, the cause is individual: training, experience, aptitude or engagement.
Diagnosing which one you have is the first analytic move, and it is usually visible from the data if you disaggregate. Aggregate rates hide the pattern. Rates by person, by service line, by shift or by record type reveal it. Any submission that recommends a fix without first showing that it disaggregated the data is guessing, and evaluators can tell.
The consequence for your writing is that the response has to match the cause. A systemic problem calls for a process change, a documentation improvement effort or a target adjustment. An individual problem calls for a performance management approach: clear expectations, measurement, feedback, coaching, a documented improvement plan, and a defined path if it does not improve. Applying the wrong response is both ineffective in practice and a scoring failure on the page.
Building the deliverable from the aspects
Your scored aspects are in the Course of Study rather than the catalog, and in this course they usually cover a quality method, a measurement approach, a human resource dimension and a safety dimension. Sort them by that split before drafting so you can see which one you are about to under serve, which is almost always the human resource one.
The word budget, worked. Take a 2,100 word submission with ten scored aspects. Reserve 130 for a paragraph establishing the department, its measured performance and the target, leaving 1,970, or 197 per aspect flat. Then weight by difficulty of evidence. The method and measurement aspects need 280 each, because both require you to justify a choice rather than name one. Human resource aspects need 240, since they must include a specific sequence rather than a principle. Safety aspects need 240 for the same reason. Descriptive aspects drop to 130. Add it up before drafting; in this course the arithmetic usually reveals that there is no room for the general paragraph about the importance of quality that students write first.
Write the human resource sections early. They are the ones that get squeezed, and they are also the ones where specificity is hardest to produce under time pressure.
A performance improvement plan for a department
Where a template is supplied, follow it. Where it is not, this arrangement holds both halves of the course and produces a document that reads like something a real department would use.
| Component | What it must specify | The evidence behind it |
|---|---|---|
| Performance gap | Current measure against target, over a stated period | Disaggregated data, not an aggregate rate |
| Pattern analysis | Whether the gap is systemic, individual or both | Breakdown by person, service line, shift or record type |
| Method selected | The improvement approach and why it fits this problem | A published method, applied by its own steps |
| Process change | What changes in the workflow, for whom, when | Before and after description of the affected steps |
| Expectations | Written standard for performance, communicated and dated | The standard document itself, and how it was shared |
| Feedback loop | How individuals see their own results and how often | Cadence, format and who delivers it |
| Support | Training, mentoring, tools, workload adjustment | What was offered, when, and for how long |
| Safety linkage | How the quality gap affects patient safety or data integrity | The specific downstream harm or risk, named |
| Review | Re-measurement date and the threshold for further action | A date and a number, both written down |
The feedback loop row is worth dwelling on. In practice most performance problems in production oriented departments improve substantially once individuals can see their own measured results regularly, and the intervention costs almost nothing. Saying that in your plan, and specifying the cadence, is a concrete recommendation rather than a general one.
Evidence craft when the subject includes people
Writing about employee performance carries responsibilities that writing about processes does not.
- Describe roles, never individuals. Even in a fictional scenario, write about a coder rather than a named person, and avoid details that would identify someone in a real workplace.
- Keep the process of performance management factual and documented: expectation, measurement, feedback, support, review, and escalation only after those.
- Note where human resources involvement or policy review is required, because discipline, accommodation and classification are all constrained areas.
- Use published quality methods and cite them, applying their own steps as your structure rather than naming them and moving on.
- Express safety linkage concretely: a coding error that misstates a diagnosis affects the record, the registry, the payment and potentially future care decisions.
- Cite in APA at the claim, including professional association guidance on productivity and accuracy standards.
One sentence noticeably strengthens this kind of writing: acknowledge the tension between productivity targets and accuracy targets. Every production department lives with it, and a plan that pretends both can be maximized at once reads as inexperienced. Naming the trade off and saying how you would balance it is what a manager actually does.
What separates Competent from a submission sent back
Three patterns send this work back. The aggregate rate with no breakdown, which makes the diagnosis unsupported. The individual performance response applied to a systemic problem, usually visible as a recommendation to retrain everyone. And the safety dimension omitted entirely, because the student treated the task as a productivity exercise.
Work that passes on the first read shows disaggregated data, states whether the problem is systemic or individual and why, matches the response to that diagnosis, includes a written expectation and a feedback cadence, names the safety or data integrity consequence, and sets a re-measurement date with a threshold. It also acknowledges what the plan asks of staff, which is the mark of somebody who has thought about whether it would actually work.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return costs term time rather than a score. In this course the most common rebuild is adding the human resource specificity that was crowded out, which is why writing those sections first is the practical advice.
Where a proctored objective assessment accompanies this course in your plan, our support is preparation only. We drill methods and measures, work practice items and give 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 C815
- Reasoning from an aggregate. Break the data down before diagnosing, because the pattern determines the entire response.
- Retraining as the universal fix. If the process is the problem, training makes people better at a broken process.
- Performance management with no written expectation. Feedback against an unstated standard is not manageable or defensible.
- Ignoring the safety half. The catalog names patient safety explicitly, and data errors have clinical consequences.
- Productivity and accuracy both maximized. Name the trade off and say how you balance it.
- No re-measurement. A plan without a review date and a threshold cannot be evaluated, which is usually its own aspect.
How we work this course with you
Send the task directions and your rubric and you get a disaggregation plan that shows what breakdowns would diagnose your problem, a method selection with the reasoning already written, a performance improvement plan skeleton covering expectation, feedback, support and review, and a section plan with word counts that protects the human resource and safety aspects. On review we check that the response you recommend matches the diagnosis you made, which is the mismatch that sends most otherwise complete submissions back. Where a task involves both a process fix and an individual performance issue, we help you keep them in separate sections so an evaluator can score each one without having to untangle which recommendation belongs to which problem.
Questions C815 students ask
Can I write about disciplining an employee?
What quality measures work for a health information department?
How do I connect a data quality issue to patient safety?
Writing the C815 improvement plan?
Send the HIM 4511 directions. You get a disaggregation plan and a performance plan skeleton back.
Where C815 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.