NR-588 Week 4 Evidence Selection: How to Write It

What NR-588 Week 4 asks for

Evidence-based is the catalog phrase, and in a systems leadership course it means something narrower than it does in a research methods course. You are not being asked to appraise a study for its internal quality alone. You are being asked whether the intervention studied would work at your boundary, in your organizations, with your staffing, under your incentives. That is a question about context, and context is where most systems interventions fail even when the underlying idea is sound.

The literature you are drawing on has a distinctive shape. Interventions that span organizations are studied through pragmatic trials, stepped-wedge designs, quality improvement collaboratives, program evaluations and single-site reports, far more often than through tidy randomized trials, because randomizing organizations is expensive and often impossible. That means the evidence base is thinner and messier than in clinical topics, and a paper that dismisses everything below trial level has left itself with nothing to build on.

The graded move is weighting rather than sorting. A single-site improvement report tells you almost nothing about effect size and a great deal about feasibility: what it cost in staff hours, what broke in the first month, what the receiving organization refused to do. A larger evaluation tells you the reverse. Writing that reads both kinds of study for what each is actually good at is the difference between a graduate synthesis and an annotated list.

Expect the deliverable to be a written evidence review or synthesis supporting the change you have been building toward since week one, often with a summary table, and sometimes accompanied by a posted response naming your strongest source and why. If your section runs a discussion this week, be precise about study design and setting, because a claim about a study is easy for a grader to check and posts do not reopen after submission in Canvas.

There is one trap specific to this stage in a leadership course. Students frequently gather evidence about the clinical problem when the rubric wants evidence about the intervention. Literature establishing that transitions from post-acute settings carry medication risk is background. Literature about what happens when somebody tries to fix it is the evidence your proposal actually rests on, and it is the harder search.

The NR-588 Week 4 method, step by step

Six moves for building an evidence base a cross-organization proposal can actually stand on.

1. Write the question as intervention, population, setting and outcome

   Not what causes transfer failures, but what happens to avoidable transfers when a structured communication process is introduced between a skilled facility and a receiving hospital. The setting term is the one that matters most in this course, because an intervention that works in an integrated system may have nothing to say about two independent organizations.

2. Search for the intervention, then separately for the context

   Two searches, kept apart in your notes. The first finds studies of the change itself. The second finds work on the setting: post-acute care, interfacility communication, contracted services, whatever your boundary consists of. The second search is what lets you argue transferability instead of asserting it.

3. Extract implementation detail, not only results

   For each study, record who delivered the intervention, how much staff time it consumed, what technology it assumed, whether the organizations shared a record, and what the authors say went wrong. This is the column students omit and the column that determines whether your proposal is realistic.

4. Grade each source for weight rather than sorting it into a tier

   Say what this study is good evidence for and what it is not. A stepped-wedge evaluation across twelve facilities is good evidence about effect and weak evidence about your particular staffing. A single-site report is the reverse. Writing that sentence for each source is most of the synthesis.

5. Name the context gaps between the studies and your boundary

   List the differences that could change the result: shared versus separate records, on-site versus visiting providers, agency versus permanent staffing, a partner who chose to participate versus one who is contractually indifferent. Each gap becomes either an adaptation in your proposal or a stated limitation.

6. Close with a weighted verdict, not a summary

   State what the evidence supports doing, how confidently, and which part of your intended change the literature does not cover at all. A synthesis that ends by restating the studies has described the field. A synthesis that ends by saying the effect is modest, the feasibility evidence is thin, and the change is still worth attempting for these reasons has done leadership work.

A layout and word budget for a systems evidence synthesis

Our frame for an evidence review supporting a cross-boundary proposal, sized for roughly 1,300 to 1,600 words plus a summary table. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

Evidence craft for cross-organization literature

Name the design from the methods section, never from the abstract. Abstracts describe programs generously and often call an uncontrolled before-and-after project an evaluation of effectiveness. Read what was actually done: whether there was a comparison group, whether allocation was anything other than volunteering, and whether the outcome was measured the same way in both periods.

Report effects in units a leader could act on. Transfers per hundred resident-months, readmissions per hundred discharges, minutes to reconciliation. Percentage reductions detached from a base rate are the single most common way a systems paper overstates its evidence, because a large relative change on a small absolute base looks like a transformation and is not.

Treat single-site improvement reports as feasibility evidence and say so. They are the most common publication in this field and they carry genuine information about what an intervention costs to run. What they cannot rule out is everything else that changed in the same period, including the attention the project itself created. Use them for the practical layer, name their design plainly, and do not let a favorable local result carry a claim your stronger sources do not support.

Note who participated and how they were recruited. Organizations that volunteer for a transitions collaborative differ systematically from organizations that do not, and that difference is directly relevant when your partner across the boundary has no particular interest in your project. One clause naming this is worth more than a paragraph of generic limitations.

Say who funded the work and where it was conducted. Funding source and health system context both affect how a finding should be weighted, and a program evaluated inside an integrated delivery system may assume infrastructure that two independent organizations simply do not have between them.

Five mistakes that cost points in this week's territory

• Evidence about the problem instead of the intervention. Ten sources establishing that transitions are risky do not support a proposal about what to do at 4pm on a Friday.
• Study-by-study paragraphs. A synthesis is organized by finding, not by author. Sequential summaries are the clearest signal that no synthesis occurred.
• Dismissing everything below trial level. In cross-organization work that leaves you with almost nothing, and it discards the only sources that describe implementation honestly.
• Ignoring setting. An intervention evaluated inside one integrated system, applied without comment to two independent organizations, is the transferability error this course is built to catch.
• No verdict. An evidence section that ends without saying what the evidence supports has described a literature rather than used one.

Before you submit

• The question names the setting and the boundary, not only the intervention
• The search is described precisely enough that a reader could repeat it
• Each design is named from the methods rather than from the title
• Effects appear in absolute units with their base rates
• Every context gap is marked as either an adaptation or a stated limitation
• The section closes with an explicit judgment about what the evidence supports

Questions students ask about this stage

Keep going