| Course | MMHA 6540 Population Health Management Applications |
|---|---|
| Week | Week 9 |
| Paper type | Baseline and target framework |
| Length | About 1,070 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Master of Healthcare Administration (MHA) |
| Updated | October 2026 |
Free sample paper for MMHA 6540 Week 9
Baselines, Targets and a Fair Comparison: An Evaluation Framework for Prairie Gate's Falls Program
Student Name
Walden University
MMHA 6540: Population Health Management Applications
Instructor Name
Month Day, Year
Baselines, Targets and a Fair Comparison: An Evaluation Framework for Prairie Gate's Falls Program
Purpose
This framework sets out how Prairie Gate Health Plan will judge its falls prevention program. It defines outcome and process measures with baselines and targets, adds a measure members report themselves, and describes a comparison design. The main threat to a fair judgment is built into the program: participants are selected because they recently fell, and people selected at a high point tend to do better afterward even without help (Barnett et al., 2005). A framework that compares participants only with their own previous year would credit the program with improvement that would have happened anyway. All values are illustrative.
Measures
Table 1 lists the measures with baselines, targets and sources.
Table 1
Falls Program Measures (Illustrative Values)
| Measure | Type | Definition | Baseline | Target | Source and lag |
|---|---|---|---|---|---|
| Fall-related emergency visits | Outcome | Per 1,000 participants per year | 620 (segment's prior year) | Lower than comparison group | Claims; about 3 months |
| Fall-related admissions | Outcome | Per 1,000 participants per year | 270 (segment's prior year) | At least 44 fewer than expected per 600 participants | Claims; about 3 months |
| Reached within 7 days | Process | Share of identified members contacted within 7 days | Not applicable | 80% | Care management system; real time |
| Home safety visit received | Process | Share of enrolled members visited within 14 days | Not applicable | 85% | Therapy visit notes; weekly |
| Modifications completed within 30 days | Process | Share of recommended modifications completed within 30 days of the visit | Not applicable | 75% | Repair completion reports; weekly |
| Class attendance | Process | Participants present for half or more of their class series | Not applicable | 50% | Area agency attendance; monthly |
| Fear of falling | Member-reported | Short fear-of-falling questionnaire score | Measured at enrollment | Improvement at 6 months | Coordinator call; at enrollment and 6 months |
Outcome Measures
The two outcome measures count fall-related emergency visits and admissions per 1,000 participants per year, using diagnosis and external cause codes in claims. The baselines come from the target segment's prior year, but because the segment was defined by having fallen, those baselines are inflated: they include the very falls that qualified members for the program. The targets are therefore stated against a comparison group rather than as a fixed reduction from baseline. The admission target is tied to the break-even point in the payer brief: at least 44 fewer admissions than expected among 600 participants. Because fall claims take roughly a quarter to settle, so the first full year of outcomes can be read only about fifteen months after launch.
Process Measures
The process rows mirror the blueprint's four steps one for one, and unlike claims they can be read within weeks. They answer a different question from the outcomes. If outcomes disappoint, these rows reveal whether the fault lay in the idea or in its execution. If a step is slipping, for example if modifications lag because of the repair bottleneck, the program can fix it long before claims would reveal any effect on falls. Exercise reduces falls mainly when people actually attend (Sherrington et al., 2019), so class attendance is the process measure most closely tied to the outcome.
Member-Reported Measure
Fear of falling is common after a fall and leads many older adults to restrict their activity, which can weaken them and increase future risk. A short questionnaire at enrollment and at six months, asked by the coordinator by phone, will show whether participants feel safer. This measure matters for two reasons: it captures a benefit members value that claims will never show, and it helps interpret the outcomes, since a participant who feels safer may move more and therefore have more opportunities to fall.
Comparison Design
The program will be rolled out by county in stages: the metro county first, as a pilot, then Ash and Corley. Members who meet the segment definition in counties not yet served will form the comparison group, and their fall-related visits and admissions will be tracked in the same way. The program's effect is estimated as the difference between the change among participants and the change among comparison members over the same months, the logic of difference-in-differences (Dimick & Ryan, 2014). Because both groups are selected by the same rule, both will regress toward lower rates, and the comparison removes that shared improvement. Staggering rollout in this way is a recognized design for programs an organization intends to extend to everyone (Hemming et al., 2015).
The comparison has limits. The rural counties differ from the metro county in age, housing and access, so their trends may differ for reasons unrelated to the program; the analysis should adjust for age and prior falls. And the comparison ends when the last county is served, so the design yields its strongest evidence in the first year.
Reporting
Process measures will be reported weekly to coordinators and monthly to the population health director. The member-reported measure will be summarized at six months. Outcomes will be reported fifteen months after launch, when claims for the first year are complete, to the executive committee, together with the process measures and the comparison results. The report will state plainly whether the break-even threshold was met and what the program achieved for members either way.
Data Readiness
Several pieces must be in place before the first member is enrolled. The analyst must confirm that fall-related emergency visits and admissions can be identified reliably in claims, using injury diagnosis codes together with external cause codes, and must test the definition on last year's data to see whether it matches the counts in the burden profile. The care management system needs fields for the date a member was identified, the date of first contact and the date of enrollment, so that the seven-day measure can be calculated automatically. The repair nonprofit's completion reports must include the date of the home visit they respond to, or the thirty-day measure cannot be computed. The area agency's attendance file must carry a member identifier the plan can match. And the coordinators need a script for the fear-of-falling questions, so that every participant is asked the same way at enrollment and at six months.
Each of these is a small task, but missing any one would leave a measure blank in the first report. The population health analyst will own a readiness checklist and report its status to the director two weeks before launch, and launch should wait until every item on it is complete.
References
Barnett, A. G., van der Pols, J. C., & Dobson, A. J. (2005). Regression to the mean: What it is and how to deal with it. International Journal of Epidemiology, 34(1), 215-220. https://doi.org/10.1093/ije/dyh299
Dimick, J. B., & Ryan, A. M. (2014). Methods for evaluating changes in health care policy: The difference-in-differences approach. JAMA, 312(22), 2401-2402. https://doi.org/10.1001/jama.2014.16153
Hemming, K., Haines, T. P., Chilton, P. J., Girling, A. J., & Lilford, R. J. (2015). The stepped wedge cluster randomised trial: Rationale, design, analysis, and reporting. BMJ, 350, Article h391. https://doi.org/10.1136/bmj.h391
Sherrington, C., Fairhall, N. J., Wallbank, G. K., Tiedemann, A., Michaleff, Z. A., Howard, K., Clemson, L., Hopewell, S., & Lamb, S. E. (2019). Exercise for preventing falls in older people living in the community. Cochrane Database of Systematic Reviews, 2019(1), Article CD012424. https://doi.org/10.1002/14651858.CD012424.pub2
What the MMHA 6540 Week 9 instructions ask for
Evaluation framework assignments ask you to define how a program's success will be judged before it starts. List every measure with its type, definition, baseline, target and data source, noting reporting lags. Think hard about how participants were selected, since selection at a high point inflates baselines, and state targets against a comparison group where needed. Include process measures for each step and a member-reported measure for benefits claims cannot see. Describe the comparison design and its assumptions and limits. Set reporting dates that respect data lags. Close with the data fields and agreements that must exist before launch, and who will confirm them. State who will own the evaluation and when results will reach leaders. Agree the comparison group's definition with the analyst before launch.
Inside the MMHA 6540 Week 9 example
The purpose section names regression to the mean, citing Barnett and colleagues. Table 1 lists two outcome, four process and one member-reported measure. The outcome section explains inflated baselines and ties the admission target to break-even. The process section explains reading delivery within weeks and cites Sherrington and colleagues on attendance. The member-reported section explains fear of falling. The design section describes county-by-county rollout with not-yet-served members as comparisons, citing Dimick and Ryan and Hemming and colleagues, and its limits. A reporting section sets weekly, monthly, six-month and fifteen-month reports. A data readiness section lists five items to confirm before launch, from the claims lag to the ambulance data agreement, so nothing stalls the first report.
Where the marks sit in the MMHA 6540 Week 9 rubric
Frameworks are graded on rigor and practicality. Complete measure definitions with baselines, targets and sources earn the first share. Recognizing that selection inflates baselines, and setting targets against a comparison, earns the largest share; frameworks that compare participants only with their own past lose credit. Process measures tied to delivery steps and a member-reported measure show breadth. A comparison design with stated assumptions and limits demonstrates methodological skill. Reporting dates that respect claims lag are expected. A data readiness checklist shows the framework can actually be used. A measures table complete enough to run without asking the author questions is the target.
MMHA 6540 Week 9 help from the desk
Evaluation frameworks often set a target like a 20 percent drop from baseline. If participants were chosen because they just had a bad year, that drop may happen anyway. Compare them with similar people who have not yet received the program. Measure each delivery step so you can tell an idea that failed from one that was not carried out. Ask members something claims cannot answer. Respect data lags when you promise results. Confirm the data fields exist before launch. We can design an evaluation framework for your organization's program with a fair comparison. Agree the targets with leaders before launch so they cannot be reinterpreted afterward.
Get a MMHA 6540 Week 9 example written to your instructions
Along with your blueprint and budget, forward the Week 9 instructions and rubric; a framework that gives every measure a baseline, a target, a source and a comparison group returns in 24-48h, your first free of charge. Its baselines and targets are illustrative values for a composite plan's members.
More MMHA 6540 papers and MHA samples
- MMHA 6540 Week 1: Population Scoping Memo
- MMHA 6540 Week 2: SDOH Lever Post
- MMHA 6540 Week 3: Falls Burden Profile
- MMHA 6540 Week 4: Need Ranking Matrix
- MMHA 6540 Week 5: Partner Readiness Map
- MMHA 6540 Week 6: Falls Intervention Blueprint
- MMHA 6540 Week 7: PMPM Staffing Budget
- MMHA 6540 Week 8: Payer ROI Brief
- MMHA 6540 Week 10: Integrated Initiative Draft
- MMHA 6540 Week 11: Falls Prevention Plan
- MMHA 6530 Week 9: HEDIS Measure Plan
- MMHA 6520 Week 9: Analytics Program Evaluation
- MMHA 6501 Week 9: Leadership Development Plan
- MMHA 6475 Week 9: Comparison Group Design
MMHA 6540 Week 9 questions, answered
Where can I find a free MMHA 6540 Week 9 sample paper?
The evaluation framework and measures table are free to read on this page.
Why are baselines inflated in the MMHA 6540 Week 9 framework?
Participants were selected because they recently fell, so their prior year includes the falls that qualified them.
How is the program's effect estimated?
By comparing participants' change with the change among qualifying members in counties not yet served.
What member-reported measure is used?
A short fear-of-falling questionnaire at enrollment and six months.
When can fall outcomes be reported?
About fifteen months after launch, once claims for the first year are complete.