MPH-500 Week 8 System Assessment Synthesis: How to Write It

What MPH-500 Week 8 asks for

Synthesis is a construction problem, not a recall problem. Suppose the subject is the network of services supporting older adults leaving hospital in one county: the licensed facilities, the home health agencies, the area agency on aging, the public payers, the local department that inspects some of it and none of the rest. Six stages of coursework have handed you tools for that subject, but a synthesis paper does not deploy them in order. It states one claim about the network, then reaches for whichever tool proves each part of it. Authority mapping appears where authority is the problem. The seam analysis appears where the handoff is the problem. Surveillance appears where the absence of a shared measure is the problem. Everything that does not serve the claim stays out.

The claim itself has to be a system claim with a testable shape. That the network is fragmented is not a claim; it is the field's background noise. That responsibility for a resident's first thirty days after discharge is distributed across four organizations, none of which is measured on that period, and that this is why a locally funded transition program produced no measurable change in a county indicator, is a claim. It names actors, it identifies a mechanism, and it points at evidence. A grader reading a culminating paper is looking for exactly that difference.

Expect the closing stage to carry both a paper and a posted element in many sections, and expect the workload compression that always attends the final week of a short session. Two practical consequences follow. Write your reference list as you draft rather than at the end, because reconciling twenty in-text citations against a list at eleven o'clock on the last night is where formatting points are lost in bulk. And budget explicit revision time, since a synthesis paper is the one deliverable in the term whose quality depends most on a second pass with fresh eyes.

One more note on scope. Closing pieces reward depth over coverage. A paper that treats one problem in one jurisdiction thoroughly will outscore one that gestures at the national system, because the specific paper can carry denominators, named instruments and real documents, and the general one can only carry adjectives.

The MPH-500 Week 8 method, step by step

Seven moves for assembling a culminating systems paper under time pressure.

1. Write the claim as a single sentence and post it above your draft

   Actor, mechanism, consequence. If the sentence does not contain all three, it is a topic rather than a claim, and every paragraph you write under it will drift toward description.

2. Choose the jurisdiction and lock the denominator early

   One county, one district, one service region, with the population figure and its source fixed before drafting. Late changes to the geography force recalculation of every rate in the paper, which is how good drafts die on the final weekend.

3. Select three analytic tools and refuse the rest

   Authority mapping, financing trace, seam analysis, surveillance assessment, organizational assessment. Pick the three that prove your claim and leave the others out entirely, because completeness of coverage is not a criterion anyone is scoring.

4. Build the evidence table before the prose

   One row per claim, with the source, the figure, the denominator and the year beside it. Gaps in that table are the research you still owe, and finding them on a Tuesday is cheap while finding them on Sunday is not.

5. Write the recommendation section as a set of decisions

   Each recommendation names who decides, under what authority, funded how, and what indicator would show it worked in a stated window. Three of those outrank eight aspirations, and they are the part of the paper that most often carries the top band.

6. Reconcile citations in a dedicated pass

   Read the reference list first and find each entry in the text, then read the text and find each citation in the list. Two directions, ten minutes, and it catches almost every reference error a formatting row penalizes.

7. Cut on the second pass rather than adding

   Closing papers are usually long, not short. Remove the definitional paragraph, the history recap and any sentence that begins by announcing what the paper will do next, and the argument gets faster without losing a single piece of evidence.

A layout and word budget for a culminating systems paper

Our frame for a closing synthesis, sized for roughly 1,500 to 1,800 words and scaled proportionally if your assigned length differs. It is our own outline rather than anything the university issues, and your week's scoring guide outranks it wherever they disagree.

Evidence craft for a closing synthesis

Weight your sources rather than stacking them. A statute, an agency budget document, a national surveillance release and a peer-reviewed evaluation do different jobs, and a synthesis that says which kind of claim each source is carrying reads as controlled. Three well-used sources beat nine cited once each in a parenthesis.

Check recency where recency matters. Structural descriptions age slowly and numbers age fast. A funding figure or a utilization rate from several years ago needs either a newer figure or an explicit statement that it is the most recent published, and saying which is a sign of a careful writer rather than an admission.

Handle reuse of your own earlier work transparently. Academic programs generally expect written work to be original to the assignment, and submitting the same text twice without permission can be treated as an integrity matter, so check your own program's policy and your section's instructions before recycling. The safe and usually better route is to reuse the research rather than the prose: keep the sources, rebuild the sentences around the new claim.

Make the limitations paragraph do analytic work. Say which specific inference your evidence cannot support and why, whether that is a suppressed subgroup, a measure not published at your geography, or a comparison confounded by governance differences. Generic acknowledgements of limited scope are filler, while a precise one demonstrates command.

Keep the final proofread mechanical. Read the paper once for citations only, once for numbers and their denominators, and once aloud for sentence length. Three narrow passes catch more than one broad reading, and they are achievable in the hour before a closing submission when a full rewrite is not.

Five mistakes that cost points in this week's territory

• A parade of the term's topics. Marching through everything the course covered proves attendance rather than analysis, and it is the single most common shape of a mediocre closing paper.
• A brand new subject in the final week. Starting fresh forfeits the research you already own and guarantees a thin evidence base under deadline.
• Recycled paragraphs. Pasting earlier submissions into the closing piece risks an integrity finding and produces prose aimed at the wrong claim.
• Recommendations without decision-makers. The closing section is where a systems course finally checks whether you know who can actually act, and generic calls to action answer no.
• Reference drift. Sources in the list that never appear in the text, and citations in the text missing from the list, are cheap points to lose in the last hour of a session.

Before you submit

• A one-sentence claim naming actor, mechanism and consequence sits behind the paper
• The jurisdiction and its population figure are fixed and sourced
• Each supporting measure carries a denominator, a period and a source
• Every recommendation names a decision-maker, an authority and an indicator
• The reference list was reconciled in both directions
• The limitations paragraph names a specific inference the evidence cannot support

Questions students ask about this stage

Keep going