HLTH 2120 Week 11 planning manual

1. Capture the live Week 11

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.

The final verification pass, in order

The last Week of the arc rewards procedure over inspiration. Run the passes in a fixed order and do not skip ahead. First, the literal instruction audit: every part of the live prompt answered, in the form it asked for. Second, the rubric pass: every criterion given something visible to score. Third, the evidence pass: every figure carrying its numerator, denominator, period, and place, and every citation pointing at the source that reports the finding. Fourth, the mechanics pass: format, headings, citation style, length, labeling, accessibility, and removal of anything confidential.

Then the process pass, which is the one most often lost at the end of a quarter. Confirm the file opens from the submitted copy, confirm the timestamp and time zone, confirm any reply or participation requirement is complete rather than partly complete, and confirm every dependency and institutional step has been finished by the student through the official channel. Save the receipt. A finished artifact that never registered is indistinguishable from work never done.

Separating the lesson from the language

Closure has a second job: deciding what leaves this course with you. The answer is method and evidence habits, not text. Previously submitted work belongs to the activity that was scored, and carrying its language into another course creates an originality problem and, more practically, produces reasoning that no longer fits the new prompt. What travels well is the sequence: define the population and baseline, trace determinants and system constraints, compare interventions, and connect the recommendation to implementation and evaluation.

Write a short method file for yourself while the quarter is still fresh. Record the four-part way you learned to specify a measure, the source families that answered how big the problem is, who says so, what the rule is, how the system runs, and what has been tested, the criteria this section repeated across activities, and the two corrections you had to make more than once. Those pages are worth more in the next course than any saved draft, and they take twenty minutes to write now and considerably longer to reconstruct later.

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.

Retiring the source file responsibly

Before closing the course, make one last pass over the working file. Confirm that every source used in a final submission is fully recorded with its authority or design, date, population and place, finding, and limitation, so a later question about a claim can be answered from your own notes rather than from memory. Remove anything that never performed work, and mark the items you expect to remain useful in later coursework.

Then check the currency of what you keep. Statistical releases and policy documents update on their own schedules, and a figure that is current this quarter may not be next term. Note the release cadence where you know it, so a later reuse begins with a check rather than an assumption. Assigned readings stay with the class that assigned them; the habit of matching source level to claim level is what transfers.

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 11 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 one last time

For the final graded work, read the live rubric twice: once before drafting, and once after a draft exists, with the second reading done against the text rather than against your intentions. In that second reading, point at the sentence satisfying each row. Anything you cannot point at is not there, however clearly you remember thinking it.

Then check the rows governing completeness and process, which carry real weight at the close of a quarter: submission format, required components, participation or reply requirements, and anything the activity asks the student to complete and attest to personally. Your classroom rubric decides all of this for your section, and the live instrument governs even where it differs from every general description, including this one.

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 11. 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 11, 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 11.

Two closing pitfalls and the repair for each

The first pitfall is stopping at submission. The upload happens, the browser closes, and nothing confirms that the right file registered at the right time. The repair is a two-minute routine the student performs every time: reopen the submitted copy from the submission record, read the first page, check the timestamp against the posted deadline and time zone, and save the confirmation.

The second is carrying forward the wrong thing. Files get archived and methods get forgotten, so the next course starts from nothing while an old draft waits in a folder to cause an originality problem. The repair is to write the method file described above, store it where the next course will find it, and keep graded artifacts only as records of what was scored rather than as material to reuse.

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

Week 11 questions