NR-702B · Week 1 of 8 · Problem, setting and the 192-hour scope

NR-702B Week 1 Problem, Setting and Scope: How to Write It

The short answer

NR-702B carries 3 practicum credits and 192 clinical hours, and the opening written work in a stage like this is the definition of a practice problem that the rest of the sequence will be built on. The extra hours over the shorter variant buy depth rather than a different assignment, and at this stage depth usually means a problem defined tightly enough that the evidence work which follows has something exact to answer. Your section may print this as NR 702B or NR702B; 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 702B Week 1 grading scale at Chamberlain, the criterion levels this assessment is scored on, from Chamberlain Tutors
How Chamberlain grades NR 702B Week 1, visualized by Chamberlain Tutors.

What NR-702B Week 1 asks for

Where does a doctoral practice problem actually come from? Almost never from a literature search. In a hospital-based outpatient infusion center, the charge nurse can tell you within a minute that peripheral access attempts fail repeatedly on the same group of long-course patients, that each failure costs a chair slot, and that nobody has ever counted it. That last clause is the doctoral opening. A practice problem is a shortfall someone lives with daily, expressed as a measured distance between what happens and what should happen, in a setting small enough to change. Your first written deliverable is the act of converting a known frustration into that measured form.

The second thing this stage asks is that you frame the work correctly as translation. A practice doctorate project takes evidence that already exists and moves it into a setting that is not yet using it. It does not generate new knowledge, it is not a dissertation, and describing it in those terms distorts every section that follows, because it puts the literature in the role of exposing a gap rather than in the role of justifying an intervention. The sentence that signals you understand this is simple: the evidence supports doing X, this site does not do X consistently, and the size of the shortfall is this. Everything after that is design.

Third, this stage asks for scope proportionate to 192 hours across an eight-week session. That is roughly twenty-four hours a week for someone who is very likely also working clinically. It is more room than a two-credit block affords, and the honest use of that room is depth on the evidence and the planning rather than breadth in the problem. A wider problem does not become feasible because the hour load rose; a deeper, better-supported plan for a narrow problem does become possible, and that is the distinction faculty read for in an opening submission.

The boundary that governs every page in this manual. Clinical hours, hour logs, encounter counts, site documentation, preceptor evaluations and signatures are the student's own record and the site's. They are never drafted, reconstructed or estimated with help from anyone, and no tutor performs, observes or documents clinical activity on a student's behalf. What can be supported is only the written layer around real work you did: defining a problem, structuring an argument, appraising sources in prose, writing a reflection that analyzes rather than narrates. De-identify every patient detail before it reaches a page, and describe your site by type and size rather than by name.

The NR-702B Week 1 method, step by step

Seven moves for converting a clinical shortfall into a defensible doctoral problem.

  1. Split the rubric into administrative rows and scholarly rows

    Practicum criteria mix hours, site agreements and supervision with the graded written product. Separate them in a working file. Only the scholarly half gets a word budget, and it is usually a smaller share of the page count than students expect.

  2. Write the setting as a service, not an institution

    A twelve-chair outpatient infusion service running four days a week with two infusion nurses per shift is a setting. A health system is not. Size, staffing and volume let a reader judge feasibility, and they avoid naming the organization.

  3. Name the shortfall in the language of a count

    Something happening to a number of people out of a number of eligible people over a defined period. If the count does not exist yet, write the sentence with gaps and treat closing them as the first substantive use of your practicum time.

  4. Find the standard your site is falling short of

    A national quality measure, a professional society recommendation, an accreditation requirement, or your organization's own written policy. Name the issuing body and the version year inside the sentence, because a target with no parent is an opinion.

  5. Express the gap in patients rather than percentage points

    A thirty-point shortfall means nothing until it becomes roughly ninety patients a year who did not receive something the evidence supports. That conversion is the single most effective sentence-level move in doctoral problem writing.

  6. Establish that a solution family already exists, without appraising it yet

    One or two citations showing that interventions of this type have been reported to work. You are not proving the choice this week; you are demonstrating that this is a translation problem rather than an unanswered clinical question.

  7. Cost the problem against the hours you actually have

    Ask what would need to happen for the change to be attempted and measured. If the honest answer involves a purchase, a hire or a decision by a committee that meets quarterly, narrow now. A 192-hour block buys depth, not permission.

A layout and word budget for the opening problem deliverable

The frame our doctoral bench uses at this stage, sized for roughly 1,400 to 1,700 words, which suits the deeper written work a three-credit block can carry. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.

SectionWhat belongs in itWord target
The shortfall, stated firstBoth numbers and the gap between them, before any context about the condition or the literature.100 to 130
Service described by capacityChairs, sessions, staffing pattern, weekly volume, population served, and the workflow the project touches.170 to 210
How the number is knownThe source of the baseline, its period, and how confidently it can be produced again after a change.200 to 250
Standard being missedThe benchmark with its issuing body and year, and what the standard is trying to prevent or achieve.150 to 190
Consequence for these patientsWhat the gap costs the people in your denominator, in clinical and operational terms rather than national ones.200 to 250
Evidence exists, brieflyTwo or three sources establishing that an intervention family has support, flagged for full appraisal later.170 to 210
Scope against 192 hoursWhat this term can carry, what belongs to later courses, and what the project explicitly excludes.180 to 220

Evidence craft for a doctoral problem statement

Lead with the local number and let national data play support. Statistics about prevalence establish that a condition matters; they do not establish that your service has a problem. The order that scores puts your figure first and the wider context second, in a single paragraph, and students who reverse it almost always run out of words before the section that is actually being graded.

Give every figure a retrieval path in your notes. Beside each number, record where it would come from: a report someone runs monthly, a scheduling extract, a device or infusion log, a chart audit you would have to perform under your own access. Numbers with no route become promises you cannot keep in the implementation course.

Attribute and date standards inside the sentence. Quality measures are respecified, guidelines are revised and organizational policies are reissued. Naming the body and the year in the text is what lets a reader judge whether your benchmark is current, and it protects you from defending a threshold that moved.

Keep intervention language provisional at this stage. Write that a body of work reports benefit, not that an approach works. Committing to a solution before the appraisal is done tends to produce a synthesis written to defend a decision, and readers recognize the shape of that argument quickly.

De-identify aggressively, including the site. Where a specific encounter prompted the problem, use it stripped of name, date and any combination of details that would identify a person in a small service. Describe the setting by type and size, and if a subgroup in your data is small enough to expose an individual, report it at a coarser level and say why.

Five mistakes that cost points in this week's territory

  • A topic in place of a problem. Vascular access complications is a subject; a counted failure rate in a named type of service over a defined quarter is a problem a project can move.
  • Dissertation framing. Language about investigating, discovering or testing a hypothesis reframes a translation project as research and misplaces the role of the literature.
  • A benchmark without a source. Targets that appear from nowhere cannot be checked, so the gap they define cannot be scored.
  • Scope inflated by the extra hours. A three-credit block funds deeper work on a narrow problem, not a broader problem, and confusing the two produces a plan that cannot be delivered.
  • Background crowding out the site. Half a paper on national epidemiology and two sentences on the service is the inversion that most reliably caps an otherwise sound opening submission.

Before you submit

  • The gap and both of its numbers appear in the opening paragraph
  • The setting is described by capacity, staffing and volume, never by name
  • The baseline carries a numerator, a denominator and a time window
  • The standard names its issuing body and the version year in the sentence
  • The consequence is expressed as patients affected in your own denominator
  • At least one source signals that an intervention family already has support
  • A scope paragraph states what 192 hours will and will not carry
  • Nothing in the paper could identify a patient, a colleague or the service

Opening NR-702B this week?

Send the rubric out of Canvas with whatever baseline figures you can reach. A premium original draft comes back in 24 to 48 hours with the shortfall stated in counts, the benchmark attributed, and the scope honestly sized to your hours, and revisions run until the grade lands.

Questions students ask about this stage

Does the larger hour load mean my project should be bigger?
Not wider, deeper. The additional hours in a three-credit block are best spent on work that makes the same project more defensible: a more thorough evidence search, an appraisal that reaches verdicts rather than summaries, a readiness assessment built on conversations with people who own the workflow rather than on assumption, and a measurement plan tested against what the data system can actually produce. A broader problem does not become feasible because you have more hours, because the constraint on breadth is the site's capacity to absorb change, not your time. Committees consistently reward a narrow project supported to the hilt over an ambitious one held together by optimism, and the narrow version is also the one that survives the implementation courses.
What if I inherit a problem my department has already chosen for me?
That is common and workable, provided you do the bounding yourself. Departments hand students problems in the vocabulary of goals rather than gaps, and your task is to convert what they have given you into a measurable form and then check that the measurable form is deliverable. Occasionally the conversion reveals that the department's problem is really three problems, or that the part they care about most is out of reach in your window. Write what you found, propose the bounded piece you can carry, and say in a sentence how it relates to the larger ambition. That is a professional response, and it usually strengthens rather than damages the relationship, because you are handing back something concrete rather than a broad aspiration.
Can anyone help with my hour logs, site forms or preceptor paperwork?
No, and the answer does not change with the framing. Hours, logs, encounter records, site agreements and preceptor evaluations are documents the university and your site verify, and having anyone else complete, reconstruct or estimate them is an integrity problem rather than a service. The clinical experience itself cannot be shortcut. What is legitimately supportable is the written layer: bounding the problem, structuring sections, appraising sources in prose, tightening register to doctoral level, and making sure a reflection analyzes rather than recounts. If you are ever offered help that touches the verified layer, treat the offer itself as a warning about the source.
How do I know the problem is doctoral rather than a unit improvement task?
A useful test is whether the change requires translation judgment or only effort. If the fix is obvious, uncontested and simply undone, it is a task: order more supplies, fix a broken printer, remind people. If it requires you to select among competing evidence-supported approaches, adapt one to a setting that differs from where it was studied, plan for adoption by people who have reasons not to adopt, and evaluate whether it worked without the tools of a trial, then it is doctoral work. The second test is systems altitude: a doctoral problem usually touches workflow, roles, policy or data infrastructure rather than one person's behavior. If your problem passes neither test, keep the setting and look one level up, since the underlying structural issue is often the real project.

Keep going

Online now