NR-361 Week 2 The EHR You Already Chart In: How to Write It

What NR-361 Week 2 asks for

Somewhere near the end of every shift there is a nurse charting in a hallway alcove with a folded paper towel of scribbled vitals beside the keyboard, back-entering numbers captured hours earlier because the medication pass could not wait for the login screen. Every working RN recognizes that scene, and most have starred in it. Week 2 of this course asks you to stop experiencing that scene and start analyzing it: what the record is for, why its workflows fight the work, what your workarounds reveal about the system's design, and what happens to a charted item after you sign it.

The analytic frame that separates an RN-to-BSN submission from a complaint is the difference between the record as your task and the record as an information system. From the user's chair, documentation is a burden measured in clicks and minutes at the end of a long shift. From the system's side, your flowsheet rows feed acuity tools, quality reporting, the next shift's picture of the patient, the coder who translates care into revenue, and eventually the datasets research runs on. The graded skill this week is holding both views in one piece of writing: honest about the friction, accurate about the functions, and specific about the path one data element travels after it leaves your hands.

Deliverables at this stage commonly take the shape of a discussion post or a short paper analyzing the EHR's role in nursing practice, sometimes with a workflow focus and sometimes with a benefits-and-barriers structure. Whatever your section runs, resist the two easy registers. Vendor-brochure prose, where the record has transformed care and everything is seamless, reads as unexamined. Break-room prose, where the record is the enemy of nursing, reads as unprofessional. The strong submission sounds like a clinician consultant: this is what the system does well, this is where it costs, here is the evidence, here is one moment from my own de-identified practice that shows the cost or the benefit operating.

Your workarounds are this week's richest material, and they need careful handling. Charting in batches, keeping a paper brain sheet, free-texting what a structured field made awkward: informatics literature treats workarounds as diagnostic evidence of a mismatch between workflow and design, not as confessions. Write about them in exactly that register, neutrally and without naming your facility, and never describe anything that would read as a safety violation you committed. Describe the pattern, cite the literature that documents it broadly, and analyze what it signals.

The NR-361 Week 2 method, step by step

Six moves for writing about a system you know too well to see.

1. Anchor the post in one workflow you personally run

   Admission assessment, a scheduled medication pass, discharge teaching documentation. Choose the one you could perform asleep, because your fluency is what lets you describe it precisely, and precision is what the rubric buys. Announce the choice in your first paragraph.

2. Trace the workflow in sequence, at the level of decisions

   Not every click, but every point where the system shapes what you do: what it demands before it lets you proceed, what it defaults, what it flags, what it hides two screens deep. A traced workflow is this course's recurring move, and this week is where you install it.

3. Name the friction and read it as evidence

   Where the sequence fights clinical reality, say so plainly and then interpret: a required field nobody's patient fits signals a design assumption; a paper brain sheet signals the record does not surface a working view of the shift. Cite the documentation-burden or workaround literature so the interpretation stands on more than your shift.

4. Follow one data element downstream

   Take a single item you chart, a pain score, a fall risk rating, an intake total, and follow it: who reads it next shift, what tool aggregates it, what quality measure or reimbursement logic eventually touches it. One element traced end to end demonstrates systems thinking better than a paragraph of generalities about data flow.

5. Balance the ledger with what the record does well

   Legibility, allergy visibility, retrievable history, remote access for a provider called at home. Give the benefits their own cited sentences rather than a grudging clause, because balance is almost always an explicit expectation in the rubric and always an implicit one with the grader.

6. Close with the nurse as more than a user

   End on the professional implication: the nurse who can articulate why a workflow fails is the nurse who belongs on the committee that fixes it. One or two sentences pointing from your analysis toward system-improvement participation lands the post exactly where a BSN course wants it.

A layout and word budget for an EHR workflow analysis

Sized for a short paper of roughly 700 to 900 words, a common Week 2 shape; halve the bands for a discussion post and keep the proportions. The outline is ours, drawn from the catalog arc rather than any syllabus, and your section's instructions outrank it wherever they differ.

Evidence craft for writing about the record

Let the literature carry every general claim about EHRs. Statements about documentation time, alert fatigue, error reduction or clinician burnout are empirical claims with published studies behind them. Your shift supplies the illustration; a cited source supplies the proof. A paragraph that runs claim, citation, then your de-identified moment scores; the same content in reverse order reads as anecdote with decoration.

Keep your facility invisible and your vendor unnamed. "A medium-sized community hospital's record system" does everything analysis needs. Brand names convert your paper into product commentary you must then source, and facility names put your employer into a submission you cannot retrieve. Screenshots, even cropped ones, are off the table entirely: they are facility property and they leak metadata you cannot see.

Describe workarounds as patterns, not incidents. Write that batch charting at shift's end is a common response to workflow mismatch, cited, and that your practice environment shows the pattern. Do not narrate a specific dated episode in which documentation lagged care in a way that reads as a policy breach with your name attached. The analytic point survives the generalization; your professional exposure does not survive the specifics.

Numbers arrive with base and window or not at all. If you cite a study on documentation burden, keep its terms: minutes per shift, proportion of shift time, sample and setting. And keep internal numbers out; your unit's click counts, audit reports and dashboard metrics are employer records, not citable evidence in student work.

Five mistakes that cost points in this week's territory

• The vent. A fluent complaint about charting, however true, answers no rubric row. Friction only earns points once it is interpreted as design evidence with a citation beside it.
• The brochure. An EHR post with no costs in it reads as unexamined to a grader who knows exactly what end-of-shift charting looks like.
• Breadth instead of a trace. Touring every module of the record leaves no words for the traced workflow where the depth points live.
• Confessional specifics. Dated, detailed workaround stories convert analysis into self-report. Patterns, cited and de-identified, make the same point safely.
• Forgetting downstream. A post that ends when the nurse signs the entry misses the half of the week that makes it an informatics assignment rather than a workflow diary.

Before you submit

• One workflow you personally run is named and traced in sequence
• Every general claim about EHRs carries a citation
• Workarounds appear as cited patterns, never as dated incidents
• One charted element is followed downstream with its stops named
• Benefits hold a cited paragraph of their own
• No vendor, facility, patient or internal metric appears anywhere

Questions students ask about this stage

Keep going