The closing stage of NR-715 usually asks you to assemble everything the session produced into one coherent concept for a scholarly project: the problem, its magnitude, the evidence available to translate, the framework that will carry it, the setting and its stakeholders, a preliminary evaluation idea, and a plan for reporting the work to people who can act on it. This is a concept, not a protocol. It commits you to a direction and to the reasoning behind it, and it is the document your later project courses will build from. Your section may print this as NR 715 or NR715; 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-715 Week 8 asks for
Return to a familiar shape from ambulatory pediatrics: children identified at a well-child visit as needing nutrition or weight management support, referred to a service, and then never seen there. The referral is placed, the family receives a phone number, and roughly a third of the loop closes. Across a session, a student has counted the gap, found guidance recommending structured follow-up, chosen a framework that emphasizes context assessment, and mapped who controls the scheduling template. The concept paper is where those pieces become one argument that a reader can accept or challenge as a whole.
Integration is the actual difficulty. Most students arrive at this stage with six correct sections that do not agree with each other: a problem statement about one population, an evidence scan about a slightly different one, a framework whose stages nobody has mapped onto the plan, and an evaluation idea measuring an outcome the problem statement never mentioned. A doctoral reader reads for that alignment before anything else, because misalignment at the concept stage guarantees an expensive correction later.
The second demand is honesty about status. A concept paper is allowed to say that data access is unconfirmed, that a sponsor has not yet agreed, or that the intervention will be chosen after a fuller appraisal. Writing those as known limitations with a plan attached reads as competence. Writing them as settled when they are not is the single most common reason a concept has to be rebuilt.
The third demand is the dissemination layer, which students consistently underweight. A practice doctorate produces change plus a report that lets somebody else sustain or repeat it. Naming the audiences and the products now, at least in outline, keeps the project pointed at practice rather than drifting toward a paper nobody outside a gradebook will read. Expect a concept or prospectus-style paper, sometimes with an appendix table, and often a final posted reflection.
The NR-715 Week 8 method, step by step
Six moves for assembling a concept that holds together.
-
Run an alignment pass before you write a word of new prose
Put your population, your gap, your evidence, your framework and your intended measure in five lines on one page. If any two disagree about who or what is being changed, fix that before drafting. This pass takes twenty minutes and prevents most rewrites.
-
Compress the problem into one paragraph that could stand alone
Population, setting, standard, local rate with its base, and consequence. A concept paper is read by people who will not have read your earlier work, and a problem paragraph that needs context to make sense will be judged as if it were the whole argument.
-
Summarize the evidence by what it supports, not by who wrote it
Group the literature into the two or three things it consistently shows, and say which of those your setting could adopt. An annotated list of studies is a reading log; a statement of what the body of evidence supports is a translation argument.
-
State the intended change at the level of a process step
Say what would be different in the workflow, who would do it, at which point, and with what support. Concepts written at the level of improve follow-up cannot be evaluated and cannot be sponsored.
-
Sketch the evaluation as measures, sources and comparison
Name one process measure, one outcome measure and one balancing measure, with where each would come from and what you would compare against. Keep it preliminary and say so, but make it concrete enough to criticize.
-
Write the risks and the dissemination plan as real sections
Two or three genuine risks with mitigations, then the audiences and products: a report to the practice, a presentation to the group, materials that outlive your attention. These sections are short, they are frequently skipped, and they are where a concept starts reading like a doctoral one.
A layout and word budget for a project concept paper
Our frame for a closing concept, sized for roughly 1,800 to 2,400 words. 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 |
|---|---|---|
| Concept in brief | The problem, the intended change and the expected benefit in one paragraph a busy reader could act on. | 120 to 160 |
| Problem and magnitude | Standalone problem paragraph with local count, denominator, period and national significance. | 250 to 300 |
| Evidence available to translate | What the body of literature consistently supports, at the level of guidance and synthesis, with the strength stated. | 300 to 360 |
| Framework and its role | The chosen model, what job it does in this project, and the stages it will govern. | 200 to 250 |
| Setting, stakeholders and readiness | Where the work would happen, who controls it, what support exists and what does not. | 250 to 300 |
| Intended change and preliminary evaluation | The process step that changes, plus process, outcome and balancing measures with their sources. | 300 to 360 |
| Risks, ethics and dissemination | Real risks with mitigations, the approval steps you will follow, and the audiences and products at the end. | 240 to 300 |
Evidence craft for a concept paper
State the strength of the evidence, not only its existence. A concept that says several studies support this has told a reader nothing about whether the support is a systematic review or three single-site reports. Characterize the body: what kinds of evidence, how consistent, and how close to your population.
Keep the local figure identical everywhere it appears. The same count, denominator and period should appear in the brief, the problem section and any table. Numbers that drift between sections are the fastest way to lose a reader's trust in a document meant to be read whole.
Describe approvals as a process you will follow, never as an outcome. Say that the work will go through your organization's and your program's determination and review steps before implementation. Do not state or imply what any review body will decide, and do not label the project as exempt yourself.
Name what a site-level evaluation cannot establish. Your design will show change over time in one setting where other things also changed. Writing that limitation plainly, once, is worth more than any amount of hedging spread across the discussion.
Give the dissemination products real names. A written report to the practice leadership, a one-page workflow card for rooming staff, a presentation to the group's clinical meeting, and a submission to a practice-facing publication are products. Dissemination as a bare noun is not.
Five mistakes that cost points in this week's territory
- Sections that disagree with each other. A population defined one way in the problem and another way in the evaluation is the most expensive error available at this stage.
- Evidence listed rather than characterized. A parade of citations does not tell a reader how strong the case for translating is.
- An intended change written as an aspiration. Improve referral completion cannot be implemented. A defined step, owner, timing and support can be.
- Approval outcomes assumed. Any sentence implying a review determination has been made, or will be made a particular way, is a fabricated fact and reads as one.
- No dissemination and no sustainment. A concept ending at implementation has described half a practice doctorate, and the missing half is the half that distinguishes the degree.
Before you submit
- Population, gap, evidence, framework and measure all refer to the same thing
- The problem paragraph stands alone without the rest of the document
- The local figure is identical in every place it appears
- The evidence base is characterized by strength and closeness to your population
- The intended change is written at the level of a process step with an owner
- Process, outcome and balancing measures each name a data source
- Approvals are described as steps to be followed, with no outcome implied
- Dissemination products and audiences are named concretely
Assembling your NR-715 concept paper?
Send the rubric and your earlier sections out of Canvas. A premium original draft comes back in 24 to 48 hours with the alignment pass done and the evaluation written to be criticized, and revisions run until the grade lands.