HLTH 2120 Week 10 planning manual

1. Capture the live Week 10

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.

Revising the argument before revising the prose

Real revision starts above the sentence. Read the draft and write, beside each paragraph, the single job it performs: defines the population, establishes the baseline, traces a determinant, compares two options, states a limit, names the actor. Paragraphs that cannot be labeled are doing no work, and two paragraphs sharing a label are usually one paragraph split by accident. Fix the spine first, because rewriting sentences inside a broken structure preserves the break.

Then check that the labels run in an order a reader can follow: population before measure, measure before comparison, comparison before recommendation, and limits attached to the claims they bound rather than collected at the end. If the argument only makes sense to someone who already knows the conclusion, the order is wrong. This is the highest-value revision available at this point in the arc, and it is the one most often skipped in favor of word choice.

Repairing the pattern rather than the instance

Read the feedback ledger as a whole. The value of a quarter of comments is the repeated item, not the individual note. If denominators went missing three times, the correction is a rule applied to every rate in every remaining draft. If recommendations kept arriving without an actor, the correction is a template sentence. Write each recurring correction as a checklist line, then run the checklist against the current draft explicitly, marking each line rather than trusting a general impression.

Then verify the corrections you believe you already made. Students frequently remember adopting a fix that never reached the page. Find the specific sentence where it appears. If it cannot be found in the text, it was an intention rather than a revision, and it still needs doing.

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.

Verifying sources instead of adding to them

Late revision is where citation errors surface. Go through the draft and confirm, for each citation, that the source says what the sentence claims, that the population and period match the claim, that the date is right, and that the reference entry matches the in-text mention. Errors here are usually mechanical rather than dishonest, and they cost the same on evidence criteria either way.

Then remove what is not working. A source cited once, in a sentence that would survive its deletion, is padding, and padding weakens a reference list rather than strengthening it. If deleting an item leaves a claim unsupported, that claim needs either better evidence or a narrower statement. Adding new material at this stage is justified only when a specific claim is unsupported and nothing already in the file can support it at the right level.

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 10 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 10

Run a revision pass driven entirely by the rubric rather than by reading order. Take the rows one at a time, find the exact text satisfying each, and mark it. Rows with nothing to mark become the revision list, in priority order by weight. This is slower than reading the draft straight through and it finds different problems, because a reader moving through prose silently supplies missing connections without noticing.

Where a row is satisfied but only barely, ask what the next level of that row describes and whether one added sentence would reach it. Often it will: a stated limit, a named actor, a specified denominator, an explained comparison. Your classroom rubric decides the rows and levels for your section, so read the live instrument for this activity and let it, rather than this description, drive the pass.

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

Three Week 10 pitfalls and the repair for each

The first pitfall is line editing disguised as revision. Sentences get smoother, the structure stays broken, and the reasoning criteria do not move. The repair is to forbid sentence-level editing until the paragraph-job labels are written and the order is fixed.

The second is revising against remembered feedback. Memory softens comments and drops the specific words that named the gap. The repair is to open the actual returned comments and the actual rubric while revising, and to work from the wording of the comment rather than from your summary of it.

The third is treating length as a proxy for depth. When a draft feels thin, adding another paragraph of background is tempting. The repair is to ask what a scored criterion is missing and supply that, which is usually a connective sentence, a limit, a denominator, or an actor, and is almost never more background.

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

Week 10 questions