C855 Nursing Informatics Capstone, catalog number NURS 6030, is the two-CU culminating course of the MSN Nursing Informatics specialty. It completes the practice experiences and delivers a system optimisation proposal addressing the Triple Aim, with planning for the final phase of the systems development life cycle. Two specific things are named there and both are scored: the Triple Aim framing and the closing SDLC phase. A proposal that ignores either has left an aspect empty.
What NURS 6030 is actually testing
Optimisation is a specific idea and it is not implementation. Implementation gets a system live. Optimisation improves a system that is already running, which is harder in one particular way: the users have habits, workarounds and opinions, and every change disturbs work that is currently functioning. Nobody thanks you for a change that makes Tuesday different.
The Triple Aim gives the proposal its evaluation frame. Better care experience, better population health and lower per capita cost. A serious optimisation proposal addresses all three, including where they conflict, because they routinely do. A change that improves the clinician experience by removing documentation may weaken the population health data that documentation supported, and a proposal that notices that tension is doing the work the framework was designed for.
The systems development life cycle supplies the project frame. Planning, analysis, design, implementation and then the final phase, which is maintenance, evaluation and continuous improvement. The catalog names the final phase specifically, so the proposal has to say what happens after go-live: who owns the system, how issues are triaged, how the configuration stays current, and when the optimisation itself gets re-evaluated.
The fourth element is that a capstone must be persuasive. The audience is a governance committee with a budget and a queue of competing requests, and the document has to be readable by someone who was not on the project.
Turning scored aspects into a section plan
Scoring detail is portal-resident, inside the Course of Study, and the public catalog carries none of it. Count the aspects before assembling anything, and expect a capstone rubric to carry more of them than a coursework rubric. Each is scored independently on a three-point scale and each needs a 2.
The word budget, worked. Where a capstone proposal runs to roughly 2,400 words across seven scored aspects, reserve 170 for an executive summary and 110 for a close, leaving 2,120 across seven aspects, or about 302 each. Then weight it. The Triple Aim aspect deserves 400 because it has to cover three dimensions and their conflicts. The final SDLC phase aspect deserves 360, since ownership, triage, currency and re-evaluation all live there. That leaves 1,360 for five aspects at about 272 each.
Write the executive summary last and place it first. The reader is deciding, not learning, and the ask has to be in the opening paragraph with its cost and its measure attached.
A structure that fits a system optimisation proposal
Task directions govern where they specify a format. Where they do not, this arrangement reads as a proposal a committee could act on.
| Section | What belongs in it | What earns the aspect |
|---|---|---|
| Executive summary | The problem, the optimisation, the cost, the measure, in one paragraph | The ask stated first rather than built toward |
| Current system state | What the system does now, its workarounds and its pain points | Workarounds documented, since they are the clearest evidence of a design problem |
| Problem evidence | Data from your practice experience, usage logs, incidents or user feedback | More than one source, each dated |
| Proposed optimisation | The specific configuration, workflow or interface change | Detailed enough that someone else could implement it |
| Triple Aim analysis | Experience, population health and cost, each addressed and any conflict named | All three dimensions plus the tension between them |
| Change and adoption | Who is affected, how they are prepared, how resistance is handled | Adoption planned rather than assumed |
| Final SDLC phase | Maintenance ownership, issue triage, configuration currency, re-evaluation schedule | Named ownership and a review date, since this is the aspect the catalog specifies |
| Evaluation plan | Baseline, target, interval, and the result that would count as failure | A design capable of showing the optimisation did not work |
| Risk | Clinical, technical and organisational risk with mitigation and a rollback | A rollback plan, because optimisation changes live systems |
| References | APA list of informatics literature, standards and any regulation | Frameworks cited to their sources with years |
Anonymise the organisation as you did in the field experience, and check again now that material from several sections sits together. Detail that was safe when scattered can identify a site when combined in one document.
Evidence craft in an optimisation capstone
A capstone aggregates evidence from a placement and from coursework, and aggregation introduces its own errors.
- Re-verify everything carried forward from C854 and the earlier specialty courses. Standards get versioned, regulations get amended, and a figure that was current a term ago may not be.
- Cite the Triple Aim and the systems development life cycle to their sources rather than treating them as common knowledge. Both have identifiable origins.
- Give cost real content: licence or configuration effort, analyst hours, training time, and the productivity dip that follows any change to a live system.
- Use system data where you can. Usage logs, override rates and time stamps are stronger evidence than user opinion, and they are usually available.
- Label opinion as opinion. Feedback from clinicians is legitimate evidence and it is not the same as measurement.
- Quote sparingly, and check reuse rules for material from earlier courses. WGU runs submissions through a similarity check and a capstone carries more reuse risk than any single assignment.
The habit that most strengthens an optimisation proposal is documenting the workarounds users have already invented. A nurse who keeps a paper list because the system view is unusable has already told you what the design should have done. Workarounds are free requirements gathering, and quoting them is the most persuasive evidence a proposal of this kind can carry.
What separates Competent from a submission sent back
Aspects score on their own, and the Triple Aim and final-phase sections are where returns concentrate.
- All three Triple Aim dimensions are addressed and at least one conflict between them is named.
- The final SDLC phase has named ownership, a triage route and a re-evaluation date.
- Cost includes effort and the temporary productivity loss, not only licences.
- The evaluation plan has a baseline and a defined failure result.
- The document stands alone without your earlier submissions.
WGU performance assessment work can be revised and resubmitted with no grade penalty, so a return costs schedule rather than standing. At the end of a specialty that schedule matters more than usual, since this is often the final course before completion. Terms run six months at a flat rate, and a capstone that goes several rounds can push a completion date into a term you had not planned to open.
Five mistakes that cost time in C855
- Proposing implementation rather than optimisation. The system is already live, and the argument is about improving it without disturbing what works.
- Naming the Triple Aim without using it. Three dimensions, each addressed, with the conflicts stated.
- Stopping at go-live. The catalog names the final SDLC phase, so ownership, triage and re-evaluation are required rather than optional.
- Costing at zero. Analyst hours, training time and the dip in productivity after any change are all real costs.
- No rollback plan. Changes to live clinical systems occasionally have to be reversed, and a proposal without a reversal path reads as untested.
How support works on this course
C855 is an integration and persuasion problem more than a research one. Send the rubric out of your Course of Study with the task directions and the work starts by auditing what carries forward from C854: which evidence still stands, which sources need re-verifying, which claims shift meaning in a proposal context. From there you get a document structured for a decision-making reader, a Triple Aim analysis that handles the conflicts rather than the headline, a final-phase section with real ownership, a costed proposal and an evaluation plan that could show failure.
The boundaries hold. We do not complete field or practice hours, contact mentors, sites or vendors, sign placement paperwork or fill in hour logs. Objective assessments at WGU are proctored, so we prepare only, never sit them, and never ask for portal credentials.
Questions students ask about C855
Is C855 the same course as NURS 6030?
Does the capstone have to continue the C854 project?
What if my proposal will never be implemented?
Assembling the C855 capstone?
Send your Course of Study rubric and the task directions. We audit what carries forward, then build a standalone optimisation proposal with a real cost and a real evaluation plan.
Where C855 sits in WGU's programs
The July 2026 catalog places this code in 2 current WGU programs. 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.