NR-667 Week 1 opens the FNP capstone, and everything the next seven weeks build rests on what gets written now: a practice gap stated narrowly enough to answer, with a population, a setting, an outcome, and a number a reader can check. Your section may print this as NR 667 or NR667; 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.
NR-667 is a precepted practicum with an on-ground intensive, and its 125 catalog hours, site arrangements and logs sit entirely inside your program's machinery. This page, like the desk behind it, works on the capstone's written spine only, and this week that spine is one paragraph that must be right.
What NR-667 Week 1 asks for
Expect the territory to center on problem definition: what separates a topic from a question, what makes a gap a gap rather than a complaint, and how the difference between current practice and best practice becomes measurable. Around that core sit the opening logistics of a capstone, choosing something feasible inside one eight-week session, and drawing the backward calendar that reserves time for the certification review this course also carries.
The deliverable shapes this week usually takes are a project proposal or topic statement, a gap analysis paragraph with supporting data, or an opening post introducing the problem your project will chase. If your section runs a discussion this week, it tends to ask for your gap in a few sentences so classmates and faculty can stress-test the scope, and since posts cannot be edited after they land, the scope you publish is the one you will defend.
Your week's rubric will most likely pay for precision: a bounded population, a named setting, an outcome that moves, and evidence that the problem is real rather than remembered.
The NR-667 Week 1 method, step by step
Six moves from a vague unease to a fundable question.
-
Start from something that repeats at your site
The strongest capstones begin as irritations: the screening that keeps getting skipped, the follow-up that never lands, the education that does not stick. Something you have watched happen more than twice is a better seed than any imported hot topic.
-
Bound it in one sentence
Population, setting, outcome: adults with the condition, in this kind of clinic, and the measure that should move. If the sentence cannot hold all three, the project is still a topic, and topics produce eight weeks of drift.
-
Attach a number someone could check
The gap becomes real when it is counted: how many of how many, over what window, from what source. A unit report, a quality dashboard, or a published benchmark all work; an impression does not, however widely shared.
-
Test it against eight weeks
Ask what must exist by the session's end and whether the intervening weeks can build it. A question needing a year of data collection fails this test however worthy it is, and discovering that in week one costs nothing.
-
Phrase the question so evidence can answer it
Recast the bounded gap as an answerable question: whether a defined change, for this population in this setting, improves the named outcome. That phrasing is what the search in the coming weeks will be built from, so its terms need to be searchable ones.
-
Draw the backward calendar, then format
Put the final deliverable's date on paper and walk backward through the drafting, appraisal and search milestones, leaving standing blocks for certification review. Then the mechanics: current APA from the first citation, headings in your rubric's wording.
A gap statement, section by section
Targets assume roughly 1,000 words for a proposal-shaped deliverable, plus the calendar. Many sections ask for less; if yours does, keep the proportions and shrink the whole.
| Section | What belongs there | Word target |
|---|---|---|
| The observed problem | What keeps happening, where you saw it, and why it matters clinically | 150 to 190 |
| The number behind it | The local count or published benchmark with denominator, window and source | 120 to 160 |
| Population and setting bounded | Who is in, who is out, and the practice environment the project lives in | 140 to 180 |
| The outcome that should move | The measurable quantity, its current value, and the direction a success would push it | 120 to 160 |
| The question, answerably phrased | The gap recast in the form the evidence search will chase | 90 to 120 |
| Feasibility and the calendar | Why this fits one session, with the backward milestones and protected review blocks | 180 to 230 |
The feasibility section is the one faculty read first even though it comes last, because it predicts whether the next seven weeks succeed. Give it real dates, not intentions.
Proving a gap with numbers that survive checking
Local data is the most persuasive footing a gap can have, and the most commonly misused. If you cite unit-level figures, describe how they were collected, over what period, and by whom, and confirm you are permitted to use them in coursework; de-identified aggregate counts are the safe currency here. Never let a number imply chart access you did not have.
Published benchmarks need their pedigree in the sentence: the organization or study, the year, and the population measured. A national screening rate drawn from a survey of large health systems may say little about a rural clinic, and naming that mismatch, then using the benchmark anyway as the best available anchor, is exactly the honest move graders reward.
Keep the arithmetic visible. A gap is a subtraction, current performance against expected performance, and both sides of the subtraction need sources. Where either side is an estimate, say so and say why the estimate is reasonable; a labeled estimate holds, while a disguised one collapses the first time a reader asks where it came from.
Five mistakes that cost points in an opening week
- A topic wearing a question mark. "Improving diabetes care" is a shelf of books, not a project; the rubric row on scope has nothing to hold.
- A gap with no denominator. "Many patients are not screened" cannot anchor a project; how many of how many decides whether the problem is real.
- Scope sized for a thesis. Anything requiring new instruments, long follow-up or multiple sites fails the eight-week test in week one, quietly, and the course collects the failure in week seven.
- An outcome nothing can measure. Awareness, empowerment and engagement move projects into territory where success cannot be shown; pick the countable proxy instead.
- A question the evidence has already closed. If strong current guidance settles it, the project has nowhere to go; the gap must live in practice, not in the literature.
Before you submit
- The problem is one you can attach to observed, repeating events
- Population, setting and outcome share a single bounded sentence
- The gap carries a number with denominator, window and source
- The eight-week feasibility case is argued, not assumed
- The question is phrased in searchable, answerable terms
- The backward calendar exists with review blocks protected
Capstone opening while clinic hours run?
Send your topic idea and the rubric. A bounded gap statement with the feasibility case argued returns inside 24 to 48 hours, floor-checked before it reaches you.