| Course | DDHA 9901 Practice-Based Problem Identification |
|---|---|
| Week | Week 9 |
| Paper type | Scope boundary document |
| Length | About 770 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Healthcare Administration (DHA) |
| Updated | October 2026 |
Free sample paper for DDHA 9901 Week 9
Cutting the Discharge Summary Problem to a Size One Project Can Finish: Four Boundary Passes, Each Cut Recorded, and Where Every Removed Piece Went
Student Name
Walden University
DDHA 9901: Practice-Based Problem Identification
Instructor Name
Month Day, Year
Cutting the Discharge Summary Problem to a Size One Project Can Finish: Four Boundary Passes, Each Cut Recorded, and Where Every Removed Piece Went
The Problem at the Size the Evidence Supports
The evidence gathered this term supports a wide problem: across Larchmont Health, a composite two-hospital system, information about a patient's hospital stay often fails to reach the clinicians responsible for care after discharge. That statement covers medical and surgical patients, obstetric patients, patients going to skilled nursing facilities, emergency visits where the patient goes home from the department, the content of the summary as well as its delivery and every period for which records exist. No single project could close it. Four boundary passes follow, each cutting on a different axis.
Pass 1: Population
Kept: adults discharged home from the medical services. Excluded: surgical patients, obstetric patients and patients discharged to skilled nursing facilities.
Surgical summaries are written by surgeons through a different template and often supplemented by clinic notes; that is a later project, which could reuse this one's measure. Obstetric patients are followed by obstetric clinicians rather than primary care, and their discharge information belongs to the women's services leadership, so that portion is somebody else's problem. Patients going to skilled nursing facilities receive a transfer packet through a separate process that the post-acute coordination team owns; it is also somebody else's problem, and the evidence gathered here does not cover it.
Pass 2: Setting
Kept: both hospitals, and only patients whose primary care clinician practices outside the shared record. Excluded: patients of employed practices and emergency visits where nobody is admitted.
Employed practices see summaries immediately in the shared record, and the evidence shows no shortfall there, so including them would dilute the measure. Emergency department discharge notes follow a different workflow under emergency services leadership; that is a later project. Keeping both hospitals is a deliberate choice, because the smaller hospital refers more patients to independent practices and dropping it would hide part of the problem.
Pass 3: Mechanism
Kept: delivery, meaning whether the summary reaches the outside clinician within two business days. Excluded: the content of the summary and whether clinicians read it.
Content matters. Pending test results and the follow-up provider are often missing from summaries elsewhere (Were et al., 2009), and the same may be true here. But improving content is a different project with a different owner, the hospitalist group's documentation committee, and it should follow once delivery is reliable, since a better summary that does not arrive helps no one. Whether outside clinicians open and read what arrives cannot be reached from inside Larchmont, because it happens in other organizations' record systems. That piece is recorded as unreachable from here.
Pass 4: Period
Kept: discharges from June through August 2026 for the full transmission measure, with March through May included for secure messages only. Excluded: anything earlier.
The fax server purged its log after 90 days, so failures before June cannot be traced. Extending the period would mean counting only secure messages and treating every fax as unknown, which would overstate the problem. Earlier periods are unreachable rather than deferred.
What Remains
After the four passes, the project's problem is this: for adult medical patients sent home from either hospital to an outside primary care practice, discharge summaries reach that clinician within two business days only about half the time, against a contract term that promises delivery within that window. That problem has a measure, a baseline, an owner who could act and a period short enough to finish. Kripalani et al. (2007) describe information transfer at discharge as failing at many points, and this project chooses one of them deliberately.
Where the Removed Pieces Went
The pieces sent to other owners will be described in a short note to each, so that the boundary does not become a way of losing them. Hoyer et al. (2016) linked timeliness to readmissions across settings, which suggests that several of the removed pieces deserve projects of their own.
Table 1
Pieces Removed and Their Destination
| Removed piece | Axis | Destination | |
|---|---|---|
| Surgical discharges | Population | Later project, reusing this measure | |
| Obstetric discharges | Population | Women's services leadership | |
| Discharges to skilled nursing facilities | Population | Post-acute coordination team | |
| Employed practice patients | Setting | No shortfall found; not needed | |
| Emergency department discharges | Setting | Later project under emergency services | |
| Summary content | Mechanism | Hospitalist documentation committee, after delivery is fixed | |
| Whether clinicians read summaries | Mechanism | Unreachable from inside the organization | |
| Periods before June 2026 | Period | Unreachable; fax records purged | |
Each removal names a destination so that the boundary records a decision rather than an omission.
References
Hoyer, E. H., Odonkor, C. A., Bhatia, S. N., Leung, C., Deutschendorf, A., & Brotman, D. J. (2016). Association between days to complete inpatient discharge summaries with all-payer hospital readmissions in Maryland. Journal of Hospital Medicine, 11(6), 393-400. https://doi.org/10.1002/jhm.2556
Kripalani, S., LeFevre, F., Phillips, C. O., Williams, M. V., Basaviah, P., & Baker, D. W. (2007). Deficits in communication and information transfer between hospital-based and primary care physicians: Implications for patient safety and continuity of care. JAMA, 297(8), 831-841. https://doi.org/10.1001/jama.297.8.831
Were, M. C., Li, X., Kesterson, J., Cadwallader, J., Asirwa, C., Khan, B., & Rosenman, M. B. (2009). Adequacy of hospital discharge summaries in documenting tests with pending results and outpatient follow-up providers. Journal of General Internal Medicine, 24(9), 1002-1006. https://doi.org/10.1007/s11606-009-1057-y
What the DDHA 9901 Week 9 instructions ask for
The scope boundary week usually asks you to reduce a problem you have demonstrated to something one project can address. Begin with the problem at the size your evidence supports, which is usually larger than any project. Then make boundary passes on different axes, such as population, setting, mechanism and period. For each pass, state what you kept, what you excluded and why, and whether each excluded part is someone else's problem, a later project's problem or simply unreachable from your position. Do not pretend the removed pieces disappear. Close with a clear statement of what remains and a table recording where each removed piece went. The boundary should read as a set of decisions rather than omissions.
How the DDHA 9901 Week 9 example is put together
The document opens with the problem at full size, covering every discharge type, content and period. The population pass keeps adult medical discharges home and assigns surgical, obstetric and skilled nursing discharges to a later project or other owners. The setting pass keeps both hospitals and outside practices and explains why the smaller hospital stays. The mechanism pass keeps delivery, defers content to the documentation committee and marks reading as unreachable. The period pass explains why records before June cannot be traced. A section states the remaining problem with its measure, baseline and owner. Table 1 lists eight removed pieces and their destinations, and a closing note commits to telling each owner.
DDHA 9901 Week 9 rubric: what earns full marks
Scope boundaries are graded on transparency and realism. Markers look for the problem stated first at the size the evidence supports. Each pass should cut on a distinct axis with reasons. Classifying each removed piece as someone else's, a later project's or unreachable shows that the writer has thought about consequences. A clear statement of what remains, with a measure and a period, demonstrates that the project is now finishable. A table of destinations is often a specific criterion. Boundaries that quietly drop parts of the problem lose credit. Sources should support decisions about what matters and what can wait.
Common DDHA 9901 Week 9 mistakes, and how to avoid them
Students often narrow their problem without saying what they cut. Record every exclusion and where it goes. Make your passes on different axes so the logic is visible. Be honest about pieces you cannot reach, such as events inside other organizations. Keep pieces that make the problem harder if they are central, and explain why. Check that what remains still connects to your evidence and comparison. If your problem keeps growing, we can help you set boundaries that a committee will accept. Test the final scope by asking whether one project team could finish it within your program's timeline; if not, make another pass. Send a short note to each owner of a removed piece so the boundary does not quietly lose them.
Get a DDHA 9901 Week 9 example written to your instructions
Send the prompt, the rubric and the problem statement as it currently stands, and a bounded version with all four narrowing passes and their exclusions written out arrives inside 24-48 hours, free the first time. Proprietary policy documents sitting inside a real employer remain where they are, and none is reproduced.
More DDHA 9901 papers and DHA samples
- DDHA 9901 Week 1: Complaint Testing Post
- DDHA 9901 Week 2: Context Memo
- DDHA 9901 Week 3: Problem Statement
- DDHA 9901 Week 4: Evidence Log
- DDHA 9901 Week 5: Benchmark Comparison
- DDHA 9901 Week 6: Cost Estimate
- DDHA 9901 Week 7: Stakeholder Map
- DDHA 9901 Week 8: Provenance Critique
- DDHA 9901 Week 10: Identification Paper
- DDHA 9901 Week 11: Reflection Post
- DDHA 9500 Week 9: Alignment Check
- DDHA 8801 Week 9: Due Diligence Memo
- DDHA 8703 Week 9: Predictive Model Brief
- DDHA 8006 Week 9: Evidence to Practice Application
DDHA 9901 Week 9 questions, answered
Where can I find a free DDHA 9901 Week 9 sample paper?
The discharge summary scope boundary document is free to read on this page.
What four axes does the DDHA 9901 Week 9 example cut on?
Population, setting, mechanism and period.
Why is summary content excluded?
Improving content is a separate project for the documentation committee and should follow once delivery is reliable.
Which piece is unreachable?
Whether outside clinicians read summaries, which happens inside other organizations' record systems.
What problem remains after the cuts?
Summaries reach outside practices within two business days only about half the time for adult medical discharges home.