| Course | DDHA 9901 Practice-Based Problem Identification |
|---|---|
| Week | Week 7 |
| Paper type | Stakeholder map |
| Length | About 1,060 words, 6 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 7
Who Has a Reason to Say the Discharge Summary Problem Is Imaginary: A Stakeholder Map Sorted by What the Current Arrangement Gives Each Group
Student Name
Walden University
DDHA 9901: Practice-Based Problem Identification
Instructor Name
Month Day, Year
Who Has a Reason to Say the Discharge Summary Problem Is Imaginary: A Stakeholder Map Sorted by What the Current Arrangement Gives Each Group
The Rule for Sorting
This map sorts the groups involved in Larchmont Health's discharge summary problem by what the present arrangement gives them and costs them, and by how visible the problem is from where they sit. Larchmont is a composite two-hospital system. Groups appear as roles rather than as individuals. Visibility matters most: a group that never encounters the failure has no dishonest motive for denying it, and its denial tells us about the organization's blind spots rather than about anyone's interests. The longest section concerns the groups who would dispute the framing, each paired with the counter-account they would bring.
The Map
In the salience framework of Mitchell et al. (1997), managers notice groups that can force outcomes, whose claims seem rightful and whose demands cannot wait. The independent practices have legitimacy and urgency but little power inside Larchmont, which helps explain why a problem they experience every week has never been formally recorded.
Table 1
Groups, What the Arrangement Gives and Costs Them, and Visibility
| Group | What the present arrangement gives them | What it costs them | How visible the problem is to them | |
|---|---|---|---|
| Hospitalists | Measured only on signing within the medical staff deadline, which they meet | Occasional calls from practices | Low; they never see what happens after signing | |
| Health information management | A completion rate that meets federal and medical staff rules | Handling requests for resent summaries | Moderate; they see the requests but log them as routine | |
| Interface and information technology team | A sending process that works when data are correct | Troubleshooting when practices complain | Low; failures caused by missing addresses or fields look like non-events | |
| Patient access staff | Registration that moves quickly without verifying the primary care field | Little | Very low; they never learn where summaries went | |
| Case managers | Responsibility for follow-up appointments, not for information transfer | Calls from practices about patients they discharged | Moderate | |
| Independent primary care practices | Nothing; they bear the cost | Staff time chasing summaries and clinician time at visits | High | |
| Employed primary care practices | Summaries visible in the shared record | Little | Very low; the problem does not reach them | |
| Accountable care leadership | A partnership with independent practices | Strain in that partnership, possible loss of shared savings | Moderate, through complaints | |
| Transitions committee | A proposal for a new platform already in motion | Its proposal if the problem lies elsewhere | High, but framed around its remedy | |
| Patients | Usually unaware of the gap | Visits where their clinician lacks the hospital's account | Low, though some notice | |
Roles and the characteristics recorded for them come from one interview per role and from the term's evidence log.
The Disputers and What They Would Bring
Hospitalists are likely to say the problem is not theirs. Their counter-account is the signature data, which show summaries signed within two days in most cases, far inside every deadline that applies to them. The account is accurate, and the problem framing should accept it. The evidence shows the failure is in delivery, not signing, and the identification paper should say so plainly rather than implying that hospitalists are slow.
Health information management is likely to say there is no shortfall, pointing to its completion rate, which meets the federal record completion rule. The response is that the completion rule measures whether summaries are finished, not whether they reach the next clinician, and that the benchmark comparison showed Larchmont performing well on completion while falling short against its own contract term on transmission.
The interface team is likely to argue that the sending process works and that failures come from practices without secure addresses or from inaccurate registration data. Their counter-account is largely supported by the evidence: the system sends summaries automatically when the data are right. The disagreement is about framing, not facts. The interface team would frame the problem as a data quality issue outside its responsibility; the identification paper should frame it as a gap that falls between several groups, none of which owns the whole transfer.
Patient access staff may say that the primary care field is reported by patients and that many do not know or do not state their clinician. A study of summaries at another health system found the outpatient follow-up provider frequently missing (Were et al., 2009), which suggests the weakness is common rather than peculiar to Larchmont's registration desk. The response is that the field can be verified at registration or by case managers before discharge, and that the evidence log found it blank for 11% of discharges.
The transitions committee is the most important disputer, because it has already framed the problem around a platform. It would not deny the problem but would contest the finding that the cause is registration data and unregistered practices rather than the absence of a product. Its counter-evidence would be vendor material describing improved delivery at other hospitals. The response is that those results came from settings where the causes may differ and that a platform depending on the same registration field would inherit the same failure.
The Group Without a Voice
Patients are the group most affected by the content of the summary and least represented in any discussion of it. Kripalani et al. (2007) linked failures of information transfer at discharge to risks for patients, yet no patient group or advisory council has been asked about this problem at Larchmont. The map records that absence rather than speaking for them.
Putting the Map to Work
The map will shape how the identification paper is presented. Each disputer's counter-account will be acknowledged in the paper, with the evidence that answers it, so that no group reads the paper as blaming it for a failure that belongs to the whole path. The paper will be shared first with the physician liaison and accountable care leadership, who see the problem most clearly from inside, and then with the other groups together.
What the Map Shows
No group owns the whole path from signature to delivery. Each group can accurately say that its own part works, and each is measured on its own part. That is the structural reason the problem has persisted, and it is the finding the stakeholder map adds to the case.
References
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
Mitchell, R. K., Agle, B. R., & Wood, D. J. (1997). Toward a theory of stakeholder identification and salience: Defining the principle of who and what really counts. Academy of Management Review, 22(4), 853-886. https://doi.org/10.2307/259247
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 7 instructions ask for
For Week 7, the groups tied to your problem are mapped by where they stand and why. List groups as roles, not individuals. For each, record what the present arrangement gives them, what it costs them and how visible the problem is from their position, since a group that never sees the failure has no dishonest motive for denying it. Give the longest section to the groups likely to dispute your framing, and for each, state the counter-evidence they would bring and how you would answer it. Accept counter-accounts that are accurate and adjust your framing accordingly. Note any affected group without a voice. Close with what the map reveals about why the problem persists.
Inside the DDHA 9901 Week 7 example
The map explains its sorting rule. Table 1 covers hospitalists, health information management, the interface team, patient access, case managers, independent and employed practices, accountable care leadership, the transitions committee and patients. A paragraph applies the salience model to explain the practices' lack of influence. The disputers section takes five groups, accepting the hospitalists' signature data, answering health information management's compliance claim, treating the interface team's view as a framing dispute, citing Were and colleagues on registration weaknesses and contesting the transitions committee's platform framing. A section notes patients' absence. A section explains how the map will shape the paper's presentation, and the conclusion identifies the ownerless path.
Where the marks sit in the DDHA 9901 Week 7 rubric
Stakeholder maps are graded on insight into positions, not on listing groups. Markers look for roles described by what the arrangement gives and costs them and by their visibility of the problem. The disputers section usually carries the most weight, especially when counter-accounts are taken seriously and accurate ones change the framing. Identifying groups without a voice shows ethical awareness. A conclusion that explains persistence structurally earns credit. Theories of stakeholder salience should be used to explain behavior. Clear tables and fair language about each group are expected. Graders reward maps whose disputers section could be handed to those groups without embarrassment, because it treats their views fairly. Maps that explain persistence through structure rather than personal failings are generally the strongest.
DDHA 9901 Week 7 help: mistakes that cost marks
Students often map stakeholders as supporters and opponents without asking why. Ask what each group gets from the current arrangement and whether it can even see the problem. Take the disputers seriously; some will be right about their own part. Adjust your framing when they are. Avoid language that blames individuals. Look for the group affected but absent from every discussion. If you need a stakeholder map for a problem in your setting, we can build one with the disputers given their due. Before finishing, imagine each disputer reading their row; if any would call it unfair, revise the wording while keeping the evidence. Note also any group whose visibility of the problem might change soon, since positions shift when visibility does.
Get a DDHA 9901 Week 7 example written to your instructions
Send the map prompt, the rubric and the setting description it is drawn from, and a finished map with the objection pairs written out returns inside 24-48 hours, the first sample free. Names of actual staff and units never enter the work; every group appears as a role.
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 8: Provenance Critique
- DDHA 9901 Week 9: Scope Boundary
- DDHA 9901 Week 10: Identification Paper
- DDHA 9901 Week 11: Reflection Post
- DDHA 9500 Week 7: Approach Outline
- DDHA 8801 Week 7: Community Notice
- DDHA 8703 Week 7: Adjusted Comparison
- DDHA 8006 Week 7: Doctoral Position Paper
DDHA 9901 Week 7 questions, answered
Where can I find a free DDHA 9901 Week 7 sample paper?
The discharge summary stakeholder map is free to read on this page.
How does the DDHA 9901 Week 7 map sort stakeholders?
By what the current arrangement gives and costs each group and how visible the problem is to them.
Who would dispute the problem framing?
Hospitalists, health information management, the interface team, patient access and the transitions committee.
Which counter-account does the map accept?
The hospitalists' evidence that they sign summaries quickly, which shifts the problem to delivery.
Why has the problem persisted?
Each group can show its own step works, while no group owns the path from signing to arrival.