HLTH 2120 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 Health Informatics, 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.

Building the remaining-work map

Week 9 reasoning is logistical, and at the end of a quarter logistics decide outcomes more often than insight does. List every activity still visible in the registered classroom with its deadline, its weight, its dependencies, and its submission route. Then sort by the earliest date on which work must actually begin rather than by the date it is due, because an item with a dependency starts long before its deadline.

Mark dependencies explicitly and separately: anything requiring another person, an approval, a technical step, a scheduled activity, or an institutional process. Those items cannot be compressed at the end, and they are the reason a student who understands the material can still lose points. Anything on that list which has not started this Week is now the most urgent item on the map, ahead of any drafting.

Sequencing by risk instead of by comfort

With the map built, order the work by risk rather than preference. The riskiest item is usually the one carrying the highest weight, the most dependencies, or the least clarity about what is being asked, and it is usually the one students schedule last. Start it first, in rough form, this Week. An early rough version of a difficult deliverable converts unknown risk into a known list of gaps, and gaps can be filled.

Then reserve verification time as a fixed block that is never reallocated to writing. Verification in this class means comparing finished work against the live instructions and the current rubric line by line, confirming every figure carries its denominator and period, confirming the file opens and the format is right, and confirming the submission registered. Work that is complete but unverified is not finished, and at this point in the arc no later Week is left to absorb the consequence.

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 the source file before the final drafts

The end of a quarter is a poor time to be searching. Consolidate now: one file, one line per source, carrying authority or design, date, population and place, usable finding, limitation, and the claims it supports. Confirm that everything you expect to cite across the remaining activities is already there, and note the two or three gaps that would weaken a final argument if left open.

Fill those gaps deliberately rather than broadly. The families have not changed: current surveillance and official statistics for magnitude, policy and regulatory documents for definitions and obligations, organizational reporting for operational reality, peer-reviewed work for tested relationships, and assigned classroom readings wherever the live activity requires them. Verify each new item at the level of the claim it will support, and write its use note before it enters any draft. A source added late without a use note is the one most likely to be misquoted.

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.

Reading the rubric row by row in Week 9

Read every rubric currently posted for the remaining activities together, in one sitting. Looking across them shows where the weight actually sits for the rest of the quarter and prevents the common error of giving equal effort to unequal items. Note any row appearing in more than one instrument, because that is a standing expectation you can prepare once and satisfy repeatedly.

Then, for the highest-weighted remaining activity, convert its rubric into a working outline before drafting: one section per row, in the order the instrument lists them, with a note of the evidence each will need and the step only the student can perform. Your classroom rubric decides the rows, order, and weights for your section, so build that outline from the live document rather than from any general shape described here.

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.

Three Week 9 pitfalls and the repair for each

The first pitfall is sequencing by comfort. Easy items get done first because they produce visible progress, and the difficult, heavily weighted item arrives with no time left. The repair is the risk order described above, enforced by starting the hardest item in rough form before any easy item is finished.

The second is the invisible dependency. A step involving another person, an approval, or a scheduled process is assumed to be quick until it is not. The repair is a separate dependency lane with a start date for every item and a status checked at the beginning of each remaining Week, with the student completing every step through the official channel.

The third is leaving format conversion until the end. Documents change when converted, tables move, labels break, and files occasionally fail to open at all. The repair is to convert and open the file early, at draft stage, so a conversion problem is discovered while there is still time to solve it.

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