NURS 8100 Week 1 planning manual

1. Capture the live Week 1

Open the registered classroom and create one row for every visible activity. Record its exact name and type, complete action verbs and questions, rubric or scoring criteria, points and course weight, due date and time zone, required and permitted resources, length and format, discussion reply rules, dependencies, attempt limits, submission location, and instructor announcements. Save the rubric version beside the working file.

Reading the rubric row by row for the first time

Open the rubric before the prompt and read every row twice. The first pass looks only at the noun each row names: a problem statement, an analysis, a comparison, a recommendation, a set of citations, a format. The second pass looks only at the verb and the level it implies, because describe sits below analyze, analyze sits below evaluate, and a row that says evaluate will not be satisfied by a well written description.

In a policy and analysis course the rows usually separate the population and baseline from the determinant analysis and from the recommendation, so a single flowing narrative that blends all three can land thin on every row at once. Beside each row write the one sentence you intend it to score, and note where that sentence will live in the finished piece. Then look at the weighting: the row carrying the largest share is telling you which kind of thinking the instructor most wants to see, and it deserves the first and longest working session. Your classroom rubric decides the actual rows, levels, wording, and weights for this Week, and nothing here replaces reading it inside the registered classroom.

2. State the Week's reasoning question

For Healthcare Policy and Analysis, the durable class question is: Which population, determinant, stakeholder, and measurable outcome define the problem? Translate the live activity into one sentence that names the decision or explanation, the required evidence, the audience, and the expected output. If that sentence cannot be written, return to the prompt instead of guessing from a prior Week or third-party example.

3. Build the work in proof order

Define the population and baseline, trace determinants and system constraints, compare interventions, and connect the recommendation to implementation and evaluation.

Make a rubric-to-evidence matrix before prose: one row per criterion, the evidence or reasoning needed, where it will appear, what the student must personally do, and the test that will prove completion. Draft the highest-risk row first, not necessarily the introduction. Protect time for replies, calculations, format conversion, approvals, and the final upload.

Walking the method once on scratch before anything is graded

Week 1 is the only Week where the course method can be run with nothing at stake, so run it. Take a problem you already understand and push it through the four moves the class uses. Name a population precisely enough that someone could count it: not older adults, but an age band with a coverage status, a geography, and a care setting attached. Write the baseline as a number with a source and a date beside it, or write baseline unknown and treat that phrase as a finding rather than a hole to cover.

Next, split determinants into two columns. One column holds what sits upstream of care: income, housing, transportation, language, education, insurance status. The other holds what sits inside the delivery system: staffing, referral pathways, payment rules, screening workflows, and what the data system actually captures. Add a third column for constraints, and make it name the decision holder, the statutory or contractual authority, and the budget or workforce ceiling.

Finally, choose one outcome measure and one process measure that would move first if the problem were addressed. The dry run costs under an hour and shows which of the four moves you cannot yet perform, which is precisely the information an orientation Week is supposed to produce.

4. Use evidence deliberately

Use current surveillance, policy, organizational, and peer-reviewed evidence at the same geographic and population level as the claim.

For every source, write a one-line use note before drafting. Distinguish direct evidence from interpretation and local observation. Quote sparingly, paraphrase from understanding, and cite the claim actually supported. If the activity requires current evidence, confirm publication dates and whether an older foundational source is still appropriate.

Building the source shelf: what counts as scholarly in health policy analysis

Scholarly in this subject is layered rather than binary, and Week 1 is when the layers get set up. Surveillance and administrative datasets establish who and how many. Peer-reviewed studies establish mechanism, effect size, and the conditions under which an effect held. Statutes, regulations, and agency guidance establish what is permitted and who is authorized to act. Organizational and professional reports establish whether an option is operationally realistic. An advocacy brief or trade article may sharpen how a problem is framed, but it should not be the load-bearing citation under a claim about incidence or effect.

Match the level of the source to the level of the claim, since national prevalence cannot carry an assertion about one county and a single-site study cannot carry an assertion about a state program. Start a source register this Week with columns for the citation, the date, the design or authority, the population and setting, the one usable finding, the limitation, and the exact sentence the source will support. That last column is the discipline: write the sentence first, then attach the source that earns it. Any entry whose sentence column stays empty does not belong in the reference list.

5. Complete discussions and collaborative work

When the live Week contains a discussion, schedule the initial post by its own deadline and each reply by the response window. A useful reply does more than agree: compare evidence, apply the peer's idea to a different context, identify a boundary, or ask a focused question supported by the course material. The student writes and posts every contribution; a tutor may critique clarity and reasoning before submission.

6. Protect identity, practice, and research boundaries

Do not share protected health information, employer secrets, client identities, private peer content, assessment security material, or unauthorized research data. Clinical encounters, field hours, simulations, observations, interviews, group participation, proctored work, residencies, approvals, attestations, and original data collection must be completed and recorded by the student under the applicable Walden process.

7. Run the Week 1 quality gate

Test equity, feasibility, stakeholder effects, measurement validity, unintended consequences, and the boundary between association and causation.

Then perform a literal instruction audit: every prompt part answered, rubric row visible, calculation reproducible, citation matched, heading and format correct, accessibility checked, file opened successfully, and confidential material removed. Compare against the current rubric, not a saved rubric from another section or term.

Three Week 1 pitfalls and the fix for each

The first pitfall is treating orientation as reading. A student scrolls the syllabus, feels informed, and begins drafting with nothing written down. The fix is to make the capture table the actual output of the first sitting, and to refuse to open a draft file until every column in it is filled from the live classroom.

The second pitfall is a problem statement about a condition instead of a population. Wording such as poor medication adherence is a topic rather than a problem a policy could address, because it carries no denominator and no boundary. The fix is to rewrite until the sentence contains a counted group, a setting, and a time frame, then confirm that a real data source could verify it.

The third pitfall is committing to a topic before checking whether evidence exists at the level you chose. Students discover several Weeks later that no accessible baseline reports at the level they named, and by then the argument has been built on it. The fix is to spend twenty minutes now confirming that at least one credible baseline source reports at your stated level, and to narrow or widen the scope immediately if it does not, while nothing has been written.

8. Submit and close the loop

The student performs the final upload or entry, opens the submitted artifact, confirms the timestamp and file, and saves the receipt. When feedback arrives, record each criterion result, instructor comment, correction, and lesson for Week 2. Contact the instructor or official support channel promptly for a missing, late, or technically failed submission.

9. Defend the learning before moving on

Before closing Week 1, the student should explain the live task, central claim or decision, strongest evidence, method or calculation, important limitation, and next action aloud without reading the submitted artifact. For a discussion, explain what the peer exchanges changed. For clinical, field, research, group, or proctored work, identify which parts the student personally performed and how they were verified. Any point that cannot be explained becomes the first short practice item for the next study session. This oral defense tests understanding more honestly than another formatting pass and turns the finished Week into preparation for Week 2.

Source boundary

Walden's current catalog verifies this Course-Based class context, and the quarter calendar supports positional Weeks. The public catalog does not identify the student's Week 1 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 1 questions