NR-662 Week 1 Immersion Plan and Problem Statement: How to Write It

What NR-662 Week 1 asks for

Picture the setting most of these projects actually live in. A family medicine practice with a pediatric panel discharges a child after an asthma visit, and the parent leaves with a rescue inhaler, a follow-up card and no written action plan. The clinicians know an action plan should go home. Everyone would say so out loud. It still does not happen on roughly half the visits, and nobody in the building can tell you the number without pulling charts. That gap between what a team believes it does and what the record shows it does is the raw material of a process improvement capstone, and the opening stage of this course is where you convert it into something writable.

The written work at this stage typically has two halves. The first is a plan for your 144 hours: where you will be immersed, who the experienced person guiding you is in role terms, what you intend to learn about the advanced role, and how the hours will be shaped so the project fits inside them. The second is a problem statement: a specific process, in a specific place, with a specific undesirable result, attached to a number that came from somewhere real. Some sections also open a discussion where you post your proposed problem for peer response. Treat that post as final copy, because in Canvas a posted response does not reopen, and a project idea described vaguely in public is harder to narrow later than one described precisely from the start.

The trap in an opening capstone stage is scale. Students arrive with a problem the size of a service line, readmissions, burnout, access, and try to shrink it in week five when the measure will not cooperate. A capstone-sized problem is one process, one population, one measurable behavior, in a unit small enough that you can see the whole of it. Missing asthma action plans for children aged five to eleven at one clinic site is a capstone. Improving pediatric asthma outcomes is a career.

The boundary, stated once and meant. The 144 clinical hours in this course are yours and only yours. The immersion, the conversations at the site, the observation of the advanced role, the relationship with whoever is guiding you, all of that is real work that cannot be delegated, shortened or reconstructed. Hour logs, encounter counts, site paperwork, signatures and any evaluation completed about you are your own record, and they are never drafted, estimated or reconstructed with help from anyone. What a manual like this supports is the written layer that surrounds the immersion: how to state a problem so it can be measured, how to structure a plan document, how to make an argument a reviewer can follow. Where your writing draws on anything you saw at the site, every patient detail is de-identified before it reaches the page.

The NR-662 Week 1 method, step by step

Six moves that take a vague clinical irritation and turn it into a capstone problem statement.

1. Read the scoring guide before you fall in love with a topic

   Copy each row into a blank document and reduce it to the verb it demands. A row asking you to justify wants a reason with a source behind it. A row asking you to define wants boundaries. Projects fail their opening stage far more often for missing a required element of the plan than for choosing a weak problem.

2. Describe the process as a sequence, not as a complaint

   Write the current state as numbered steps from trigger to end point: child presents, provider assesses, plan is or is not generated, plan is or is not printed, plan is or is not explained, visit closes. A complaint cannot be improved. A sequence has places where a change can be inserted.

3. Attach one local number to the gap

   Say how many out of how many, over what window, from what source. Fourteen of thirty-one charts reviewed across one month is a defensible baseline sentence. High rates of missing documentation is not, and a grader reading a capstone plan is specifically watching for whether the problem has been counted or only asserted.

4. Name the population and the boundary of the project

   Which patients, which clinicians, which site, which shifts or clinic days. State plainly what is outside the project as well. A boundary written down in week one is the sentence you will quote to yourself in week five when someone suggests adding a second location.

5. Write the significance in two currencies

   Clinical and organizational. What the gap does to the child or the family, and what it costs the practice in avoidable visits, staff time or quality reporting. Capstone readers expect a project to matter to the organization, not only to the patient, because that is the argument the advanced role has to make in real rooms.

6. Draft the immersion plan around the project timeline

   Lay your hours against the eight stages: assessment early, evidence next, baseline before any change, implementation in the middle, measurement after. State how many hours you expect each phase to take and what you intend to learn about the advanced role during it. This is a plan, so it is allowed to be revised, but it must be specific enough to be revised against.

A layout and word budget for an opening capstone plan

The frame our tutors keep beside a first capstone document, sized for roughly 1,200 to 1,500 words. It is our own outline rather than anything the university issues, and your week's scoring guide outranks it wherever the two disagree. Scale each target proportionally if your assigned length differs.

Evidence craft for a capstone problem statement

Separate the local number from the published number. Your chart review says fourteen of thirty-one. The literature says action plan delivery in ambulatory pediatric settings is inconsistent. Those are different claims doing different jobs, and a paragraph that blends them lets a reader think you counted something you read. Give the local figure its own sentence with its own source, then use published work to say the pattern is not unique to you.

Cite guidance for the standard, not for the problem. The reason a missing action plan matters is that a recognized body of guidance says one should be provided. Name the guidance and give it a year in the sentence. Standards are revised, and a recommendation quoted without a date is a claim about the present made from an unknown moment.

Prefer counts with denominators to percentages. Forty-five percent sounds authoritative and hides how many charts you actually looked at. Fourteen of thirty-one tells a reader immediately how much weight the figure can carry, and honest smallness in a baseline is not a weakness in a single-site capstone. It is the truth about your sample, and stating it protects every claim you build on top.

Keep interviews as context, never as data. What staff told you about the workflow is valuable and belongs in the setting description, clearly labeled as what team members reported. It is not a measurement, and presenting perception as baseline is one of the fastest ways to lose the evidence row in a capstone document.

De-identify while you draft, not afterwards. Names, dates of birth, exact visit dates, employee identifiers and anything that would let a reader locate a specific child do not belong in the document at any stage. Write the anonymized version first, because a draft that ever contained identifiers has to be handled as if it still does.

Five mistakes that cost points in this week's territory

• A problem too large to measure. If you cannot state the numerator and denominator of your baseline in one sentence, the project is not yet a project.
• Solution written before problem. Plans that open by announcing a chosen intervention read as an idea looking for evidence, and capstone readers spot the ordering immediately.
• An immersion plan made of adjectives. Meaningful experience and exposure to leadership describe nothing. Phases, hours and observable role activities do.
• Borrowed baselines. A national statistic used as your site's starting figure means there is no local problem established, and every later comparison becomes uninterpretable.
• No stated boundary. A project without an explicit edge grows all session, and the growth shows up as a measurement plan that cannot be completed in eight weeks.

Before you submit

• The problem names one process, one population and one site
• A local baseline appears with numerator, denominator, window and source
• Significance is argued in both clinical and organizational terms
• The standard being missed is cited with an issuing body and a year
• The immersion plan assigns hours to phases across the session
• No identifiable patient, staff or site detail appears anywhere in the document

Questions students ask about this stage

Keep going