C854 Nursing Informatics Field Experience, catalog number NURS 6020, is the four-CU supervised practice course in the MSN Nursing Informatics specialty, where you work in the informatics nurse role applying methods and solutions that support clinical decision-making. At four CUs it is the largest course in the specialty. The practice hours, the site and the mentor relationship are entirely yours, and the boundary on that is stated in full below.
What NURS 6020 is actually testing
The phrase to hold onto is clinical decision-making. This is not a general technology placement. The work is expected to touch how a clinician decides something: what an alert fires on, what a report shows a manager, how an order set constrains a choice, what a dashboard makes visible that was invisible.
Three competencies get scored. The first is working as an informatics nurse rather than as a clinician who is interested in computers. That means gathering requirements from people who cannot articulate them, translating clinical language into system terms and back, and sitting between two groups who each think the other is being difficult.
The second is applying a method rather than improvising. Informatics has structured approaches to workflow analysis, requirements gathering, usability testing, implementation and evaluation, and a field experience is where you use one deliberately and can say which one you used and why.
The third is evidencing the effect on decision-making. Not that a change was made, but that a decision now happens differently: a nurse sees something at the moment she needs it, a prescriber is stopped from an unsafe combination, a manager notices a trend four weeks earlier than before.
What sinks field experience submissions is scope. Four CUs is a substantial amount of practice time and a genuinely small amount of project time, and students routinely start something that could not finish inside the placement. A narrow piece completed, evaluated and documented scores far better than an ambitious project abandoned at the analysis stage.
Turning scored aspects into a section plan
Scoring detail for a WGU course sits in the portal Course of Study, never in the public catalog. Count the scored aspects before writing, because field courses usually carry several narrow ones rather than a few wide ones. Every aspect is judged separately on a three-point scale, and a 2 in each is what passes the task.
The word budget, worked. Where a written component runs to about 2,000 words across six scored aspects, reserve 120 for an opening naming the site, the mentor role and the project, and 100 for the close, leaving 1,780, or about 296 per aspect. Then weight it. The method aspect deserves 380, since it has to name the approach, justify it and show it applied. The evaluation aspect deserves 340, because measuring an effect on decision-making needs a before and an after. That leaves 1,060 for four aspects at about 265 each.
Fix the project scope in the first fortnight, in writing, with your mentor. A scope agreed early and narrowed deliberately is the single strongest predictor of a field experience that finishes on time.
A structure that fits an informatics practice record
Program forms and task directions govern the deliverables. Where the internal shape is yours, this arrangement produces a defensible record.
| Element | What belongs in it | What makes it defensible |
|---|---|---|
| Site and role | Type of organisation, the informatics function, your position in it | Your own scope of action described honestly, including its limits |
| Project scope | What you set out to do and what you explicitly excluded | An exclusion list, since it shows the scope was managed |
| Method selected | The informatics approach used, named and justified | A named method rather than a description of activity |
| Stakeholder work | Who you gathered requirements from and how you resolved conflicts | Conflict resolution shown, since it is the core of the role |
| Decision-support link | The specific clinical decision the work affects | One decision named, traced from data to display to action |
| Implementation activity | What was built, configured, tested or trained | Your contribution separated from the team's |
| Evaluation | Before and after measures, including any unintended effect | A measure with a baseline; opinion after the fact is not evaluation |
| Reflection | What the role demanded that you did not expect | Specific competency gaps identified with actions attached |
| References | APA list of methods sources, standards and any regulation applied | Methods cited to informatics literature |
Separate your contribution from the team's plainly. Informatics work is collaborative and evaluators know it, so writing that overstates individual authorship is both inaccurate and easy to detect.
Evidence craft in an informatics placement
A field experience generates real organisational material, which brings obligations a coursework paper does not.
- Anonymise the organisation, the vendor and every individual unless the directions and the site permit naming. Screenshots of live systems are almost never appropriate in a submission.
- Never move patient data anywhere. Where you need to illustrate a screen or a report, use fabricated example values and say that is what they are.
- Separate what you were told from what you measured. A clinician saying the report is useful is different from usage data showing it is opened.
- Cite the method you used to its source. Workflow analysis, requirements elicitation and usability testing approaches all have documented origins.
- Give every evaluation number a baseline and a period. Improvement claims without a before are unevaluable.
- Quote sparingly. WGU runs submissions through a similarity check, and internal documentation should be described rather than reproduced.
One further habit protects you in a way students rarely anticipate. Write down what the system did before you touched it, in detail, on the day you arrive. Screen counts, click counts, the number of fields on the form, how long a task takes when you time it yourself. Organisations rarely have that baseline recorded, and once a change goes in nobody can reconstruct it. Half an hour of measurement in the first week is what makes the evaluation section of both this course and the capstone possible.
The practice that most improves an informatics field record is a dated decision log. What was decided, by whom, and what was rejected. Projects change shape as they meet reality, and a log lets you write an honest account of why the work ended up different from the plan. Without one, the final submission usually pretends the plan was followed.
What separates Competent from a submission sent back
Aspects score independently, and evaluation is the aspect most often thin in a field submission.
- The project scope is stated with explicit exclusions.
- A named informatics method is used and justified.
- One clinical decision is traced from data through display to action.
- Evaluation has a baseline, a period and at least one unintended effect considered.
- Your own contribution is separated from the team's.
WGU performance assessment work can be revised and resubmitted with no grade penalty, so a return costs time. In a four-CU field course that cost is heavier than usual, because the placement has a calendar and a mentor whose availability is finite. Terms run six months at a flat rate, and C855 sits directly behind this course, so a delay here usually moves the capstone as well.
Six mistakes that cost time in C854
- Scoping a project the placement cannot finish. The most common and most damaging error in this course.
- Describing activity instead of method. Attending meetings is activity. A named analysis approach applied deliberately is method.
- Losing the decision-support thread. The catalog names clinical decision-making, so the work has to connect to a decision.
- No baseline. Without a before measurement, nothing you did can be shown to have worked.
- Ignoring unintended effects. Every alert added is an interruption created, and a mature evaluation says so.
- Reconstructing the project narrative at the end. Keep the decision log from week one or the account will smooth over everything interesting.
How support works on this course
The boundary comes first. We do not complete field or practice hours. We do not contact mentors, placement sites, vendors or organisational staff. We do not sign, prepare or submit placement paperwork. We do not fill in, edit or reconstruct hour logs. The placement and the record belong to you.
Around that, the written and planning work benefits from structure. Send the rubric out of your Course of Study with the task directions and you get scope pressure-tested against the time available, a method selected and justified from the informatics literature, a baseline measurement designed before the work starts, a decision-support thread that stays visible, and review of anonymised drafts for organisational and patient privacy risk.
Objective assessments at WGU are proctored, so we prepare only, never sit them, and never ask for portal credentials.
Questions students ask about C854
Is C854 the same course as NURS 6020?
Can you help me find an informatics placement or mentor?
Can the field experience be at my own employer?
Scoping the C854 field experience?
Send your Course of Study rubric and the task directions. We pressure-test the scope, pick the method and design the baseline before the work starts. Hours, mentors and logs stay entirely yours.
Where C854 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.