The middle of a differential diagnosis practicum is where testing gets argued rather than ordered. Every investigation in a written plan has to answer one question on the page: what decision would this result change? A test whose positive and negative results lead to the same next step has cost the patient time and money and has bought your reasoning nothing, and in an office where most people are well it has also created the conditions for a false positive to do real harm. Your section may print this as NR 576 or NR576; 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. Clinical hours, logs and preceptor evaluations remain your own record and are never drafted, reconstructed or estimated with help.
What a diagnostic plan has to justify
An audit of ordered tests against documented reasoning is one of the more uncomfortable exercises in ambulatory practice, and it teaches the lesson this stage is built on. Pull a set of visits, look at what was ordered, then look at what changed as a result. A substantial share of the tests will turn out to have been reflexive: the panel that comes with the complaint, the imaging ordered because the patient expected it, the screening item that belongs to a different visit entirely. Nothing in the note says what any of them were for. Your written plan has to be the opposite document.
The argument for a test has three parts and all three belong in the writing. Where you are starting, which is the probability you reached at the end of your differential. What the test does to that probability in each direction. And what you would do differently depending on which way it lands. A test justified that way is defensible even when it comes back normal, because the normal result was itself a planned outcome with a planned response.
Primary care makes the base rate argument unavoidable. When most people presenting with a complaint do not have the condition you are testing for, even a reasonably accurate test produces a meaningful number of false positives, and each of those carries a cascade: repeat testing, referral, anxiety, sometimes a procedure. Writing one sentence about what a positive result would actually mean at your starting probability is the strongest single addition available to this section, and very few students include it.
Watchful waiting with a defined interval is a plan, not an absence of one, and it should appear in your writing as a deliberate choice with its own justification. In an office, time is a diagnostic instrument: many self-limiting conditions declare themselves within days, and the reasoning for observing rather than testing needs the same structure as the reasoning for a test, including what would end the observation early.
The boundary is unchanged. Ordering, performing and following up investigations for real patients happens inside your precepted practice under supervision and belongs to that relationship; your hours, your log and your evaluation are your own record. What is being built here is the written justification for reasoning you did, de-identified. Deliverables at this stage are commonly a case document with a diagnostic plan section, sometimes with a table of tests and rationales, and any post is final copy since posts do not reopen after submission in Canvas.
The NR-576 Week 4 method, step by step
Six moves that make a testing plan defensible in writing.
-
Write your starting probability in words before listing anything
Likely, plausible or unlikely, tied back to the ranking you argued. Everything in this section is an operation on that starting point, and a plan written without one is a plan with no reference frame.
-
State the decision each test would change
One clause per test: if positive I would do this, if negative I would do that. If the two branches are the same, delete the test. This single rule removes more unjustified investigations than any other.
-
Say what the test actually does to probability
Use the language of shift rather than of proof. Sensitive tests used to lower the likelihood of a serious cause, specific tests used to confirm, and an honest note where a test does less than clinicians commonly assume.
-
Write the false positive sentence
At your starting probability, what would a positive result most likely mean, and what would follow from it. This is the sentence that demonstrates ambulatory reasoning more clearly than any other in the document.
-
Sequence rather than batch
Say what you would do first and what depends on the result. A plan that orders everything at once has not made a decision; a plan that names an order has, and it also reflects how ambulatory workups actually run.
-
Cost the plan in the patient's terms
Out-of-pocket cost, travel, time off work, availability of the test locally, and how long results take. A plan the patient cannot execute has not been planned, and naming the constraint is graded content rather than an excuse.
A layout and word budget for the diagnostic plan
Our frame for the testing section of an ambulatory case document, sized for roughly 400 to 600 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 |
|---|---|---|
| Starting position | The probability you carried out of the differential, in words, with the candidate it attaches to. | 40 to 60 |
| First-line investigation | The test, the decision it changes in each direction, and what it does to the probability. | 110 to 150 |
| Conditional next steps | What depends on the first result, stated as branches rather than as a batch of orders. | 90 to 130 |
| What you are not ordering and why | Two tests a reader might expect, declined with reasons, including where the result would not change management. | 80 to 120 |
| False positive and cascade | What a positive would most likely mean at this starting probability and what would follow. | 50 to 80 |
| Feasibility for this patient | Cost, access, timing and what you would substitute if the preferred test is unavailable. | 60 to 90 |
Evidence craft for testing arguments
Cite the performance of the test, not just its existence. Sensitivity, specificity or likelihood ratios drawn from a study in a comparable population turn an assertion that a test is useful into an argument about how useful. Name the population, because performance measured in a referral centre rarely transfers to a clinic.
Use guidance documents where they exist, with body and edition named. Recommendations about who should be tested and when are published, and citing the current version inside the sentence is both stronger and safer than paraphrasing a remembered rule. Where your reasoning departs from guidance, say so and give the reason.
Keep numbers proportional and honest. If you report a test characteristic, report it as it was published rather than rounding it into a claim. Where you illustrate the effect on probability, show the arithmetic in fractions of a defined group rather than in bare percentages.
Name the harms of testing as well as the benefits. Radiation, incidental findings, cost, delay, and the anxiety of an ambiguous result are all legitimate content in a diagnostic plan and all rarely appear in student work. One clause each is enough to demonstrate that the trade-off was weighed.
Do not attribute a real order to your own judgment. If the plan you write differs from what happened in the visit, say which is which. Describing your reasoning as the reasoning behind decisions somebody else made is both inaccurate and unnecessary, and the honest version reads better.
Five mistakes that cost points at this stage
- A list of orders with no rationale. Tests named without the decision they change is the ambulatory equivalent of a differential with no discrimination.
- Batching everything at once. Ordering the full panel plus imaging on the first visit shows no sequencing judgment and usually contradicts the ranking you just argued.
- Ignoring the base rate. A confident interpretation of a positive result in a low-probability patient is the classic ambulatory reasoning error and it is easy for a grader to spot.
- Watchful waiting written as doing nothing. Observation without an interval, a review plan and an end condition is not a plan and will be scored as an omission.
- No cost or access consideration. Primary care plans that ignore what the patient can actually afford or reach are incomplete on their own terms.
Before you submit
- A starting probability is stated before any test is named
- Every test carries the decision it would change in each direction
- Test performance is described with a source and a named population
- At least two plausible tests are explicitly declined with reasons
- The meaning of a positive result at this base rate is addressed
- The plan is sequenced, with branches rather than a batch
- Cost, access and timing appear at least once
Writing an NR-576 diagnostic plan?
Send the rubric and your de-identified case notes out of Canvas. A premium original draft comes back in 24 to 48 hours with every test tied to the decision it changes and the base rate argument written in, and revisions run until the grade lands.