This page holds a finished NR 558 Week 2 screen and default review: every element on one screen, the state it arrives in, and the layer that state came from. Searches like "nr 558 week 2 assignment example", "nr558 week 2 sample" and "nr 558 week 2 example" land here.
What a finished NR 558 Week 2 screen and default review looks like
It reads as an inventory with an argument attached. The screen is fixed first, by name and by the point in the shift it opens, and then every element on it is listed in the order the eye meets them rather than the order the build lists them. Beside each sits its arrival state and whether a nurse can leave it alone. Required, optional, pre-filled and hidden are kept apart, because a required element and a pre-filled one fail in opposite directions: one stops you, the other agrees with you. The review then does the harder half, naming what the screen has no place for at all, and where that finding actually ends up instead. Two or three elements get a paragraph each and the rest stay in the table.
How a NR 558 Week 2 example is structured
Scope opens the review and is unusually literal: one screen, named, with the work either side of it sketched in a line so a reader knows what came before and what the nurse does next. The inventory arrives next in table form, a row for every element, carrying the printed label, the arrival state, whether it blocks saving, and the layer it plausibly came from. Prose then takes the three rows worth arguing about, and the argument keeps the same shape each time: this state was somebody's decision, here is the behavior it produces at speed, here is what that behavior puts into the record. What is missing comes next, since an absent element is a decision as much as a pre-checked one. The review ends on questions with addressees, each written so that a yes or a no would count as an answer.
One screen, fixed by name and moment
The screen named and placed in the shift, with a line on what precedes it and what the nurse does next, so the review has edges it cannot drift past.
Arrival state before judgment
Pre-checked, pre-filled, blank, grayed or hidden, recorded for every element first, because a judgment made ahead of the inventory only ever finds what annoyed the writer.
Required and pre-filled are opposites
One refuses to let you leave, the other agrees with you and lets you go. Rows mixing the two produce a table nobody downstream can act on.
What the screen has no room for
The finding with no element of its own, and where it goes instead, usually a comment box that no report and no next reader will ever open.
Questions with an addressee
Two or three, each aimed at a role that could answer, phrased so a yes or a no settles something rather than opening a longer conversation.
Where marks go in NR 558 Week 2
A review that judges the screen before inventorying it loses the week, because every judgment then rests on the three elements the writer already disliked. Running second is the arrival state left out, so a reader cannot tell whether the nurse had to do anything at all to produce the value under discussion. After that comes the missing-element half skipped entirely, which is both half the assignment and the half separating a review from a complaint. Smaller costs accumulate quickly. Required and pre-filled handled as one category. A layer asserted with no route to checking it. An element named in ward slang so nobody could find it. A closing question aimed at the software rather than at a person. And a table carrying more rows than the writer can argue through.
Get a NR 558 Week 2 example written to your instructions
Send the Week 2 instructions and, if your section supplies a template with fixed columns, that too, and a custom review is written to them and returned inside 24 to 48 hours, first one free. A live screen photographed on a work phone and a report file carried out of the building are the two things this desk will not build from.
NR 558 Week 2 questions, answered
How many elements should the table hold?
Whatever the screen actually holds, which is often fifteen to thirty and sometimes more. The table is cheap and the prose is not. Inventory everything, then argue three rows properly. A review covering ten elements at equal depth reads flat, and a marker cannot tell which of them the writer thought mattered, which is exactly the judgment being graded.
Can I review a screen from a system I do not use?
Yes. Publicly described records, training environments and the ordinary behavior of any electronic record give you enough, and sections often supply a mock screen for that reason. What the review needs is a fixed object with labels on it. What it cannot use is a screen assembled from memory, because the arrival states drift as you write.
What if a default turns out to be correct?
Then say so and say why, and the review gets stronger for it. Most pre-filled values were chosen because they are right most of the time. The interesting question is what happens on the shift when one of them is wrong, and how visible that wrongness is to somebody clicking through at speed. A review finding every default indefensible has not looked at the common case.