HLTH 6882 Week 6 Healthcare Change Proposal Paper Example

Improving Healthcare Performance Through Social Entrepreneurship Walden University Free custom sample in 24 to 48h

This HLTH 6882 Week 6 change proposal example describes one change down to who does what differently on a Monday morning: Prairie Bend stops booking referrals on arrival and adopts a holding list, slots that open three weeks out, a list of patients able to come at short notice and reminders a week ahead, run by an outreach coordinator function carved from scheduler hours. Walden HLTH 6882 wants graduate health administration program students to show the mechanism, and the paper links each component to the root cause and benchmark, citing Dantas and colleagues and Gurol-Urganci and colleagues. It names what staff stop doing, uses Dees to justify asking county aging offices for short-notice rides, checks the change against contract, software and staffing in a table that includes one conflict, protects patients who might be harmed and lists exclusions, citing Murray and Berwick.

CourseHLTH 6882 Improving Healthcare Performance Through Social Entrepreneurship
WeekWeek 6
Paper typeChange proposal paper
LengthAbout 1,020 words, 6 pages
FormatAPA 7 student paper
SchoolWalden University
Programgraduate health administration program
UpdatedOctober 2026

Free sample paper for HLTH 6882 Week 6

1

Change Proposal: A Three-Week Booking Window and Short-Notice List for Prairie Bend's Visiting Specialist Clinic

Student Name

Walden University

HLTH 6882: Improving Healthcare Performance Through Social Entrepreneurship

Instructor Name

Month Day, Year

What this page is doingThe title names one change with its two parts, which signals that everything below explains how that change works.
2

Change Proposal: A Three-Week Booking Window and Short-Notice List for Prairie Bend's Visiting Specialist Clinic

The Change in One Paragraph

Prairie Bend Community Hospital will stop booking specialist referrals into the next open slot on arrival. Instead, non-urgent referrals will go onto a holding list, and each session day's slots will open for booking three weeks before the session. Patients on the holding list will be asked whether they can come at short notice, and those who can will form a short-notice list. When a booked patient cancels late, the slot will be offered to patients on that list. A one-week text reminder with a reply-to-cancel option will be added. These tasks will belong to an outreach coordinator function of about ten hours a week, carved from hours the scheduler already works, with registration coverage on clinic days shifted to a float clerk. Urgent referrals will still be booked immediately. Figures throughout describe a composite hospital and are illustrative.

What this page is doingStating the change at the top lets the reader test every later section against it.
3

Mechanism

Each component of the change acts on a specific link in the cause chain traced in Week 4.

The three-week window acts on the root cause directly. Lost slots were concentrated in visits booked 43 or more days ahead, which were lost at a rate of 37%, compared with 10% for visits booked within three weeks. The window removes most long-lead bookings by design, moving visits into the lead time band where the clinic already keeps 90% of slots. The mechanism rests on the clinic's own data and on a systematic review that ranked lead time among the strongest recurring predictors of no-shows (Dantas et al., 2018).

The short-notice list acts on late cancellations, which were 30% of lost long-lead slots. A slot freed late is currently lost; with the list, it can be refilled. Cedar Ford, the peer hospital, refills about half of late cancellations this way.

The one-week text reminder acts on forgetting, the most common reason in the scheduler's call-back notes. A Cochrane review pooled trials showing that texted reminders raise attendance relative to sending none (Gurol-Urganci et al., 2013). The reply-to-cancel option turns some no-shows into cancellations early enough for the short-notice list to fill.

The coordinator function acts on the fourth link in the chain: bookings made whenever the scheduler had a free moment between registration tasks. Giving the booking work protected hours makes the window and the list possible to run.

What this page is doingEach component is linked to the root cause and the benchmark evidence, which is the part the rubric weighs most.
4

Roles: What Staff Start and Stop Doing

The scheduler will become the outreach coordinator for about ten hours a week, spread across two afternoons and the mornings before each session day. In those hours, the coordinator manages the holding list, opens slots three weeks ahead, books patients, keeps the short-notice list and calls it after late cancellations.

The scheduler will stop covering outpatient registration on the four session days a month, when registration is busiest; a float clerk from the business office will cover those shifts. The scheduler will also stop the current practice of calling no-shows after each session to rebook them, because the holding list and the window replace it. The reminder letter mailed at booking will be discontinued, since the text reminder replaces it. These stopped tasks account for most of the coordinator hours; the remainder comes from the float clerk's coverage.

What this page is doingNaming what staff stop doing shows the proposal does not assume free capacity.
5

Reaching Past the Hospital's Own Resources

Patients on the short-notice list must be able to reach the clinic at a day or two's notice, and some may need a ride. Prairie Bend does not run transport and should not start. J. Gregory Dees described social entrepreneurship as pursuing opportunities without being limited by resources currently held (Dees, 2007). Applied here, the hospital can ask the two counties' aging offices, which run volunteer driver programs for older residents, to accept short-notice ride requests for patients called from the list. This does not respond to transport as a general cause, which the root cause analysis rejected. It responds to a narrow need the new process creates.

What this page is doingThe Dees reference changes the proposal by adding a partner, not by decorating the conclusion.
6

Constraints

The change was checked against the clinic's main constraints.

Table 1

Constraints Check for the Booking Change (Illustrative)

ConstraintRequirementFit with the change
Specialist session contractSession dates confirmed 60 days aheadFits: dates are still confirmed 60 days ahead; only patient booking moves to 3 weeks
Specialist contract noticeGroup asks for patient lists 1 week aheadFits: lists are complete 3 weeks ahead and updated from the short-notice list
Scheduling softwareSlot templates can be released by dateFits, pending vendor confirmation; holding list kept as a work queue
Text remindersRequires a vendor moduleConflict: module not licensed; cost to be confirmed in the business case
Staff hoursNo new positionsFits if float clerk covers 4 clinic days a month
Urgent referralsMust not wait for the windowFits: urgent flag books immediately
What this page is doingThe constraints table checks the change against arrangements someone could verify, including a conflict.
7

Patients Who Might Be Harmed

Two groups could be worse off. Patients whose referrals are not flagged urgent, but should have been, would now wait on the holding list instead of holding a booked date. The proposal handles this by asking the coordinator to call any referring provider whose referral has waited more than six weeks unbooked. Patients without a mobile phone would not receive text reminders; for them, the coordinator will make a reminder call. Both safeguards will be monitored in the pilot. A third group, the specialist groups themselves, could be affected if patient lists arrive later than they are used to. The proposal answers this by sending each group its list one week ahead, as the contract asks, and by sharing the short-notice list's results with the groups after each session so they can see whether their days are fuller.

What this page is doingThe proposal names who could be worse off and how that risk is handled.
8

What the Proposal Excludes

The proposal does not add session days, change the specialist contracts, start a hospital transport service, introduce telehealth visits or change the referral criteria. Each may have merit, but none addresses the diagnosed cause, and including them would make it impossible to tell which part of a change produced any improvement. Advanced access work warns that clinics often add capacity when the real problem is how existing capacity is booked (Murray & Berwick, 2003); this proposal tests the booking rule first.

What this page is doingStating exclusions keeps the change narrow enough to test.
9

References

Dantas, L. F., Fleck, J. L., Cyrino Oliveira, F. L., & Hamacher, S. (2018). No-shows in appointment scheduling: A systematic literature review. Health Policy, 122(4), 412-421. https://doi.org/10.1016/j.healthpol.2018.02.002

Dees, J. G. (2007). Taking social entrepreneurship seriously. Society, 44(3), 24-31. https://doi.org/10.1007/BF02819936

Gurol-Urganci, I., de Jongh, T., Vodopivec-Jamsek, V., Atun, R., & Car, J. (2013). Mobile phone messaging reminders for attendance at healthcare appointments. Cochrane Database of Systematic Reviews, (12), Article CD007458. https://doi.org/10.1002/14651858.CD007458.pub3

Murray, M., & Berwick, D. M. (2003). Advanced access: Reducing waiting and delays in primary care. JAMA, 289(8), 1035-1040. https://doi.org/10.1001/jama.289.8.1035

HLTH 6882 Week 6 instructions, in plain terms

Change proposals in this course usually ask for one change described precisely enough to carry out. State the change in one paragraph at the top. Then explain the mechanism: link each component to the specific cause you traced and to evidence, such as benchmark practice or published studies, so a reader could argue with how it should work. Describe roles, including what staff stop doing, because a proposal that only adds duties assumes capacity the organization does not have. Check the change against real constraints, such as contracts, software and staff hours, and admit any conflict. Say which patients or staff might end up worse off, and what protects them. List what the proposal deliberately excludes, so the change stays narrow enough to test and its effect can be attributed.

Inside the HLTH 6882 Week 6 example

The opening states the whole change in one paragraph. The mechanism section links the window to the lead time data and Dantas and colleagues, the short-notice list to late cancellations, the reminder to forgetting and Gurol-Urganci and colleagues and the coordinator function to the scheduler's divided job. The roles section lists what the scheduler starts and stops doing and how the float clerk covers registration. A section uses Dees to justify asking county aging offices for short-notice rides. Table 1 checks six constraints, including a software conflict. A section names patients and specialist groups who could be affected. The final section lists exclusions, citing Murray and Berwick.

Reading the HLTH 6882 Week 6 rubric

Top marks go to a mechanism a reader could argue with: proposals that describe a change and assert it will work skip the part the rubric weighs most. Fit with the diagnosed cause is scored next, and a change aimed at a rejected cause contradicts the paper's own evidence. Roles earn credit for naming what staff stop doing. The constraints table is rewarded for honesty, including any conflict found. Naming who could be harmed, with safeguards, shows responsibility. A course thinker used to change the proposal, not to decorate it, adds credit. Exclusions that keep the change testable show discipline. Precise language throughout lets the pilot and business case build on the proposal.

HLTH 6882 Week 6 help from the desk

Change proposals often bundle several ideas, such as new software, extra sessions and a transport program, so no one could tell which worked. Others describe the change without explaining why it should fix the cause. Begin with one paragraph stating exactly what changes. Then write one sentence for each component that begins with because, linking it to your cause analysis. List the tasks each affected role will stop doing, then check every constraint you know of and record conflicts honestly. Finally, write down what you are leaving out and why. We can write a change proposal for your organization with a mechanism tied to the cause you traced.

Get a HLTH 6882 Week 6 example written to your instructions

Send the root cause and benchmark work alongside the Week 6 prompt and rubric, and the proposal builds its mechanism from them. Your first sample carries no fee and comes back in 24 to 48 hours. The outreach coordinator, the float clerk and the county drivers were all made up for this page.

More HLTH 6882 papers and graduate health administration program samples

HLTH 6882 Week 6 questions, answered

Where can I find a free HLTH 6882 Week 6 sample paper?

Open this page to read the complete change proposal; there is no charge.

What change does the HLTH 6882 Week 6 proposal make?

Referrals wait on a holding list instead of being booked on arrival, slots open only three weeks before each session, late cancellations go to patients who can come quickly and reminders go out a week ahead.

Who runs the new process?

The scheduler, working about ten hours a week as outreach coordinator, with a float clerk covering registration on session days.

What do staff stop doing?

Covering registration on session days, rebooking calls after no-shows and mailing reminder letters.

What conflict does the constraints check find?

The text reminder module is not licensed, so its cost must be confirmed in the business case.