WGU C855: Nursing Informatics Capstone

What C855 actually is: the finish line of your MSN in Nursing Informatics

WGU's C855, Nursing Informatics Capstone, is the final course in the Master of Science in Nursing, Nursing Informatics specialty (offered in both the RN-to-MSN and BSN-to-MSN tracks). It is not a class of lectures and quizzes. It is a supervised project in which you analyze a real health information system, identify a meaningful improvement, and build a formal system optimization proposal grounded in the Institute for Healthcare Improvement's Triple Aim: better patient experience, better population health, and lower cost of care. You also complete a required block of clinical practice experience (CPE) hours working alongside a WGU-approved industry professional and other stakeholders in a healthcare setting.

Direct answer: You pass C855 by starting your practice-experience hours and stakeholder conversations early, then writing your optimization proposal strictly to the task rubric one section at a time. There is no test to cram for; the "exam" is a well-documented, evaluator-ready paper, so treat every aspect of the rubric as a checklist item you must explicitly satisfy.

Nearly everyone who reaches C855 has already finished the MSN core and specialty courses, because those are prerequisites. That matters: the capstone is designed to integrate what you learned across the whole program rather than introduce new theory. If you carried an idea forward from the Nursing Informatics Field Experience course (C854), C855 is where you complete and submit it.

What the capstone asks you to produce

The specific tasks and section labels are set by your current course of study, but the work consistently centers on these areas:

• Needs assessment: analyzing an existing health information system and justifying why a particular optimization is warranted.
• Triple Aim alignment: tying your proposed change to measurable improvements in care experience, population health outcomes, and cost.
• Stakeholder engagement: identifying who is affected, gathering input, and documenting how you collaborated with your practice-experience professional and organizational stakeholders.
• Project planning: outlining scope, resources, timeline, and a systems development or implementation approach for the optimization.
• Evaluation strategy: defining key performance indicators and how the organization would measure whether the change succeeded.
• Clinical practice experience: logging the required CPE hours accurately and completing the associated evidence.

How hard is it, and how long does it take?

C855 is assessed entirely by performance assessment (PA). There is no objective, proctored exam, no multiple-choice questions, and no passing percentage to hit. Instead, an evaluator reviews your submitted deliverables against a rubric and returns them either as "Competent" or with revision requests.

Many students report that the intellectual difficulty is moderate for anyone who has done well in the earlier informatics courses. The real challenge tends to be logistical: scheduling and completing practice-experience hours, coordinating with a busy professional and stakeholders, and writing precisely enough to satisfy every rubric line so the paper passes without multiple return trips. Because the CPE component and stakeholder input cannot be rushed, students commonly describe pacing themselves across a good part of a term rather than knocking it out in a weekend. Plan for steady weekly effort, and expect at least one round of evaluator feedback to be normal, not a failure.

A practical plan to move through C855 without stalling

Because this is a project, not a memorization task, your study tactics look different from an objective-assessment course. Adapt the proven learning techniques to the capstone's realities:

• Front-load the logistics. The single biggest time sink is waiting on other people. Confirm your practice-experience professional, schedule stakeholder conversations, and begin logging CPE hours in week one. Everything else depends on this.
• Reverse-engineer the rubric. Before writing a word, copy each aspect of the task into your own document as a heading. This is a form of retrieval practice for project work: you are forcing yourself to recall and address every requirement rather than writing an essay and hoping it covers them.
• Write in small, spaced sittings. Draft one rubric section, set it aside, and return with fresh eyes a day later. Spacing your writing sessions catches gaps and vague claims that a single marathon draft hides.
• Self-test against the evaluator's lens. After each section, ask: "Would a reviewer who has never met me see the requirement clearly satisfied here?" If you are inferring or implying, make it explicit.
• Anchor every recommendation in evidence. Tie your optimization to the Triple Aim and to credible sources or organizational data. Unsupported claims are the most common reason sections come back.
• Use your course instructor and cohort deliberately. WGU course instructors can review your topic and drafts before submission. A quick topic check early prevents weeks of work on a proposal that is out of scope.

If the informatics fundamentals feel shaky as you write, it is worth revisiting the groundwork from earlier in the program, such as C790 Foundations in Nursing Informatics and the broader health-information context in C802 Foundations in Healthcare Information Management.

Mistakes that send C855 proposals back for revision

• Choosing a topic that is too big. "Fix our whole EHR" is unmanageable. A tightly scoped optimization you can plan and measure passes far more smoothly.
• Treating the Triple Aim as decoration. Naming it is not enough. Evaluators look for a concrete link between your change and each Triple Aim dimension.
• Vague or unmeasurable success metrics. If your KPIs cannot be quantified or attributed to the change, your evaluation section is incomplete.
• Weak stakeholder documentation. Saying you "consulted stakeholders" without specifics rarely satisfies the rubric; describe who, when, and what changed as a result.
• Starting the paper before the hours. Writing without having done the practice experience produces a proposal that reads as theoretical and often has to be reworked.
• Skimming the task instructions. The rubric is the grade. Answering the question you assumed rather than the one asked is the most avoidable error here.

C855 Readiness Checklist

Before you submit, confirm you can honestly say yes to each of these:

• Can you state your chosen optimization in one clear sentence, with a scope you can actually plan?
• Can you explain why the current system needs this change, using evidence from your needs assessment?
• Can you connect your proposal to each part of the Triple Aim specifically, not just in name?
• Can you name your stakeholders and describe how their input shaped the proposal?
• Can you lay out a realistic plan covering scope, resources, and timeline?
• Can you define measurable KPIs and explain how the organization would evaluate results?
• Have you logged and documented all required CPE hours accurately?
• Have you mapped every rubric aspect to a clearly labeled section in your paper?
• Has your course instructor reviewed your topic, and ideally a draft, before submission?

C855 FAQ

Is C855 an OA or a PA?

C855 is assessed entirely as a performance assessment. You submit a system optimization proposal and the associated practice-experience evidence; there is no objective, proctored exam and no multiple-choice test.

How long does C855 usually take?

It varies with your schedule and how quickly you can arrange practice-experience hours and stakeholder input. Many students report pacing it across a meaningful portion of a term rather than finishing in a few days, largely because the CPE and collaboration steps depend on other people's availability.

Do I need to find my own project site and mentor?

You work with a WGU-approved industry professional and stakeholders during the clinical practice experience. Coordinate this early with your program and course instructor, since it is the step most likely to create delays if left late.

What is the Triple Aim, and why does it matter here?

The Triple Aim is the Institute for Healthcare Improvement's framework for improving the patient care experience, improving population health, and reducing per-capita cost. Your optimization proposal must show how the change advances these goals, so it is central to the whole assessment rather than a side note.

How many attempts do I get if my submission comes back?

An evaluator can return your work with specific revision requests, and you address them and resubmit. Getting feedback is common and is part of the process, so treat a return as a targeted to-do list rather than a setback.

How is C855 different from the field experience course before it?

The Nursing Informatics Field Experience course (C854) is where many students begin shaping the optimization idea. C855 is where you complete the practice experience and finalize the full proposal, integrating competencies from across your MSN program into one evaluator-ready deliverable.

For related nursing groundwork, see D439 Foundations of Nursing, browse more programs in the Leavitt School of Health hub, or explore the full library of WGU course guides. You can also confirm current program details on the official WGU Nursing Informatics program page.