MPH-507 · Week 1 of 8 · Framing the problem and defining the population

MPH-507 Week 1 Framing the Problem and Population: How to Write It

The short answer

MPH-507 Week 1 asks you to write a problem statement that a funder could act on, which means a defined population, a quantified problem and a denominator that makes the number mean something. Everything later in this course depends on this stage: objectives are written against the problem, indicators are written against the objectives, and none of the chain holds if the opening definition is loose. Your section may print this as MPH 507 or MPH507; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.

MPH-507 Week 1 grading scale at Chamberlain, the criterion levels this assessment is scored on, from Chamberlain Tutors
How Chamberlain grades MPH-507 Week 1, visualized by Chamberlain Tutors.

What a fundable problem statement establishes

Read the review comments on a rejected grant application and the same finding appears more often than any other: the applicant described a condition rather than a problem in a population. The reviewer's notes usually run along one line. Who exactly. How many of them. Out of how many. Compared with what. And why this group rather than the neighboring one. Those five questions are a quality audit of a problem statement, and a document that cannot answer them has not yet made a case that anything should be funded, regardless of how serious the condition is in general.

The territory of an opening planning stage is the transition from topic to problem. A topic is a subject area: food insecurity, vaccination coverage, hypertension control, overdose. A problem is a topic converted into a measured shortfall in a bounded population over a stated period. The difference is not rhetorical. A topic cannot be prioritized against other topics, cannot generate an objective with a number in it, and cannot produce a baseline against which anything is later evaluated. Almost every weakness that shows up in Week 7 and Week 8 of a planning course was created here.

The denominator is the technical core of the stage. A count of cases tells a reader that something happened; a rate tells them how common it is; and the choice of denominator decides what the rate is even about. Cases per resident population, per person in the eligible age band, per person enrolled in the relevant service, and per encounter are four different measures that answer four different questions, and a plan that uses the wrong one for its claim will produce objectives that cannot be met or targets that were already met before the program started.

Deliverables at this stage tend to be a written problem statement or a short population profile, sometimes with a data table, and often a posted introduction of the problem you will carry through the session. Treat the post as final copy; Canvas boards do not reopen after submission, and in this course classmates will test whether your problem statement has a denominator in it.

A method for turning a topic into a problem

Six moves that produce a statement the rest of the plan can be built on.

  1. Reduce the scoring guide to its verbs before choosing a topic

    Describe, document, quantify, compare and justify ask for different work. Marking which rows want data and which want reasoning tells you where the effort belongs, and it usually reveals that the guide wants a narrower problem than the topic you had in mind.

  2. Bound the population on four axes

    Geography, demographic band, service or system relationship, and time period. A statement that names all four is specific enough to count; one that names two produces a population nobody can enumerate and therefore no denominator.

  3. Find the denominator before you find the number

    Decide what the rate should be per, then look for both the numerator and that denominator from sources that cover the same geography and period. Working the other way produces a striking count and no way to interpret it.

  4. Set the comparison that makes the gap visible

    A national or state rate, a benchmark target, a neighboring area, or the same population in an earlier period. A number with nothing beside it cannot demonstrate a shortfall, and demonstrating the shortfall is what the row is scoring.

  5. Say what the problem costs and to whom

    Consequences in health terms, service utilization terms and, where you can support it, economic terms. This is the paragraph that answers why anyone should spend money here rather than somewhere else, which is the actual question behind every planning document.

  6. Close on what is not yet known

    Name the data you could not find, the subgroups your figures cannot resolve, and what would need to be collected. A problem statement that maps its own gaps sets up the needs assessment stage instead of pretending the picture is complete.

A layout and word budget for a problem statement

The frame below is what our tutors keep beside an opening planning submission, sized for roughly 900 to 1,200 words. It is our own outline rather than anything the university issues, and your section's scoring guide outranks it wherever the two disagree. A small table of local figures against a benchmark will carry perhaps 130 words of this budget, and those words are better spent on the consequence and gap sections.

SectionWhat belongs in itWord target
The problem in one paragraphPopulation, place, measure, magnitude and period, stated before any background about the condition arrives.90 to 120
Population definitionThe four bounding axes, the size of the group, and how you arrived at that figure.150 to 190
Magnitude with denominatorsThe numerator, the denominator, the resulting rate, the source and the year for each figure you use.190 to 240
Comparison and gapThe benchmark or comparison group, the size of the difference, and whether the trend is moving toward or away from it.170 to 210
ConsequencesWhat the problem produces in health, service and cost terms, and which subgroups carry most of it.170 to 210
Data gapsWhat is missing, what the missing data would resolve, and how you propose to fill it in the next stage.120 to 160

Evidence craft with population data

Localize every figure or label it as a proxy. A national prevalence establishes that a condition exists somewhere; a county, ZIP code, service area or facility figure establishes that it exists where you intend to work. When only national data are available, say so in the sentence, give the closest local proxy you can find, and state what would make the local value differ. Reviewers accept proxies that are labeled and penalize proxies that are disguised.

Name the surveillance system, not just the agency. Population health figures come from identifiable systems with identifiable designs: household surveys with sampling frames, vital statistics registries, disease reporting systems, claims databases and program records. Each has known coverage and known blind spots. Naming the system and the year lets a reader judge the figure, and it is a scored competence in a planning course.

Report small numbers as counts and say when a rate is unstable. A rate computed from a handful of events in a small population swings wildly year to year and can look like a crisis or a success depending on which year you picked. Where your numerator is small, give the count, give several years, and say plainly that the rate is unstable. That sentence protects your objective from being written against noise.

Distinguish the population with the condition from the population you can reach. These are almost never the same group, and the difference determines everything about feasibility later. Say how many people have the problem, how many are eligible for your program, and how many you could realistically enroll, with the reasoning for each step. Planning documents that skip this produce objectives that are arithmetically impossible.

Five mistakes that cost points in this week's territory

  • A topic submitted as a problem. Obesity in America is a subject heading. Nothing downstream in a plan can be built on it.
  • Counts with no denominator. A number of cases reported without the population it came from cannot show whether the problem is unusually common here.
  • National statistics used as local evidence. The most common single finding in returned planning drafts, and the easiest to fix before submission.
  • A population that cannot be enumerated. If nobody could count the group you defined, you will never have a baseline, a target or a denominator for evaluation.
  • No comparison anywhere. Without a benchmark, a neighboring area or a trend, the reader has no way to see that a shortfall exists.

Before you submit

  • The opening paragraph names population, place, measure, magnitude and period
  • The population is bounded on geography, demography, service relationship and time
  • Every rate shows its numerator, its denominator and its source year
  • A comparison or benchmark appears and the gap is quantified
  • The reachable population is distinguished from the affected population
  • Data gaps are named with what would resolve them

Starting MPH-507 this week?

Send the prompt, the scoring guide and any data your section supplied. A premium original draft comes back in 24 to 48 hours with the population bounded and every rate carrying its denominator, and revisions run until the grade lands.

Questions students ask about this stage

How narrow should my population be if I have to carry it for eight weeks?
Narrow enough to enumerate, broad enough to have published data. That balance usually lands at a defined geography combined with one demographic or clinical band, such as adults over a stated age within a county, or children in a school district, or patients discharged from one system with a specific condition. Too broad and every objective becomes unachievable with any realistic budget, which will cost you in the feasibility row later. Too narrow and no data source resolves your group, which leaves the needs assessment stage with nothing to work from. A practical test before committing: spend thirty minutes trying to find a single credible rate for the exact group you have defined. If you can find one, the definition works for a whole session. If you cannot, widen one axis and try again before you write another paragraph.
My prompt asks for a real community. Can I use my own workplace or neighborhood?
Usually yes, and it tends to produce stronger work, because you can describe the service structure, the referral patterns and the practical constraints with a precision that a stranger to the setting cannot reach. Two cautions. First, keep the analysis to publicly available or appropriately aggregated data; do not import anything identifiable about individuals, and where you describe operational detail, keep it at a level that would be fine to read aloud in a meeting. Second, familiarity produces assumptions, and a planning document has to document what you know rather than assume the reader shares it. If you find yourself writing that everyone knows the clinic is overwhelmed, stop and find the figure that shows it. Check your section's instructions as well, since some prompts specify a community type or require a publicly documented one.
What if the data show my chosen problem is not actually worse here than elsewhere?
That is a genuinely useful finding and you have two honest options. The first is to change the problem, which costs you an afternoon in Week 1 and saves you seven weeks of arguing from a weak base. The second is to keep it and reframe the gap: a rate at the state average may still represent a large absolute burden, a rising trend, a sharp disparity between subgroups inside your population, or a service gap where the condition is common but treatment coverage is poor. Any of those is a legitimate problem statement, provided you say plainly that the overall rate is unremarkable and then show what is. What does not work is quietly selecting the one comparison that makes your area look worst, because a reviewer who checks the obvious benchmark will find it, and the credibility loss reaches every section after it.

Keep going

Online now