A video visit for four days of cough is the cleanest test of acute management writing there is, because the camera strips away almost everything except your history and your reasoning, and what is left on the page is the decision itself. Somewhere in the early applied stages of a management practicum the written work turns from planning to cases, and the first ones are usually acute: a single problem, a short arc, one decision to defend. The task is not to transcribe the visit. It is to argue why the treatment you selected was the right one for this person out of the several that would have been reasonable. Your section may print this as NR 577 or NR577; 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. Hours, encounter logs and preceptor evaluations are your own record and are never drafted, reconstructed or estimated with help.
What an acute management write-up has to establish
Read a stack of student acute case documents and the same structural failure appears in most of them: the assessment is thorough, the diagnosis is correct, and then the plan arrives as a set of instructions with no argument attached. Start amoxicillin, return if worse. That is a chart entry. A graded management document has to say why amoxicillin rather than the alternative, why that duration, what the decision would have been if one variable had been different, and what the follow-up interval is doing in the plan. Management courses grade the joint between the diagnosis and the treatment, and that joint is exactly where most write-ups fall silent.
The second thing the document has to establish is the decision threshold. Acute presentations in primary care are mostly self-limiting, and the interesting written question is almost never what is this. It is what would have to be true for me to treat, to test, or to send this person somewhere else today. Writing the threshold down converts a plan into reasoning: you are showing the reader the line you were working against, which is what allows a grader to evaluate the judgment rather than just the outcome.
The third is the safety net, written with specificity. Return if worse is not a safety net; it is a phrase. A real one names what the patient should watch for, at what point, and what they should do about it, and it accounts for whether they can actually act on those instructions. In a remote encounter this becomes the load-bearing part of the plan, because there is no in-person reassessment scheduled by default and the patient's own report is the entire monitoring system.
The fourth is a documented consideration of what you decided not to do. Every acute plan involves declined options: the test you did not order, the antibiotic you withheld, the referral you did not make. Naming one or two of those, with the reason, is one of the most reliable ways to lift a competent case document into the analysis band, because it demonstrates that the plan was chosen rather than defaulted into.
The boundary is fixed and worth restating on this page. The encounter happened, you were there, and the hours it counted toward, the log entry and the preceptor's evaluation of your performance are your own record, never drafted or reconstructed with help. What can be improved is the academic write-up about work you genuinely did, de-identified before it reaches a file that leaves the clinic. If your section runs a discussion alongside the case, treat the post as final copy, since posts do not reopen after submission in Canvas.
The NR-577 Week 2 method, step by step
Six moves for turning a lived acute encounter into a defensible written case.
-
1. Strip the encounter to the elements that changed a decision
Write the history and examination findings that moved your probability or your plan, and cut the rest. A full review of systems reproduced in a case document consumes the word count the argument needed and demonstrates completeness rather than judgment.
-
2. State the working diagnosis with the two you kept alive
One line for what you concluded and one for the alternatives still plausible enough to influence the plan. If nothing else was plausible, say why the presentation was that discriminating, because a differential of one is a claim requiring support.
-
3. Declare the treatment threshold before the treatment
Write the line you were working against: what would have had to be present for you to treat, test or refer. Then say which side of it this patient fell on. This single move separates reasoning from instruction more reliably than any other.
-
4. Justify the specific agent, dose and duration against a named source
Not antibiotics indicated, but this agent for this organism spectrum at this duration, per a guideline you name and date, adjusted for this person's allergies, renal function, pregnancy status, cost and what they can actually obtain.
-
5. Record the option you declined and why
One or two rejected choices with their reasons. Imaging withheld because the decision rule was negative, an antibiotic withheld because the presentation was viral and the patient understood the reasoning. Declined options are graded evidence of deliberate practice.
-
6. Build a safety net a specific patient could execute
What to watch for, by when, what to do, and where. Then test it against reality: whether they have transport, whether the pharmacy is open, whether they can afford the medicine, and whether a remote follow-up is sufficient for this problem.
A layout and word budget for an acute management case
Our frame for a single acute encounter written in depth, sized for roughly 1,100 to 1,400 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Element | What belongs in it | Word target |
|---|---|---|
| Presentation in brief | De-identified demographics, the complaint, its duration and trajectory, and the reason for presenting now. | 90 to 120 |
| Decision-relevant findings | Only the history and examination elements that moved probability or altered the plan, with the pertinent negatives that did the same. | 180 to 230 |
| Working diagnosis and live alternatives | The conclusion plus the two competitors still shaping the plan, each with the finding that keeps it alive. | 160 to 200 |
| Threshold statement | The line for treating, testing or referring, and which side of it this patient fell on. | 110 to 150 |
| Treatment justified | Agent, dose, route, duration, with the guideline named and dated and the patient-specific adjustments stated. | 240 to 300 |
| Declined options | One or two rejected choices with the reason each was rejected. | 100 to 140 |
| Safety net and follow-up | Warning signs, timing, action, location, and whether the patient can actually execute the instructions. | 160 to 210 |
Evidence craft for acute management writing
Name the guideline and its year in the sentence carrying the decision. Treatment recommendations for common acute infections change, and a recommendation attributed only in the reference list forces the grader to reconstruct which version you were working from. Put the source where the claim is.
Distinguish the guideline's recommendation from your application of it. The published recommendation is general; your decision is about one person with an allergy, a job, a pharmacy benefit and a preference. Write both, in that order. Case documents that reproduce a guideline without adapting it are marked as summary rather than management.
Use decision rules by name and report the actual score. Where a validated rule informed your threshold, say which rule, what the patient scored, and what that score implies. A rule invoked without its result is decoration, and graders in management courses check that specifically.
Report resistance and local patterns as local. Empiric choices depend on local susceptibility, and saying so, even briefly, shows you understand that a national recommendation lands differently in different places. Where you can cite a regional or institutional pattern, do; where you cannot, say the choice was made on national guidance and note the limitation.
De-identify before the document leaves the clinic. Remove names, dates, employers and the small combinations that identify: an exact age with an unusual occupation and a specific presentation is identifying even with no name. Widen bands, generalize the setting, and keep only what carries the reasoning.
Five mistakes that cost points at this stage
- The plan as instructions. A list of prescriptions and advice with no argument is a chart note, and a management rubric has nothing in it to reward.
- The whole review of systems reproduced. Completeness spent where judgment was being graded is the most common way these documents run long and score low.
- Guideline paraphrase with no patient in it. If the treatment paragraph would read identically for any patient with the diagnosis, no management reasoning has been demonstrated.
- An empty safety net. Return if symptoms worsen tells a reader nothing about what you actually told the patient or whether they could act on it.
- No declined options anywhere. A plan that appears to have had no alternatives reads as a default rather than a decision.
Before you submit
- Every finding in the document changed a probability or a decision
- Two live alternatives are named, each with the finding keeping it alive
- A treatment or testing threshold is stated explicitly
- The agent, dose and duration are justified against a named, dated source
- At least one declined option appears with its reason
- The safety net names signs, timing, action and place, and is executable by this patient
- All identifiers and identifying combinations have been removed
Writing an NR-577 acute case?
Send the rubric and your de-identified encounter notes out of Canvas. A premium original draft comes back in 24 to 48 hours with the threshold stated, the agent justified against a dated source and a safety net a real patient could execute, and revisions run until the grade lands.