HA599 Unit 2 Capstone Project Proposal Example

Reviewed by Chester Goodwin, MBA Master's Capstone in Health Care Administration Purdue University Global Free custom sample in 24 to 48h

This HA599 Unit 2 project proposal draws the boundary of a capstone on slow ambulance handoffs at a composite hospital as carefully as it states the aim. It was written for Purdue Global HA 599, Master's Capstone in Health Care Administration, in the Master of Health Administration (MHA). Offload time is defined as the minutes from an ambulance's arrival at the door to a nurse's signature, and the project covers only noon to midnight, when about 78 percent of long waits occur. The aim is a 90th percentile below 45 minutes within three months of opening a staffed arrival point. Benefits are stated in the organization's terms, each exclusion carries its reason, the leading solution is named but left open, and a stakeholder list states what each party needs before agreeing.

CourseHA599 Master's Capstone in Health Care Administration
UnitUnit 2
Paper typeProject proposal
LengthAbout 870 words, 6 pages double-spaced
FormatAPA 7 student paper
SchoolPurdue University Global
ProgramMaster of Health Administration (MHA)
UpdatedOctober 2026

Free sample paper for HA599 Unit 2

1

Noon to Midnight, One Door, One Signature: A Capstone Project Proposal on Slow Ambulance Handoffs at a Composite Hospital's Emergency Department, Drawing the Boundary as Carefully as the Aim and Naming Who Has to Agree

[Student Name]

Purdue University Global

HA599: Master's Capstone in Health Care Administration

Unit 2 Project Proposal

[Instructor Name]

[Date]

The hospital, the county and every figure are composite and bracketed for the writer's own data.

What this part is doingThe boundary gets the most words, because a graduate reviewer approves scope before anything else.
2

Summary

This project will measure ambulance handoff delay at Tessford's emergency department between [12:00] and [00:00], appraise the evidence on staffed arrival points, and, if justified, propose a twelve-month pilot of a nurse-staffed arrival point for ambulance patients. Deliverables over ten units: a needs assessment, an evidence appraisal, feasibility and financial analyses, an implementation timeline, a risk register, an evaluation plan and an executive presentation.

Problem and Measure

Offload time is the minutes between an ambulance's arrival at the emergency department door, recorded by the county's electronic care report, and a nurse's signature accepting the patient. A first look at run records places [78] percent of waits over [30] minutes between [12:00] and [00:00].

Aim

Reduce the 90th percentile of offload time between [12:00] and [00:00] from [71] minutes to under [45] minutes within [90] days of opening an arrival point, without lengthening waits for walk-in patients.

Benefits, in the Organization's Terms

Crews returned to the county sooner, improving the relationship with the county EMS medical director, who has written twice this year. Fewer diversion hours, and with them fewer admissions lost to other hospitals. Less overtime for the triage and charge nurses who now cover handoffs. Benefits are stated as directions, not amounts, because no financial work has been done yet; Unit 6 will price them.

Boundary: What the Project Excludes

Inpatient boarding. It drives much of the delay, but it belongs to bed management and a separate improvement team. Excluding it keeps this project achievable; the risk register will watch for boarding spilling into the arrival point. Walk-in waiting times. They will be watched so the project does not shift delay onto them, but improving them is not the aim. County dispatch and staffing. The project will not change where the county sends ambulances or how it staffs them. Overnight hours. Volume between [00:00] and [12:00] is too thin to test a staffed solution. Every exclusion has a reason, so a reviewer can disagree with one without rejecting the project.

Why a Local Project Is Useful

National guidance treats offload delay as a shared responsibility of hospitals and EMS systems (Cooney et al., 2011), and research focused on the delay itself, rather than crowding in general, remains limited (Li et al., 2019). One study found that delayed high-acuity patients did not have worse mortality than matched patients, but did spend longer in the department (Stewart et al., 2019), which suggests the main costs are to EMS availability and department flow rather than direct harm, a point the needs assessment will test locally.

What a Staffed Arrival Point Would Look Like

The leading candidate, to be tested in later units, is a small area near the ambulance entrance with room for [four] stretchers, staffed from [12:00] to [00:00] by a registered nurse who accepts every ambulance patient on arrival, takes report, completes a rapid assessment and moves the patient to a bed or triage queue as space opens. Crews would leave as soon as the nurse signs. The idea is not new; versions have been tried in Canada and Australia with mixed results, which the evidence appraisal will weigh. Naming the candidate now lets stakeholders react early, while making clear that the needs assessment could still point elsewhere, for example toward faster triage rather than a new space.

What this part is doingNaming the likely solution early, while keeping it open to change, lets stakeholders shape it rather than resist it later.
3

Stakeholders and Consent

Chief nursing officer, sponsor: approves the project and later the pilot. Needs: evidence and a cost estimate. Emergency department director and nurse manager: own the process. Need: staffing that does not weaken triage. County EMS medical director: shares run data and must agree to any change in where crews go. Needs: shorter waits. House supervisor: owns diversion decisions and logs. Facilities and the fire marshal: approve any use of space near the ambulance entrance. Informatics: builds any time-stamp capture. Finance: prices costs and benefits. Emergency nurses: will staff the arrival point. Need: a voice in its design.

What this part is doingThe stakeholder list states what each party needs, which is the start of getting their agreement.
4

Data and Access

County electronic care reports under the existing quality agreement; the emergency department tracking board; diversion logs; overtime records from payroll. The privacy officer has confirmed that matched records will be used for operations improvement under the hospital's existing policies, with no identifiers leaving the hospital.

Timeline Across Ten Units

Units 3 to 4: measure and appraise. Units 5 to 6: test feasibility and cost. Units 7 to 9: plan implementation, risk and evaluation. Unit 10: present to executives.

Risks to the Project Itself

County data may arrive late; the house supervisor's logs may be incomplete; the sponsor may change. Each has a fallback, such as using one month of data if a full quarter is not available.

Approval Requested

Approval to proceed with Units 3 to 10, with access to the data listed above and a monthly check-in with the sponsor.

5

References

Cooney, D. R., Millin, M. G., Carter, A., Lawner, B. J., Nable, J. V., & Wallus, H. J. (2011). Ambulance diversion and emergency department offload delay: Resource document for the National Association of EMS Physicians position statement. Prehospital Emergency Care, 15(4), 555-561. https://doi.org/10.3109/10903127.2011.608871

Li, M., Vanberkel, P., & Carter, A. J. E. (2019). A review on ambulance offload delay literature. Health Care Management Science, 22(4), 658-675. https://doi.org/10.1007/s10729-018-9450-x

Stewart, D., Lang, E., Wang, D., & Innes, G. (2019). Are emergency medical services offload delay patients at increased risk of adverse outcomes? CJEM, 21(4), 505-512. https://doi.org/10.1017/cem.2018.478

HA599 Unit 2 instructions, in plain terms

Unit 2 in HA 599 usually asks students to submit a formal capstone proposal. Instructions often require a summary, problem statement, aim, scope, benefits, stakeholders, data sources, a timeline across the remaining units and an approval request. Define the measure precisely, because later units depend on it. Write an aim with a number and a time frame. Spend real effort on scope: list what the project excludes and give a reason for each, since reviewers approve scope before anything else. State benefits as directions until financial work is done. List stakeholders with what each needs, not just their titles. Cite sources that show the problem is recognized and that evidence on solutions is limited, in APA style.

How the HA 599 Unit 2 example is put together

The sample opens with a summary a vice president could read standing up, with a margin note on why the boundary gets the most words. The problem and measure follow, then an aim with a target. Benefits are framed for the organization. Four exclusions each carry a reason, and a highlighted line notes that a reviewer can reject one without rejecting the project. A section on why a local project is useful cites national guidance and outcome research. The leading solution is described with a margin note on naming it early. Stakeholders are listed with their needs, flagged by a third note. Data access, a ten-unit timeline, project risks and an approval request close the proposal.

HA599 Unit 2 rubric: what earns full points

HA 599 proposal rubrics generally award points for a precise problem and measure, a specific aim, a well-reasoned scope, organizational benefits, stakeholder analysis, feasible data access, a realistic timeline, sources and presentation. Measure points go to a definition others could apply. Aim points reward a target and date. Scope points depend on exclusions with reasons. Benefit points go to gains stated in the organization's terms. Stakeholder points reward naming what each party needs. Data points require confirmed access. Proposals whose exclusions are each defended in a sentence tend to be graded highest, because scope is where capstones most often fail. Timelines earn credit when each remaining unit has a named deliverable.

HA599 Unit 2 help from the desk

Proposals often lose points by leaving the scope loose, so new questions keep attaching themselves until the term runs out. Others promise financial benefits before any analysis, or list stakeholders without saying what they need. Define your measure exactly. State the aim as a target figure reached by a set date. List what you will not do and why, especially anything that drives the problem but sits outside your reach. Describe benefits as directions until you have priced them. Name each stakeholder and what would win their agreement. Confirm data access in writing. Lay out which unit produces which deliverable, and ask for a specific approval. Finally, keep the proposal short enough that a busy sponsor will read all of it.

Get an HA599 Unit 2 example written to your instructions

Share the problem you settled on after the first board, a rough sense of how big it is, and who would have to approve a fix. With the Unit 2 proposal instructions and rubric attached, a first sample proposal is written free in 24-48h, its boundary and exclusions drawn to fit your setting. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More HA599 papers and MHA samples

HA599 Unit 2 questions, answered

Where can I find a free HA599 Unit 2 sample paper?

The complete HA599 Unit 2 project proposal is here, scoping a capstone on slow ambulance handoffs at one composite emergency department.

How is offload time defined in HA599 Unit 2?

The minutes from an ambulance's arrival at the door to a nurse's signature accepting the patient.

What does the proposal exclude?

Inpatient boarding, walk-in waits, county dispatch and the overnight hours, each with a reason.

What is the project's aim?

To bring the slowest tenth of handoffs between noon and midnight under 45 minutes within 90 days.

How long is the HA599 Unit 2 proposal?

About five pages with a stakeholder list.