An evidence-based project stands or falls on whether its evidence was gathered systematically or collected until it agreed with the plan. The written work at this stage is a documented search: databases, terms, limiters, yields, screening passes and the final set, written so that a stranger could run it again and recover what you found. Your section may print this as NR 611 or NR611; 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.
What NR-611 Week 4 asks for
Watch what happens when the search is done backwards. A student running a project on adolescent immunization completion in a family practice already believes reminder texts are the answer, searches for reminder text messaging and adolescent vaccination, finds nine supportive studies, and writes them up. The set looks strong and it is worthless, because nothing in it could have disconfirmed the plan. The systematic version starts from the question written in the previous stage, searches the category rather than the product, and returns a mixed picture in which reminders help modestly, standing orders help more, and the combination has been tested rarely. That mixed picture is a better project, and it only exists because the search was built to find it.
Population health widens the evidence base beyond clinical trials, and knowing which shelf to search is part of the graded skill. Practice guidelines from professional bodies, systematic reviews, agency recommendations, quality improvement reports and program evaluations from public health departments all carry different kinds of authority. A project proposal needs several of these categories rather than nine articles of the same type, and the write-up should say what each category contributed.
The boundary in this course does not move. Support covers the written and preparatory layer only. Practicum hours, hour logs, encounter and contact counts, mentor evaluations, site documentation and signatures are your own record of work you personally performed, and they are never drafted, reconstructed or estimated with help. No one contacts your mentor, your site or a community partner on your behalf. Nothing in a search log or an evidence table should contain patient information; where an example from the immersion clarifies why a question mattered, it appears de-identified and as a pattern rather than as a person.
The NR-611 Week 4 method, step by step
Six moves for a search a reviewer could reproduce.
-
Start from the question, not from the plan
Take the structured question exactly as written in the previous stage and build the concept blocks from its elements. Any term that does not come from the question needs a stated reason.
-
Search categories rather than named programs
Reminder systems, standing orders, outreach models. Searching for the specific product you hope to implement guarantees a confirming set and forfeits the appraisal row.
-
Map concepts to controlled vocabulary in each database
Subject headings differ between indexes, so build the strategy separately in each and combine headings with free text. Say in the write-up which terms were headings and which were keywords.
-
Search the grey literature deliberately
Agency reports, state health department program evaluations and guideline repositories carry material that indexed journals do not. Record how you found them with the same discipline as a database search.
-
Log every step with its yield as you go
String, database, limiters, count. Written afterward, these numbers never hold together, and an implausible descent through a log is the most detectable weakness in this assignment.
-
Screen in two passes and report the attrition
Titles and abstracts, then full text, with counts surviving each pass and two or three stated exclusion reasons. A reader should be able to follow every record from the initial yield to the final set.
A layout and word budget for a documented search
Our frame for the search section of a project proposal, sized for roughly 1,100 to 1,400 words plus the log table. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Question restated | The structured question with each element defined, plus what kind of evidence would count as an answer. | 110 to 140 |
| Sources chosen | Which databases and which grey literature repositories, each with a reason tied to your question's subject matter. | 180 to 220 |
| Strategy | Concept blocks, controlled vocabulary against free text, how blocks were combined, and any variation between databases. | 250 to 300 |
| Limiters and their reasons | Every filter applied with the argument for it, including the date horizon and any decision to widen it. | 150 to 190 |
| Log and screening | The table of steps and yields, then the two screening passes with counts and exclusion reasons in prose. | 200 to 250 |
| The retained set | What you kept, sorted by evidence type, with one sentence on what the shape of the set implies for the project. | 200 to 250 |
Evidence craft for a project search
Name the database and the platform with a search date. The same index behaves differently through different interfaces and results change over time, so record where you were standing and when. A dated strategy is what makes reproducibility a real claim rather than a stated aspiration.
Show the descent, not the destination. The teaching value of a log is the drop between lines: several thousand records on the population block alone, a few hundred once the intervention block joins, a few dozen after the design limiter. A single final count demonstrates nothing about control.
Classify each retained item by evidence type. A systematic review, a guideline from a named body, a controlled trial and a single-site improvement report support different claims. Say which each one is on first mention rather than calling everything an article.
Give grey literature the same provenance discipline. An agency report needs the issuing body, the year and the population it covers, exactly as a journal article needs its citation. What it does not get is the assumption of peer review, so say what kind of document it is.
Report the absences. If nothing in the literature tests your intervention in a population resembling yours, that is a finding with consequences for the project, and writing it plainly earns more than pretending the fit is closer than it is.
Keep the date horizon defensible rather than habitual. A five-year window is a convention, not a rule, and in some territories it removes the trial everyone still cites. Say why your horizon fits your topic: rapidly changing delivery models justify a tight window, while a screening question resting on a decade-old body of trials does not. Where you widened the window deliberately to capture a foundational study or a guideline that has not been revised, write that decision into the strategy section rather than leaving the reader to notice an outlier in the reference list and wonder how it got there.
Five mistakes that cost points in this week's territory
- Searching for the plan. A strategy built around the intervention you already chose cannot produce evidence, only agreement.
- Yields reconstructed from memory. Counts that do not descend plausibly are the clearest signal a grader gets that the log was written after the fact.
- Keyword-only strategies. Skipping controlled vocabulary produces sets that are simultaneously bloated and missing the strongest records.
- Grey literature ignored. Population health interventions are frequently evaluated by health departments and agencies rather than in indexed journals.
- A retained set of one evidence type. Nine studies of the same design leaves the proposal unable to speak to both effect and feasibility.
Before you submit
- Every concept block traces back to an element of the structured question
- Each database is named with its platform and the date searched
- Controlled vocabulary terms are distinguished from free text
- Every log line carries its own yield and every limiter carries its reason
- Both screening passes report counts and exclusion reasons
- The retained set is sorted by evidence type and its gaps are stated
Building the search documentation for NR-611?
Send the prompt and the scoring guide out of Canvas with your problem statement and question. We work on the written layer only, never on hours, logs, evaluations or site paperwork. A premium original draft comes back in 24 to 48 hours with blocks mapped to subject headings, limiters justified and the log written so a reviewer could repeat it, and revisions run until the grade lands.