HLTH 2120 Week 1 planning manual

1. Capture the live Week 1

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.

Working the population statement before anything else

Week 1 reasoning starts with a sentence nobody assigns and everybody needs: a plain description of who is being counted, over what period, in what place, and against which comparison. Health Informatics at this level treats that sentence as the unit of analysis, so write it out longhand. Adults enrolled in one regional health system over a twelve month period, compared with the same system in the prior year, is a usable statement. The community is not, because nothing in it can be counted, compared, or contradicted. If the live Week 1 activity is only an introduction or a first discussion, the statement can stay in your working notes rather than the submitted text, but writing it now prevents an entire quarter of drift.

Then name the four elements the class question asks for. Population is the counted group. Determinant is the condition, exposure, policy, or system feature that plausibly moves the outcome. Stakeholder is the person or office that can act, fund, block, or be affected. Measurable outcome is the number that would change if the determinant changed, stated with its denominator. Reasoning in this subject fails most often because one of the four went missing quietly, and Week 1 is the cheapest place in the quarter to notice.

Setting the baseline you will use all quarter

A baseline is not a fact you look up once; it is a choice with consequences. Decide now which figure you will treat as the starting value, which period it covers, which geographic level it describes, and where it came from. Record the source, the release date, and the exact indicator name in the same ledger that holds your Week 1 activity rows. Later Weeks will ask you to compare, and a comparison built on two incompatible baselines produces a conclusion that no amount of polish will rescue.

Write down what the baseline cannot tell you as well. A count is not a rate. A rate without a denominator is a rumor. One period does not establish a trend, and a trend does not establish a cause. Recording those limits in Week 1 gives you ready-made qualifying language for every later draft, and it protects the boundary between association and causation that the class quality gate tests.

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.

What counts as a source here, and how to file it in Week 1

The evidence rule for this class is that current surveillance, policy, organizational, and peer-reviewed material must sit at the same geographic and population level as the claim it supports. In practice that gives four working families. Surveillance and official statistics supply counts, rates, and denominators. Policy and regulatory documents supply rules, mandates, and definitions. Organizational reports supply operational detail such as staffing, workflow, systems, and cost. Peer-reviewed studies supply tested relationships and effect estimates. Readings assigned in the live classroom remain required wherever the current activity requires them, and they usually model the level of formality the section expects.

In Week 1, build the file rather than the argument. For every item, write one line: what it is, when it was published, which population and place it describes, the single usable finding, and the claim you expect it to support. Anything you cannot complete that line for does not enter a draft. This one-line discipline is what later turns a reference list into an argument, and it breaks the familiar first-week habit of collecting twenty open tabs and using none of them.

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

Open the rubric attached to the live Week 1 activity and read it as a scoring instrument rather than a summary. Take one row at a time and answer three questions in writing. What noun does this row grade: a claim, a source, a calculation, a structure, or a mechanical convention? Where in my draft will a reader physically see that thing? What would the weakest acceptable version look like, and what separates it from the strongest? Rows that grade reasoning need visible reasoning, not a heading that promises it.

Then note the row order, the point spread, and any threshold language. A row worth many points deserves proportional drafting time even when it feels less interesting, and a row worth few points still has to appear somewhere. Your classroom rubric decides what is actually scored in your section; this page describes how to read one, never what yours contains. Save the rubric version beside the working file so a later revision compares against the same instrument.

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 2. 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 1, 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 2.

Three Week 1 pitfalls and the repair for each

The first pitfall is treating the syllabus as the rubric. A syllabus describes the class; a rubric scores the artifact, and the two rarely use the same words. The repair is to copy the rubric rows into the working file and let the syllabus govern only calendar and policy questions.

The second is starting research before the task sentence exists. Reading feels productive and produces nothing scorable while the question is still vague. The repair is a hard rule: no source is opened until one sentence names the decision or explanation, the required evidence, the audience, and the output. If that sentence cannot be written, the problem is comprehension of the prompt, and rereading the prompt is the faster fix.

The third is writing about an undefined group. Words such as patients, the population, or the community feel safe and score poorly, because nothing in them can be measured. The repair is mechanical: every time one of those words appears in a draft, replace it with the counted group, the place, and the period, then confirm a reader could in principle go and count 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 1 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 1 questions