NR-662 Week 3 Evidence Table and Intervention Choice: How to Write It

What NR-662 Week 3 asks for

Take a project aimed at fifteen-month immunization completion in a pediatric panel. Search the literature and you will find reminder and recall systems, standing orders, provider prompts inside the record, pre-visit planning, text message outreach, and combinations of all of them. They do not all produce the same size of effect, they were not all tested in settings that look like a family practice with one floating nurse, and several of the strongest results came from systems with staff your site does not have. The capstone question is not which idea sounds good. It is which of these, given what you documented about your microsystem last stage, could actually be delivered here and still carry evidence behind it.

An evidence table is the instrument that makes that choice visible. Each row is one study or synthesis, and the columns force the comparisons that matter: design, sample and setting, what exactly was done, what was measured, what changed, and how much confidence the design supports. A table built well answers a reader's questions before they ask them. A table built as a reference list with borders answers nothing, and graders can tell the difference in about ten seconds.

The prose that follows the table has one job: to move from what the evidence collectively supports to what you will do. That is a decision paragraph, and it should name the intervention component, the reason it was chosen over the alternatives, and the feasibility argument that connects it back to your setting. Where a section runs a discussion at this stage, it often asks for your strongest single source. Post that as final copy, since Canvas responses do not reopen, and be exact about what the study actually found rather than what its title implies.

Where the boundary sits in an evidence stage. The 144 clinical hours, the immersion itself, the observation of the advanced role and everything you do at the site remain your own work and cannot be performed by anyone else. Hour logs, encounter records, site paperwork, signatures and evaluations completed about you are your own record, never drafted, reconstructed or estimated with help. The written layer is what a manual can teach: how to build a table that supports a decision, how to weigh studies whose settings differ from yours, and how to write a justification that survives a reviewer. Anything drawn from what you saw at the site enters the page de-identified.

The NR-662 Week 3 method, step by step

Six moves that turn a folder of articles into a defended intervention.

1. Convert your problem into a searchable question first

   Population, intervention, comparison, outcome, in your own words, before you open a database. A search built directly from a problem statement returns everything about the disease. A search built from a structured question returns work about the process you are trying to change.

2. Record the search so someone could repeat it

   Databases used, terms and combinations, filters, date range, and how many results survived each stage of screening. A capstone manuscript later needs this paragraph, and reconstructing it in week seven from memory is a well-known form of self-inflicted misery.

3. Build the table around decisions, not around citations

   Design, setting and sample, the intervention described concretely, the outcome and how it was measured, the result with its size, and your appraisal note. If a column would not change which intervention you pick, it does not deserve the width.

4. Read the intervention description closely enough to copy it

   Most improvement studies report a bundle. Say which component did what, who delivered it, how often, and for how long. Vague implementation description is the single largest reason improvement findings fail to transfer, and naming components precisely is where your table beats a literature summary.

5. Weigh the body, then say what it supports

   Group studies by whether they agree, look for the explanation of disagreement in the methods rather than in the authors, and write two or three sentences stating what the evidence collectively supports and at what strength. Vote counting, where four positive studies beat two negative ones, is not synthesis.

6. Choose against your own microsystem constraints

   Write the choice as a comparison: this component rather than that one, because the second requires staffing the site does not have on four days out of five. A feasibility argument grounded in the operational profile you already wrote is what distinguishes a capstone from a paper.

A layout and word budget for an evidence and selection paper

Our frame for the written argument that surrounds the table, sized for roughly 1,400 to 1,700 words plus the table itself. It is our own outline rather than anything the university issues, and your scoring guide outranks it wherever they disagree.

Evidence craft for an improvement literature set

Grade the evidence with a named system and say which one. Levels of evidence and strength-of-recommendation frameworks are published tools; adopting one and applying it consistently lets a reviewer follow your reasoning. Applying a homemade scale, or applying a real one to only half the table, both read as improvisation.

Report effects in units a clinic would recognize. Eleven more completed screenings per hundred eligible visits means something to a practice manager. A statistically significant improvement means almost nothing. Where a study gives only a proportion, convert it into the count your own volume would produce, and label that clearly as your calculation.

Treat single-site improvement reports as feasibility evidence. They are the most common form of literature in this space and they carry genuine information about how a change behaves in a real clinic. What they cannot do is rule out everything else that changed at the same time. Use them to argue deliverability and use stronger designs to argue effect.

Name the setting gap out loud. If the best study ran in an academic pediatric center with a dedicated care coordinator, say so, and say what that means for expected effect in a two-provider practice. Reviewers do not penalize an honest transfer argument; they penalize silence about a difference the reader can see immediately.

Keep every table row traceable. The citation in a row must match the citation in the reference list, and every source in the list must appear somewhere in the text or the table. Mismatches between table, text and list are a common quiet source of lost points in capstone documents because they suggest the table was assembled from abstracts.

Five mistakes that cost points in this week's territory

• The table that is really a bibliography. Rows with author, year and a one-line summary do no comparative work and cannot support a selection argument.
• Choosing the intervention first. Evidence gathered to defend a decision already made is visible in the search paragraph, because the search returns only supportive work.
• Bundles reported as single interventions. Saying reminders improved completion, when the study also added standing orders and staff training, misdescribes what would need to be implemented.
• No feasibility link. A selection that never references the staffing and volume you documented reads as a literature exercise rather than a capstone decision.
• Silence about contrary findings. Ignoring the studies that found nothing is both a credibility problem and a missed chance to explain why context changed the result.

Before you submit

• The structured question appears before the search description
• Databases, terms, limits and screening counts are all recorded
• Every table row carries design, setting, intervention detail, outcome and effect size
• Evidence is graded with a named and cited system, applied to all rows
• The chosen component is justified against your own staffing and record capability
• Rejected alternatives are named with the reason for rejection

Questions students ask about this stage

Keep going