Early in NR-569 the written work turns to the sentence that governs everything after it: the problem representation, the one-line summary that converts a pile of findings into a diagnostic question. This stage teaches the compression, not the diagnosis. Your section may print this as NR 569 or NR569; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What NR-569 Week 2 asks for
In a simulation lab the manikin drops its pressure and the scenario lead asks the team leader to summarize in one sentence. Most graduate students give a paragraph. They list the vital signs, the past history, the medications, the labs that have returned, and the reader at the end of it knows everything except what problem is being solved. That gap is the subject of this stage. A problem representation is a single abstracted sentence naming who this patient is in risk terms, over what time course, with what defining features, and it is the tool that makes a differential possible at all.
The compression follows a shape. Demographics and comorbid risk become a semantic category rather than a list. Time course becomes an adjective: hyperacute, subacute, progressive, relapsing. Findings become abstractions rather than raw data, so a potassium of 6.4 with peaked T waves becomes symptomatic hyperkalemia, and three days of climbing oxygen requirement becomes progressive hypoxemic respiratory failure. What you are practising is the move from data to semantic qualifiers, and every acute care clinician who reads quickly is reading for exactly those qualifiers.
Written work at this depth is usually short and dense: a set of representations built from your own de-identified encounters, sometimes paired with an explanation of what each abstraction bought you. Discussion boards often carry a version of the same task. Treat a post as final copy, because Canvas posts do not reopen once submitted, and a one-line summary containing a contradiction is the easiest thing in this course for a peer to catch.
Here is the boundary this course lives inside, stated again because it governs every stage. The manual supports the written layer only. Your precepted hours, encounter logs, patient counts, site paperwork and preceptor evaluations are your record alone, never drafted, reconstructed or estimated with help. What we can teach is how to write about encounters you genuinely lived, with every identifier removed before the sentence exists.
The NR-569 Week 2 method, step by step
Six moves that compress a messy presentation into a sentence a differential can hang from.
-
Strip the narrative to findings first
List what is objectively present without interpretation: the numbers, the exam findings, the trajectory. Interpretation added too early is how a wrong anchor enters the sentence and survives the whole workup.
-
Convert the person into a risk category
Not a 67-year-old man with diabetes, hypertension and prior stenting. An older adult with established atherosclerotic disease and diabetes. The category is what activates the right illness scripts; the list is what obscures them.
-
Fix the time course explicitly
Minutes, hours, days or weeks changes the differential more than almost any other variable. Write the tempo into the sentence as a qualifier rather than leaving it to be inferred from a history paragraph nobody rereads.
-
Abstract the defining findings into syndrome language
Two or three abstracted features, no more. Hypoxemic respiratory failure with new bilateral infiltrates is a representation. A recitation of the saturation trend, the film report and the current oxygen delivery device is a data dump.
-
Say what the sentence excludes
Good representations carry a discriminating negative when one exists: without fever, without chest pain, without focal deficit. A single well-chosen absence narrows a differential faster than three more positives.
-
Test the sentence by generating from it
Read your representation aloud and see what diagnoses arrive unprompted. If nothing arrives, the abstraction failed. If everything arrives, it is too vague. A working representation produces a short, specific list on its own.
A layout and word budget for a problem representation exercise
The frame our tutors keep beside this stage, sized for a written set of roughly 900 to 1,200 words covering three or four de-identified presentations. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Framing paragraph | What a problem representation does for diagnostic reasoning, supported rather than asserted, with the de-identification statement. | 110 to 140 |
| Presentation one | The raw findings in brief, then the abstracted sentence, then two lines on what the abstraction changed. | 200 to 240 |
| Presentation two | A contrasting tempo, so the set demonstrates that time course drives the sentence rather than the organ system. | 200 to 240 |
| Presentation three | One where a discriminating negative did the heavy lifting, named explicitly as the pivot. | 200 to 240 |
| Comparison across the set | What the three sentences share structurally, and where your own abstractions were still too concrete. | 150 to 190 |
| Close | The one habit you are carrying into the rest of the practicum, written as a change rather than a resolution. | 60 to 80 |
Evidence craft for problem representation writing
Cite the reasoning literature, because this is a reasoning task. Semantic qualifiers, illness scripts and dual process models are described in published clinical reasoning scholarship, and naming a source with its year is what separates an argued method from a study habit you happen to like.
Keep raw data and abstraction visibly separate. Present the findings, then the sentence, then the reasoning. When they are braided together a grader cannot see whether you abstracted or merely rephrased, and the abstraction row is the one carrying the points at this stage.
Report numbers with units and trajectory. A lactate of 4.2 rising from 2.1 over six hours is evidence about tempo. A high lactate is an adjective. Acute care writing is judged partly on whether you treat values as trends rather than as snapshots.
Use standard terminology rather than local shorthand. Unit slang and institution-specific abbreviations read as imprecision on a graduate paper, and some of them mean different things in different hospitals. Write the full term at least once, then abbreviate consistently.
De-identify before drafting, not after. Age bands rather than exact ages, no admission dates, no unit or facility names, no rare detail combinations. If a presentation is unusual enough that de-identification would not protect the person, choose a different encounter for the assignment.
Attribute the frameworks you borrow. If you organize your abstractions around a published reasoning model or a named diagnostic framework, say whose it is in the sentence where you first use it. Graders at this level read the difference between a student applying a documented method and a student improvising structure and hoping it looks like one, and the first is scored as scholarship while the second is scored as opinion. The same rule applies to any table or template you adapt: name the origin, then say what you changed about it and why the change fits acute care presentations rather than ambulatory ones.
Five mistakes that cost points in this week's territory
- A summary that is really a handoff. Everything relevant, in chronological order, is a report. A representation is an abstraction, and length is the giveaway.
- Diagnosis smuggled into the sentence. Writing a patient with sepsis has decided the question the differential was supposed to open. Write the syndrome, not the label.
- Time course omitted. Without tempo the sentence cannot discriminate between processes that share every other feature, and graders in this course look for it specifically.
- Comorbidity dumped rather than categorized. Five listed conditions activate nothing. One risk category activates the right scripts immediately.
- No source anywhere. A methods stage in a graduate course still expects support, and reasoning scholarship exists precisely so this claim does not rest on your own preference.
Before you submit
- Each representation is one sentence, not a paragraph wearing a sentence's clothes
- Demographics appear as a risk category rather than a list of conditions
- Time course is stated explicitly in every sentence
- Findings are abstracted into syndrome language, with units and trends where numbers appear
- At least one discriminating negative is present and identified as the pivot
- Reasoning scholarship is cited with the issuing author and year in the sentence
- Every encounter is de-identified and no site or unit is named
Compressing cases for NR-569?
Send the rubric and the prompt out of Canvas. A premium original draft of the written layer comes back in 24 to 48 hours with abstraction visible in every sentence, and revisions run until the grade lands. Hours, logs and evaluations stay yours.