NR-330 Week 1 The Admission Problem Map: How to Write It

What NR-330 Week 1 asks for

Picture the admission that a second adult health course is built to teach. A 71-year-old man with COPD and type 2 diabetes has been checking in with his clinic by video for a month, reading numbers off a home pulse oximeter at each visit. This week the readings slid, the video call showed pursed-lip breathing he could not talk through, and the visit ended with instructions to come in. He arrives on your medical-surgical telemetry unit with a new pneumonia stacked on top of two chronic conditions, an oxygen requirement he did not have last month, a glucose log that stopped making sense once the infection started, and a folder of home readings that are now part of his chart. Nothing about him fits on one problem line.

The opening written work of this course, in our judgment, is where you learn to hold a patient like that on paper. Before a care plan can be written, the raw database, history, home monitoring data, admission assessment, first set of labs, has to be sorted into problems, and the problems have to be arranged so that a reader can see which one is driving today, which ones are passengers, and which ones are waiting to become drivers. We call that written product a problem map, and whatever your section titles its first deliverable, the intellectual work underneath it is almost certainly this: demonstrate that you can organize complexity before you act on it.

The 144 clinical hours attached to this course change the writing in a specific way. More hours means more unit days per week, which means the gap between what you saw on the floor and what you type at night is shorter and the volume of real observations feeding your written work is larger. Graders read that volume as an expectation: a student living on the unit three days a week is expected to write assessment data with the texture of someone who has actually watched a patient breathe. Generic textbook findings in the database section read as a missed opportunity in a course that gives you this much floor time.

One boundary before anything else. The clinical hours themselves, every assessment performed on a real patient, every entry in a clinical log, every signature and every attendance record, are your own work and nobody else's. Manuals and tutors operate on the written layer only: the analysis, the organization and the argument you build on the page afterward.

The NR-330 Week 1 method, step by step

Six moves that turn an admission database into a map a grader can follow.

1. Inventory the database before judging any of it

   List every data point you have, history, home monitoring readings, admission vitals, labs, medication list, functional observations, without deciding yet what matters. Judgment applied too early deletes data; the folder of home oximetry readings is easy to dismiss and is often the only trend evidence in the case.

2. Cluster the cues by mechanism, not by chart tab

   Group findings by the process producing them rather than by where they were recorded. The climbing respiratory rate, the new oxygen need and the sliding home saturations belong together; so do the deranged glucose log and the infection driving it. A cluster organized by mechanism is already half an analysis.

3. Name each problem in nursing language

   Convert each cluster into a problem statement written in the three-part form your program teaches: the problem, its related factors, its defining evidence. Resist medical shorthand. Pneumonia is the diagnosis medicine owns; impaired gas exchange evidenced by the cues you listed is the problem nursing plans against.

4. Map the dependencies between problems

   Write one sentence per pair of problems that touch: what the infection does to the glucose control, what the hypoxia does to activity tolerance, what the chronic lung disease does to the ceiling of recovery. These sentences are the map part of the problem map, and they are what separates this course's writing from the first adult health course.

5. Rank the problems with a stated rule

   Declare the rule you are ranking by, threat to oxygenation first, then physiologic instability, then everything else, and apply it visibly. A ranking with its rule on display can be argued with, which is precisely what makes it gradable; a bare ordering is just a guess with numbers on it.

6. Attach a first monitoring plan to the top problem

   Close by writing what you would watch over the next shift for the problem you ranked first: which parameters, at what frequency, and what change would make you escalate. This is the clinical decision making strand of the course showing up early, and strong Week 1 submissions let it.

A layout and word budget for a problem map

The frame below sizes a written product of roughly 1,000 to 1,300 words for a multi-system admission. It is our own outline rather than anything the university issues, and your section's template outranks it wherever the two disagree.

Evidence craft for a problem map

Home monitoring data is evidence and deserves the same dress code. A saturation trend from a home device arrives with questions attached: what device, read under what conditions, over what period. Write it that way. A month of morning readings drifting from the low nineties to the mid eighties tells a story that a single admission value cannot, and cases increasingly include remote monitoring data precisely to see whether students will use it.

Every mechanism sentence gets a citation. When you write that infection destabilizes glucose control or that chronic air trapping changes what a normal saturation looks like for this man, cite the course text or a current clinical reference. Mechanism claims are checkable, and graders check them.

Baselines before judgments. A respiratory rate of 24 means one thing in a previously healthy adult and another in a man whose ordinary rate runs 20. Hunt the case for baseline evidence, his usual walking distance, his usual home readings, and state the baseline in the same sentence as the acute finding every time you interpret one.

De-identify with discipline. Age bands rather than ages where your template allows, no names, no dates that could locate an admission, no facility identifiers. The habit costs nothing here and protects you for the rest of the program, where the data feeding your papers comes from real floors.

Five mistakes that cost points in this week's territory

• Care planning before mapping. Students who leap to interventions in Week 1 skip the organizing work the deliverable exists to grade, and the plan they produce floats on an unsorted database.
• Clusters copied from chart tabs. Grouping data as vitals, labs and history reproduces the chart's filing system instead of demonstrating your reasoning; mechanism is the organizing principle that scores.
• Problems without evidence trails. A problem statement that cannot be traced to specific cues in your inventory reads as imported from a care plan book rather than derived from this patient.
• Rankings without rules. An unstated priority logic cannot be defended, and at this level the defense is the graded object, not the ordering itself.
• Discarding the home data. The telehealth folder and the glucose log are in the case on purpose; a map that ignores them has ignored the only longitudinal evidence available.

Before you submit

• The full database appears in inventory form before any judgment is applied
• Clusters are organized by mechanism and introduced by the linking process
• Each problem statement traces visibly to cues in your inventory
• Dependencies between problems are written as single clear sentences
• The ranking rule is stated before it is applied
• Every number carries a unit, a time and a baseline where one exists

Questions students ask about this stage

Keep going