HLTH 1005 Week 7 planning manual

1. Capture the live Week 7

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 Context of Healthcare Delivery, 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.

Worked reasoning: tighten a claim until it could be measured

Precision in this subject means a sentence someone could set out to verify. Take a claim from the current draft and ask three questions of it: how much, among whom, and compared with what. "Access is poor" survives none of them. "Completion of a recommended preventive visit is lower among adults in this service area than in the state as a whole, in the most recent year reported" survives all three, and it also tells the reader exactly which evidence it needs.

The same discipline applies to the numbers you carry. Distinguish a count from a rate and a rate from a proportion, state the denominator whenever you state a rate, and keep the units and the period visible in the sentence rather than in a footnote. When you compare two figures, say whether the difference is absolute or relative, since a change described as a large percentage can be small in people and a small percentage can be large. Round consistently and never report more decimal places than the source supports. Where a number is uncertain, name the uncertainty in the same sentence instead of adding a general caveat at the end, because a limitation attached to a specific claim is analysis while a limitation floating at the close is decoration. How much quantitative work an activity expects is what your classroom rubric decides.

Reading the rubric row by row at the level of single words

By this point in the quarter the difference between performance levels is usually one word per row. Put two adjacent levels side by side and mark the words that change, which is often thorough against adequate, consistently against generally, or specific against relevant. Those words are the instruction. A row moving from relevant to specific is telling you that naming a category will not do and naming the case will.

Then audit the draft for each marked word. Consistently means every instance, so find the one paragraph where you dropped the practice. Thorough usually means the criterion has parts you can count, so count them. Specific means a proper noun, a number, a year, or a named setting appears where a general phrase currently sits. This is also the Week to check the mechanical rows that are easy to postpone: heading structure, citation format, page or word limits, file type, and any template the classroom supplies. Those rows are fully within your control and cost nothing but attention. The wording of each performance level, and how the levels are weighted, is what your classroom rubric decides.

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.

Source work: verify the figure before you cite it

Precision work fails most often at the moment a number moves from a source into a draft. Open the original rather than a summary, find the exact table or sentence the figure comes from, and copy the population, period, and unit along with the value. Note whether the figure is age adjusted, whether it is a sample estimate with a stated interval, and whether it refers to the geography your claim is about. Any of these can turn a correct number into a wrong sentence.

When the figure enters the draft, let the sentence carry its own provenance: the value, the population, the year, and the source in your own words, followed by the citation. Never let two figures from different sources sit in the same comparison without a line confirming they are comparable. If the number you want does not exist at the level you need, say what does exist and what remains unknown, because a stated gap is a finding in a systems course rather than a failure. Keep a verification column on your evidence shelf and date it, so a figure reused in a later Week does not have to be checked from scratch. Which sources are acceptable for quantitative claims is what your classroom rubric decides.

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

Three precision pitfalls and the fix for each

The first pitfall is the hedge stack. A sentence loaded with may, could, potentially, and somewhat says nothing and still occupies a line. The fix is one hedge per claim, chosen for accuracy, with the rest cut, and where genuine uncertainty is large, naming the reason for it instead of layering qualifiers.

The second pitfall is inflation by synonym. The same idea is restated three ways across a paragraph to reach a length target, and a reader scoring for depth sees repetition. The fix is a redundancy pass in which you keep the best version of each idea and spend the recovered space on the reasoning step you skipped.

The third pitfall is the citation that drifted. During revision a sentence gets rewritten while the citation behind it stays put, and the source no longer supports the claim attached to it. The fix is a late pass that reads only the claim and its citation as a pair, checking each against your use note, which catches misattributions a general proofread never will. Citation style and reference formatting are what your classroom rubric decides.

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

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

Week 7 questions