MMHA 6520 Week 11 Population Analytics Proposal Example

Health Informatics and Population Health Analytics Walden University Free custom sample in 24 to 48h

This MMHA 6520 Week 11 analytics proposal example asks a fictional Medicaid plan's leaders to pay for a transitions team that acts on hospital discharge notices, phoning members inside two business days and asking their practices for a visit inside a week. Walden MMHA 6520 closes the MHA program's health informatics course with a full proposal, and a one-page executive summary states the request, population, expected near-term result and decision date. Five APA tables carry the evidence: population rules, data sources with delays and owners under 42 C.F.R. 482.24, outreach by risk segment citing Jack and colleagues, a measurement plan using a staggered rollout citing Hemming and colleagues and Barnett and colleagues, and staffing by role. Sections cover the five fields practices receive, oversight, what the design cannot show and the schedule.

CourseMMHA 6520 Health Informatics and Population Health Analytics
WeekWeek 11
Paper typePopulation analytics proposal
LengthAbout 1,190 words, 7 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramMaster of Healthcare Administration (MHA)
UpdatedOctober 2026

Free sample paper for MMHA 6520 Week 11

1

Reaching Members Within Days of Discharge: A Population Analytics Proposal for Riverline Health Plan

Student Name

Walden University

MMHA 6520: Health Informatics and Population Health Analytics

Instructor Name

Month Day, Year

What this page is doingThe title states the result the proposal promises in plain words, as an executive reader would want.
2

Reaching Members Within Days of Discharge: A Population Analytics Proposal for Riverline Health Plan

Executive Summary

Riverline Health Plan, a Medicaid plan built for this course, learns of most members' hospital discharges from claims that arrive weeks later, after the period when follow-up matters most. Exchange notices of those same discharges already reach the plan on the day they happen, but they wait in an inbox and are acted on only for members already in care management. This proposal requests approval and funding to route those notifications to a transitions team that calls eligible members within two business days and asks their assigned practices to see them within seven days. It covers adults going home from an inpatient stay whose primary care is attributed to a network practice. The expected near-term result is a higher share of members seen in primary care within seven days of discharge; effects on readmission and emergency use will be measured but may take longer to appear. The rollout is staggered across practices so that the effect can be measured. Leadership is asked to decide by the end of next month so that the first practices can begin in the following quarter.

What this page is doingOne page states the request, population, near-term result and decision date.
3

Population

Eligible members are working-age adults leaving a hospital ward whose attributed primary care home, on the day they go home, is one of Riverline's network practices. Table 1 states the inclusion rules, which follow the assignment-based definition adopted in the plan's earlier denominator work.

Table 1

Population Definition

RuleSpecificationSource
Age18 to 64 on discharge dateEnrollment file
EnrollmentEnrolled on discharge date; continuous enrollment not requiredEnrollment file
EventInpatient discharge to home or home with servicesExchange notification
AssignmentAssigned to a network primary care practice on discharge datePractice assignment file
ExclusionsDischarges to skilled nursing, hospice or another hospital; obstetric deliveries, which have a separate programExchange notification

Note. Continuous enrollment is not required, because members with interrupted coverage are among those most likely to need help after discharge.

What this page is doingEach table is introduced in the paragraph before it and carries an APA title and note.
4

Data Sources

The proposal relies on three sources, chosen for speed where speed matters and completeness where it does not. Hospitals participating in Medicare are required to send admission and discharge notifications electronically (42 C.F.R. § 482.24), which makes the exchange the fastest source. Table 2 lists each source.

Table 2

Data Sources, Delays and Owners

SourceDelayUseOwner
Exchange discharge notificationsHoursTrigger outreachInformatics director
Practice assignment fileMonthlyRoute notices to practicesProvider network director
Enrollment fileMonthlyConfirm eligibility; track coverage lossEnrollment manager
ClaimsWeeks to monthsEvaluation onlyInformatics director

Note. Claims are not used to trigger outreach, because they arrive too late for the purpose.

What this page is doingThe data sources table makes delay a column, since speed is the proposal's central argument.
5

Segments and Workflow

Not every discharged member needs the same response. Table 3 applies the plan's revised risk segments to the discharge population.

Table 3

Segments and Outreach After Discharge

SegmentIdentified byOutreach
Recent admissions with high risk scoreExchange notifications and quarterly scoreCare coordinator call within 1 business day; practice visit within 7 days
Thin recordEnrollment and claims countsCommunity health worker call within 2 business days; help scheduling a first visit
Social risk flaggedCare manager assessment or practice screeningCoordinator call within 2 business days; referral to community resource team
All other eligible dischargesExchange notificationsCoordinator call within 2 business days; practice visit within 7 days
What this page is doingSegments draw on the earlier stratification memo, so outreach matches each member's likely needs.
6

The workflow is simple. A notification arrives, is matched and checked for eligibility, and enters the transitions team's queue with its segment flag. A coordinator calls, confirms the member has medications and understands instructions, asks about barriers and records the result. The assigned practice receives a secure notice the same day with a request for a seven-day visit. Structured follow-up of this kind is a component of discharge programs shown to reduce return visits (Jack et al., 2009).

Data Sharing

Notices to practices will contain only the member's name, date of birth, discharge date, hospital and primary discharge diagnosis. Disclosures to treating practices are permitted under HIPAA (45 C.F.R. § 164.506). Social needs screening answers will not be shared with practices or community partners through this workflow; referrals to community resources will follow the plan's consent-based process, sharing a minimum field set with the member's agreement.

What this page is doingThe sharing section restates the minimum field rule.
7

Measurement

The rollout will be staggered: network practices will be placed in random order into four waves, starting two months apart, letting the practices still waiting act as the yardstick for those already running the workflow (Hemming et al., 2015). This design avoids the before-and-after comparison that overstated the effect of the plan's high-utilizer program, where members selected at a peak of use would have used less afterward regardless (Barnett et al., 2005). Table 4 summarizes the plan.

Table 4

Measurement Plan

MeasureDefinitionComparisonWhen reported
Seven-day follow-upPrimary care visit within 7 days of dischargeStarted versus not-yet-started practicesMonth 12, after claims mature
Thirty-day readmissionUnplanned readmission within 30 daysSameMonth 12
ReachShare of eligible discharges called within 2 business daysNot applicable; operationalMonthly
Coverage lossShare of members disenrolled within 30 days of dischargeTracked to interpret resultsMonth 12

Note. Members who lose coverage remain in the analysis using enrollment files, so results are not inflated by attrition.

What this page is doingThe measurement table names the comparison for each measure, which is what makes the result interpretable.
8

Staffing and Cost

Table 5 lists staffing by role. Costs will be presented by the finance team using the plan's salary scales; this proposal does not estimate dollar amounts.

Table 5

Staffing by Role

RoleNumberResponsibility
Transitions care coordinatorsTo be set from expected daily dischargesCalls within the response window
Community health workersShared with existing programCalls to thin-record members
Informatics analystPartial timeRouting, notices and reports
Program leadPartial time of an existing managerOversight and practice relations
What this page is doingStaffing appears by role rather than invented cost, which keeps the proposal honest.
9

Oversight

Day-to-day responsibility for the workflow sits with the care management director, who will report monthly to the quality committee on reach and response times. The informatics director will own data routing and the evaluation analysis. The privacy officer will review data sharing terms before launch. At month 12, the quality committee will receive the evaluation and advise leadership on the program's future, including whether to widen it to members outside network practices.

What this page is doingThe oversight section names who watches the program and how often.
10

What This Design Cannot Show

The design will show whether calling members and alerting practices increases seven-day follow-up visits. It may not show an effect on readmissions or emergency use within the first year, because those outcomes are less frequent and influenced by many factors beyond follow-up visits. A null result on readmission in year one would not mean the program failed. The design also cannot show effects for members not assigned to a network practice, who are excluded, or for discharges from hospitals that do not send notifications. Finally, it measures what happens when the plan acts on notifications; it does not measure the value of the exchange connection itself.

What this page is doingA dedicated section names the questions the design cannot answer.
11

Schedule

Months 1 and 2: build routing, notices and the transitions queue; hire or assign coordinators. Month 3: the first quarter of network practices goes live. Months 5, 7 and 9: the remaining three waves follow. Month 12: evaluation report to the quality committee. Leadership approval by the end of next month keeps the first wave on schedule.

What this page is doingThe schedule closes the proposal.
12

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

Condition of participation: Medical record services, 42 C.F.R. § 482.24 (2024).

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

Jack, B. W., Chetty, V. K., Anthony, D., Greenwald, J. L., Sanchez, G. M., Johnson, A. E., Forsythe, S. R., O'Donnell, J. K., Paasche-Orlow, M. K., Manasseh, C., Martin, S., & Culpepper, L. (2009). A reengineered hospital discharge program to decrease rehospitalization: A randomized trial. Annals of Internal Medicine, 150(3), 178-187. https://doi.org/10.7326/0003-4819-150-3-200902030-00007

Uses and disclosures to carry out treatment, payment, or health care operations, 45 C.F.R. § 164.506 (2024).

MMHA 6520 Week 11 instructions, in plain terms

The closing proposal in this course turns everything learned about the plan's data into one funding request. Open with a one-page summary stating the request, the population, the expected near-term result and when a decision is needed. Then move through population, data sources, segments and workflow, data sharing, measurement, staffing and cost, oversight and schedule, beginning each section with a sentence that says what it contributes to the request. Use numbered tables with APA titles and notes, and discuss each in the paragraph before it. Give the limits of your design their own section. Avoid invented dollar figures; present staffing by role and let finance cost it. Make the measurement plan strong enough to avoid the mistakes of earlier evaluations.

Inside the MMHA 6520 Week 11 example

The executive summary states the problem, request, population, expected result, design and decision date. The population section introduces Table 1's inclusion rules. The data sources section cites the federal notification rule and introduces Table 2 with delays and owners. Table 3 applies four risk segments to discharges, followed by a workflow paragraph citing Jack and colleagues. The sharing section limits practice notices to five fields under the HIPAA treatment rule. The measurement section explains four random waves, cites Hemming and colleagues and Barnett and colleagues, and introduces Table 4. Table 5 lists staffing by role. Oversight, design limits and a schedule close the proposal.

Reading the MMHA 6520 Week 11 rubric

Proposals are graded on integration and decision-readiness. An executive summary that states the request, population, expected result and decision date earns the first share. Sections that build on earlier analyses, with tables introduced and discussed, earn the largest share. A measurement plan with a credible comparison is weighted heavily, as is a frank section on what the design cannot show. Staffing presented by role rather than invented cost is credited. Clear governance and a realistic schedule complete the structure. APA table formatting, accurate references and professional tone finish the grade. Readers should be able to trace every table back to earlier analyses, and graders reward that consistency. A proposal that admits uncertainty about readmission effects is trusted more than one that promises them.

MMHA 6520 Week 11 help: mistakes that cost marks

Final proposals often grow long without growing clearer. Write the summary last and make sure a leader could approve from it. Begin each section by saying why it matters to the request. Introduce every table before it appears and say what to notice. Be honest about what the design cannot show; leaders trust that more than confident promises. Don't invent costs. Use the comparison design you developed earlier, and wait for claims to mature before reporting. Keep the schedule realistic. We can assemble a population analytics proposal from your term's assignments. Hand the summary page alone to a friend and see whether they can name the decision. Check that every number matches across sections.

Get a MMHA 6520 Week 11 example written to your instructions

For the final week, pair the prompt and rubric with your outline or earlier drafts; the complete proposal, tables formatted and citations matched, returns within 24-48h, with the first free. Plan, members and exchange are composites throughout, and nothing is drawn from any payer's analytics, contracts or member files.

More MMHA 6520 papers and MHA samples

MMHA 6520 Week 11 questions, answered

Where can I find a free MMHA 6520 Week 11 sample paper?

The full population analytics proposal, all five tables included, can be read here.

What does the MMHA 6520 Week 11 proposal request?

Money for a transitions team that acts on discharge notices, phoning members within two business days and arranging practice visits within a week.

What is the expected near-term result?

A higher share of members seen in primary care within seven days of discharge.

How will the effect be measured?

Through a staggered rollout across practices in four random waves, measured after claims are complete.

What can the design not show?

Reliable first-year effects on readmission, effects for members outside network practices and the value of the exchange connection itself.