HLTH 2120 Week 6 planning manual

1. Capture the live Week 6

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.

Carrying earlier reasoning forward without recycling it

Integration means the concepts return, not the paragraphs. Take the population definition, the baseline, and the determinant chain you established earlier, and restate them from understanding in language written for this Week's activity. Previously submitted text belongs to a previously scored activity; the method belongs to you. Preserve the lesson and the method, and write the sentences new.

Then make the integration structural rather than decorative. A draft that mentions an earlier topic in one sentence has integrated nothing. A draft that uses an earlier concept to constrain a current choice has. If an earlier Week established a measurement limitation, that limitation should now be doing work: ruling an option out, narrowing a claim, or explaining why two figures cannot be compared directly. Integration is visible when removing the earlier concept would break the current argument.

Connecting determinants to system constraints

This is the point in the arc where population reasoning and systems reasoning have to meet. A determinant explains why an outcome differs across groups. A system constraint explains why an obvious response is not simply available: the information was collected for another purpose, the process sits with a different office, the record is least complete for the group most affected, or the resource is already committed. Both belong in one analysis.

Work it as a two-column note before drafting. On one side, list the determinants that plausibly move the outcome for your named population. On the other, list the constraints that would shape any response inside the system you are describing. Then draw the pairs that actually meet, and write about those. Pairs that do not meet are interesting and out of scope. Equity enters honestly here as well, because a constraint falling unevenly across groups is itself a determinant of the outcome you are measuring.

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.

Sources that join two parts of the course

Integration puts a specific demand on evidence: you need material that speaks to more than one part of the argument, or you need to show explicitly how two separate sources meet. A surveillance figure establishes the size of a difference; a policy or organizational document explains the process that produces or maintains it; a peer-reviewed study tests whether a given response changes anything. Used together in one paragraph, those three make an integrated claim. Used in three separate paragraphs, they make three observations.

When you reuse a source from an earlier Week, reread it rather than trusting your note, and confirm that the finding you remember is the finding it reports. Update the one-line use note to describe the new work it is doing. Assigned classroom readings still govern wherever the live activity requires them, and they are often the clearest model of how this subject expects two ideas to be joined inside a single sentence.

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

Look first for any row naming connection, synthesis, integration, or the relationship between concepts. Those rows are scored on the joints of the argument rather than its parts, and they are the rows most often lost by a draft that covers everything separately and connects nothing. For each such row, identify the specific paragraph where the joint is made, and confirm the sentence that performs it is actually present.

Then read the rows about originality and independent expression literally. Reusing your own previously submitted language is a real risk at this stage of a quarter, and paraphrasing it does not solve the problem; writing from the method does. Your classroom rubric decides how integration is defined and weighted in your section, so read the posted rows rather than assuming this description matches them.

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

Two Week 6 pitfalls and the repair for each

The first pitfall is integration by name-dropping. The draft says that this connects to what was covered earlier and then continues unchanged. The repair is a removal test: delete the earlier concept from the draft and see whether anything breaks. If nothing breaks, the connection was announced rather than made, and the paragraph needs a sentence that uses the concept to decide something.

The second is the summary that pretends to be synthesis. Restating several parts of the course in sequence is a review, and reviews rarely score well against synthesis criteria. The repair is to choose one current problem and require every earlier concept in the draft to do something to that problem: constrain the population, qualify the measure, rule out an option, or explain why a stakeholder cannot act. Concepts that cannot do work on the current problem come out of the draft.

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

Week 6 questions