NR-603 Week 7 usually turns to the skill that keeps complex care coherent: deciding what leaves your scope, writing the consult question as one answerable sentence, packaging exactly the information the consultant needs, and holding the patient's care together while the answer is pending. Coordination is the clinical act this week grades. Your section may print this as NR 603 or NR603; 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.
Referral craft lands late in the arc because it presumes everything earlier: you cannot ask a sharp consult question about a case you have not reasoned, tested and audited. The desk's perimeter, drawn again at week seven: written assignments in, written drafts out, nothing else. The practicum's hours, its preceptor and every signature it requires are outside our walls permanently.
What NR-603 Week 7 asks for
Expect the territory to cover the scope decision made honestly and early, the consult question engineered as a single answerable sentence, the information package selected for the consultant rather than dumped, interim management assigned while the answer is pending, the division of labor after the consult returns, and the loop closed with the patient in language that keeps them oriented in their own care. Failed handoffs are content here too, because most coordination evidence is about where the process breaks.
The deliverable shapes are usually a referral letter or consult request with its supporting reasoning, a care coordination plan for a patient crossing settings, or a paper analyzing a fragmented-care scenario. If your section runs a discussion this week, it commonly asks where primary care management should have ended in a described case, which is a scope question graded on the reasoning rather than the line's exact position.
Graders in this territory read the consult question first, because it is one sentence and it predicts the rest. A vague question, evaluate and treat, or patient with multiple issues, promises a package assembled with the same lack of aim.
The NR-603 Week 7 method, step by step
Six moves that make a handoff hold.
-
Decide the scope question in writing
Name what stays under your management and what leaves, with the reason: diagnostic uncertainty beyond the setting's tools, therapy beyond its monitoring capacity, risk beyond its safety margin. The honest boundary, stated plainly, is the week's first graded act.
-
Engineer the consult question
One sentence a consultant could answer in a paragraph: is this finding X or Y, should this regimen add Z given this constraint, does this patient need the procedure now or surveillance. If your question needs three sentences, you are asking two questions; pick the one this referral is for.
-
Package for the reader, not the archive
Select what the consultant needs to answer that question: the relevant course, the pertinent results with dates, the current list, what you already tried and what it did. State why each inclusion earns its place. Everything else is retrieval noise around the signal.
-
Assign the meantime
Write what continues under your care while the answer is pending: the conditions still yours, the monitoring that cannot pause, the findings that would escalate the referral to urgent. Patients are lost in precisely this gap, and the rubric knows it.
-
Divide the labor after the answer
Say who does what once the consult returns: what you resume, what the specialist keeps, how disagreement between the answer and your read would be resolved. Co-management without a written division decays into duplicated tests and dropped tasks.
-
Close the loop with the patient
Write what the patient was told: why the referral, what to expect, what to do while waiting, and who to call for what. Then the format pass: current APA, headings in your week's rubric wording, references current.
A referral package, section by section
Targets assume 1,350 words. Rescale to your prompt; the question and the package are the graded core, and the meantime section is the one most drafts forget.
| Section | What belongs there | Word target |
|---|---|---|
| Scope decision | What stays, what leaves, and the stated reason the line sits where it does | 190 to 230 |
| The consult question | The single answerable sentence, plus a short defense of why this is the question | 140 to 180 |
| Information package | The selected course, results with dates, current list and tried-and-failed history, each earning its place | 260 to 310 |
| Interim management | What continues under your care, the monitoring that cannot pause, and the urgent-escalation triggers | 220 to 260 |
| Post-consult division | Who owns what after the answer, and how disagreement would be resolved | 170 to 210 |
| Patient communication | The explanation given, the waiting instructions, and who to call for what | 170 to 210 |
The tried-and-failed history inside the package is the courtesy that changes outcomes: it is the difference between a consultant starting from your month six and starting from your day one.
Citing coordination evidence
The referral and handoff literature is observational almost throughout: studies of missed referrals, unreturned consults and information lost between settings describe associations between process features and failures, and your verbs should say so. Structured communication was associated with fewer losses is citable; guarantees are not, and the register difference is scored.
Failure statistics in this territory are startling enough to tempt exaggeration, so keep each figure's scaffolding attached: the health system studied, the referral types counted, the year, and the denominator. A loss rate measured in one integrated system does not describe every clinic, and writing as if it does trades accuracy for drama at the cost of the evidence row.
Where professional bodies publish current guidance on care transitions or co-management agreements, those documents anchor the craft sections, cited in current editions with the year in your sentence. One well-chosen source on what consultants report needing from referrals is worth citing too, because it converts your package section from opinion into evidence-informed design.
Five mistakes that cost points in the referral week
- A referral without a question. Evaluate and treat hands the consultant your reasoning work and announces that it was not done.
- The chart dumped whole. An unselected package buries the answer-relevant signal and shows no editorial judgment.
- The meantime unassigned. A patient with no named manager between request and answer is the classic coordination failure, reproduced in your own paper.
- No return path. A handoff with no post-consult division of labor converts referral into abandonment one step later.
- The patient informed last. Coordination written entirely between clinicians, with the patient unbriefed, fails the person the loop exists for.
Before you submit
- The scope decision states what stays, what leaves and why
- The consult question is one answerable sentence
- Every item in the package earns its inclusion for that question
- Interim management names what continues and what escalates
- The post-consult division assigns every ongoing task
- The patient's briefing is written in their language with contacts for each problem
Referral assignment due and the question will not sharpen?
Send the case and rubric from Canvas. Within 24 to 48 hours: the scope argued, the question engineered to one sentence, the package built to answer it.