HLTH 3100 Week 9 planning manual

1. Capture the live Week 9

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.

2. State the Week's reasoning question

For Ethical and Legal Issues in Healthcare, 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.

Building the spine of a larger artifact

When the closing Weeks concentrate the work into a longer deliverable, the question stops being what to write and becomes what order to prove it in. Build the spine before the prose. Write the central claim in one sentence. Under it, list the three to six propositions that must be true for the claim to hold, in the order a reader would need them. Under each proposition, name the evidence that establishes it and the section of the artifact where it will live. What results is a document map that can be checked for gaps while gaps are still cheap to fix.

Then test the spine two ways. Read only the proposition lines in order and ask whether they add up to the claim without help. Then read only the evidence lines and ask whether any proposition is resting on nothing. Fix the structural problems now, since a missing proposition discovered during drafting usually costs a full section. Nothing here specifies what your section requires, and your classroom rubric decides the artifact's required parts, order, and length.

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.

Reading the rubric row by row to sequence the final work

Late rubrics are usually longer, and reading them in print order wastes the calendar. Extract the rows into a working list with four columns: the row, its points, whether it depends on another row being finished, and how long it will take. Then order the work by dependency first and weight second. Rows that synthesize, that evaluate the whole, or that judge coherence cannot be completed until their inputs exist, so they are scheduled last but planned first.

Mark separately every row depending on something outside your control: a group contribution, an approval, an instructor response, a scheduling or proctoring step, a technical submission requirement. These belong in their own lane with earlier internal deadlines, because an unfinished institutional step cannot be repaired by working faster on the writing. Confirm the submission route and file requirements now rather than on the due date. The rubric attached to the live activity is controlling, and your classroom rubric decides.

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.

Closing source gaps before the drafting crunch

A long artifact fails on evidence in a specific way: the early sections are well supported because they were written when there was time, and the later sections thin out. Prevent it by resolving the source list against the spine before drafting. Walk the propositions in order and mark each as supported, partly supported, or unsupported. Fill the unsupported ones first, since finding an authority or a study takes hours you will not have later.

While filling, apply the same standards the course has used all term: the governing text for a rule, peer-reviewed material for population claims, current organizational or surveillance material for a local baseline, and a stated level match between claim and source. Then decide what to cut, because a source supporting a proposition you have decided not to make is clutter rather than a reserve. Build the reference entries as you go rather than at the end, and keep a use note beside each so the final pass can verify that every entry did work.

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 9 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 9 pitfalls and the fix that closes each

The costliest one is discovering an institutional step late. An approval, a group dependency, a scheduling requirement, or a technical setup surfaces after the writing is done and no calendar is left. The fix is to read the remaining Weeks' instructions in full now, list every step requiring another party, and start those first.

The second is a reference list assembled at the end. Entries get built from memory, locators go missing, and citations in the text stop matching. The fix is to create the entry at the moment of first use and to keep the text and the list in the same file.

The third is leaving the heaviest row for last. The row worth the most is usually the one requiring synthesis, and synthesis done under deadline pressure is the first thing to read as thin. The fix is to draft that row early in outline form, even before its inputs are finished, so the final pass is a revision rather than a first attempt.

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 10. 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 9, 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 10.

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 9 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 9 questions