D912 is Healthcare Quality, carried at WGU as MHA 6913 and worth three competency units. The catalog frames it as evaluating, measuring and enhancing the quality of healthcare services, and those three verbs are effectively the assignment. Graduate quality work is not an essay about why quality matters. It is a project document: a problem defined by a measure, a method chosen for a reason, an intervention aimed at a cause, and a measurement plan that would show whether anything actually improved.
Structure, process, outcome, and picking the right one
Quality measures fall into three types and students routinely choose the wrong one for the problem they have. Structure measures describe what an organization has: staffing levels, equipment, certification, availability of a service. Process measures describe what is done: the share of eligible patients who received a screening, medications reconciled at discharge, hand hygiene observations. Outcome measures describe what happened to patients: infection rates, readmissions, mortality, function, experience of care.
The practical rule for a coursework project is that process measures move fastest and are easiest to attribute. If your project is a three month improvement effort, an outcome measure may not shift at all within your timeframe, and building an evaluation around one guarantees an inconclusive result. Choosing a process measure closely linked to a known outcome, and saying explicitly why you chose it, is a mature move that evaluators recognize.
Whatever you choose, write the measure as an operational definition: numerator, denominator, inclusion rules, exclusion rules and data source. Two competent people should be able to compute your measure from the same records and get the same number. If they cannot, the measurement aspect will not score well no matter how good the rest of the plan is.
Building the project document from the aspects
Your rubric lives in the Course of Study. In this subject the aspects usually map onto the phases of an improvement project, which is convenient because it means the aspect list is also a work plan. Sort them by phase before you draft, and check whether an aspect wants the plan or wants a rationale for the plan, because those are different paragraphs.
The word budget, worked. Take a 2,200 word project document with eleven scored aspects. Reserve 150 for a problem statement and 100 for a closing, leaving 1,950 across eleven aspects, or 177 each at a flat split. Then move money toward measurement and analysis. The operational definition and the measurement plan should have 280 each, because they are the aspects that determine whether the whole project is credible. Root cause analysis takes 280. Intervention design takes 250. That leaves about 100 apiece for the remaining descriptive aspects, which is one tight paragraph each and is enough at graduate level. If you find yourself with 400 words on the importance of quality in healthcare, that money came out of the measurement section.
Draft the measurement plan before the intervention. It is the section that stops you from designing something whose effect nobody could detect.
A quality improvement charter that scores
Where the directions supply a template, that template rules. Where they do not, this charter format covers the material most rubrics in this subject ask for, and it reads the way a quality committee expects.
| Element | Content | The test |
|---|---|---|
| Problem statement | The gap, in a measure, in a setting, over a period | Does it contain a current number and a target |
| Why it matters | Harm, cost or experience consequence of the gap | Is the consequence quantified or at least sourced |
| Measure definition | Numerator, denominator, exclusions, source, frequency | Could two people compute it identically |
| Baseline | Current performance across enough periods to see variation | Is one data point being treated as a baseline |
| Cause analysis | Contributing causes, examined systematically and ranked | Does the top cause connect to the intervention |
| Intervention | What changes, for whom, starting when | Is it a change in work, or a request to try harder |
| Test cycles | Small scale trial, review point, adjustment | Is there a plan to stop if it is not working |
| Sustainment | Ownership, monitoring cadence, escalation threshold | Who watches this in six months |
The intervention row hides the most common weakness in graduate quality writing. Education and reminders are the default proposal and the weakest one, because they rely on individual effort. Interventions that change the system, such as making the safer action the default, removing a step, or building the check into an existing workflow, are the ones improvement science supports and the ones a reviewer will take seriously.
Evidence craft in improvement work
Quality writing has its own evidence habits, and adopting them is the fastest way to sound like a professional rather than a student.
- Show variation over time rather than two points. A run of at least eight to twelve periods lets you tell a real shift from normal fluctuation.
- Use a run chart or control chart where the data allows, and describe the pattern in words as well as showing it.
- Attribute cause claims to a method. If you used a cause and effect diagram or a five whys exercise, say so and show what it produced.
- Cite published improvement literature for intervention effectiveness, and national or professional bodies for measure specifications.
- Handle safety data carefully. Incident reports are for learning and are often legally protected, so write about aggregate patterns rather than about individual events.
- Use APA for measure specifications and guidance documents, and cite at the claim.
One habit distinguishes strong submissions: naming the balancing measure. Every improvement can create a problem elsewhere, and a project that shortens a process while watching whether accuracy falls demonstrates the systems thinking the course is teaching.
What separates Competent from a submission sent back
Returns cluster around three things. The measure is not operationally defined, so nothing downstream can be evaluated. The intervention does not address the cause that the analysis identified, which is usually visible in a single paragraph. Or the evaluation plan has no threshold, so there is no stated point at which the project would be judged successful or abandoned.
Work that passes on the first read is tight. One measure, defined completely. A baseline with enough periods to show variation. A ranked set of causes with a method attached. An intervention that changes work rather than exhorting people. A test cycle with a review date. A balancing measure. And a named owner for monitoring after the project ends.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return costs calendar time rather than score. In this subject the rebuild is usually the measurement section, which sits upstream of everything else, so time spent on the operational definition at the start is the highest return hour in the whole course.
Where a proctored objective assessment appears with this course in your plan, we prepare only. We drill method vocabulary and measure types, work practice items and give a straight readiness call. We do not sit or assist during any proctored assessment and we never ask for portal credentials.
Six mistakes that cost time in D912
- An outcome measure on a short timeline. Pick a process measure linked to the outcome and explain the link.
- A baseline of one number. Without variation you cannot tell improvement from an ordinary good month.
- Causes listed but not ranked. If everything contributes equally, the intervention has no target.
- Education as the intervention. Training supports a change. It is rarely the change itself.
- No balancing measure. Speeding a process usually costs something. Say what you are watching.
- No stopping rule. A plan that cannot fail cannot be evaluated, and the evaluation aspect will say so.
How we work this course with you
Send the task directions and your rubric and the first thing back is the measure, written as a full operational definition with numerator, denominator, exclusions and source, because that single paragraph determines whether the rest of the project holds together. Then a charter skeleton mapped to your scored aspects, word budgets attached, a cause analysis structure you can complete for your setting, and a review pass that checks the intervention against the top ranked cause. We also look for the quiet inconsistency that appears in most first drafts, where the problem statement names one measure and the evaluation section reports another, because that is the single most common reason a well written improvement project comes back for a second look.
Questions D912 students ask
What if I cannot get real baseline data?
Which improvement method should I choose?
How do I write about patient safety events without breaching confidentiality?
Building the D912 improvement project?
Send the MHA 6913 directions. You get an operational measure definition and a charter skeleton back.
Where D912 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.