| Course | DDHA 8503 Strategic Management and Systems Thinking |
|---|---|
| Week | Week 6 |
| Paper type | Doctoral discussion post with two replies |
| Length | About 610 words, 4 pages |
| Format | Discussion post, APA 7 citations |
| School | Walden University |
| Program | Doctor of Healthcare Administration (DHA) |
| Updated | October 2026 |
Free sample paper for DDHA 8503 Week 6
Week 6 Discussion: Where Does the System End?
Draw the Line at the Clinic Walls and the Portal, and Admit That It Hides Nineteen Thousand Notifications a Week
I would draw the boundary of Brightwater Medical Group's messaging system around its fourteen clinics, its nurse triage pool and its patient portal, and treat the record system's notification design and payers' billing rules as fixed conditions, even though that choice pushes one of the largest causes of inbox load out of view. Inside the line are patients' messages, the routing rules, the people who answer, the phone queue that absorbs converted messages and the appointments some messages end in. Outside it are the vendor that designs the software and the payers that decide what messaging can be billed.
This boundary makes the system analyzable in a way Brightwater can act on. Every variable inside it is something the group controls or can influence within a year: who answers which messages, how many nurses staff triage, how many visit slots are held for messages that need a visit. Meadows (2008) warns that boundaries should be drawn for the question being asked, not for the convenience of the organization chart. The question here is what Brightwater can change to slow the reinforcing loop between its inbox and its clinic hours, and a boundary drawn around its own operations matches that question.
The cost is real, and it is concentrated in one place. The largest flow into clinicians' inboxes is not patient messages but automated notifications: about 19,000 a week, against about 4,700 patient messages that reach clinicians. These include result releases, refill confirmations and system alerts, and they are shaped by the vendor's defaults and by configuration choices made years ago. Tai-Seale et al. (2019) found burnout more common among physicians receiving many system-generated inbox items, so the boundary I propose excludes a cause that probably matters more than several I included. If the vendor changed its defaults, or if Brightwater decided its configuration was within reach after all, that excluded cause could move and outweigh any change inside the line. Calling the notification stream fixed is a choice, not a fact.
No boundary is neutral, but that does not mean every boundary is equally arbitrary. Sterman (2000) describes the model boundary as a decision about which variables are endogenous, explained by the model's feedback, and which are exogenous, taken as given. Mine treats patient behavior as endogenous and software behavior as exogenous. I can defend that for a first analysis, as long as the report says plainly what was excluded and how large it is.
Reply to Renata
Renata, you drew your boundary around the emergency department alone and treated inpatient bed availability as fixed. I would push your line outward by one step. Your own description says boarding patients occupy a third of your treatment rooms by evening, which makes inpatient discharge timing a driver of the very waits you want to analyze. Treating it as fixed means your loop analysis will find causes only inside the department, where the room to act may be smallest. Would you consider including the discharge process even if your department does not control it?
Reply to Felix
Felix, I think your boundary for the pharmacy prior authorization system is too wide. Including every payer's formulary policy makes the system so large that nothing inside it is under your organization's control. I would pull the line in to your own intake, review and appeal process and treat payer policies as fixed, while listing them openly as excluded drivers. You would lose the ability to model payer behavior, but you would gain an analysis your managers could act on next quarter.
References
Meadows, D. H. (2008). Thinking in systems: A primer (D. Wright, Ed.). Chelsea Green.
Sterman, J. D. (2000). Business dynamics: Systems thinking and modeling for a complex world. Irwin/McGraw-Hill.
Tai-Seale, M., Dillon, E. C., Yang, Y., Nordgren, R., Steinberg, R. L., Nauenberg, T., Lee, T. C., Meehan, A., Li, J., Chan, A. S., & Frosch, D. L. (2019). Physicians' well-being linked to in-basket messages generated by algorithms in electronic health records. Health Affairs, 38(7), 1073-1078. https://doi.org/10.1377/hlthaff.2018.05509
DDHA 8503 Week 6 instructions, in plain terms
In this thread you are usually asked to propose where your system ends and defend the choice. Take a side in your opening sentence and name the specific line: what is included, what is excluded and what is treated as a fixed condition. Argue what the boundary makes analyzable, ideally in terms of what your organization can act on. Then spend more space on what it costs, naming at least one excluded cause that would matter if it moved. Acknowledge that boundaries are never neutral without retreating to the view that all choices are equally arbitrary. Sources are optional, since reasoning carries this post. In replies, engage a classmate's line and propose moving it, with a reason.
How the DDHA 8503 Week 6 example is put together
The opening sentence states the boundary and its main cost. A short paragraph lists what lies inside and outside the line. The second paragraph defends the boundary as matching the question of what the group can change within a year, citing Meadows on drawing boundaries for the question asked. The third paragraph, the longest, gives the size of the notification stream, links it to burnout through Tai-Seale and colleagues and says that treating it as fixed is a choice. The fourth uses Sterman to describe the boundary as a decision about what the model explains and what it takes as given. The reply to Renata argues for including inpatient discharge timing. The reply to Felix argues for excluding payer formularies.
DDHA 8503 Week 6 rubric: what earns full marks
Boundary threads are graded on candor. A position in the first sentence is expected. The argument for what the boundary makes analyzable should be specific to the system. The cost paragraph carries the most weight: markers look for at least one excluded cause named concretely, with a sense of its size and what would happen if it moved. Acknowledging non-neutrality while defending a choice shows mature reasoning; claiming neutrality, or claiming all boundaries are arbitrary, does not. Few sources are needed, and stacking citations does not compensate for weak reasoning. Replies are evaluated on whether they propose moving a classmate's line in a direction and give a reason drawn from that classmate's own case.
Common DDHA 8503 Week 6 mistakes, and how to avoid them
Students often pick a boundary and defend only its benefits. Spend more of the post on what it hides. Name the excluded cause precisely and say how big it is, if you can. Do not claim your boundary is objective. Equally, do not conclude that boundaries are arbitrary; a choice can be justified for a purpose. In replies, suggest a direction, inward or outward, and explain what the move would gain and lose. Keep the post compact. If you want a boundary post written about your own system, we are happy to draft one for your discussion.
Get a DDHA 8503 Week 6 example written to your instructions
Send the Week 6 prompt with the rubric and the system already mapped, and a finished post with replies arrives inside 24-48 hours, the first free, with the position stated in the very first line. Boundary arguments use a sketched organization, and meeting records or internal memos an employer keeps are not reconstructed under any request.
More DDHA 8503 papers and DHA samples
- DDHA 8503 Week 1: Fix That Faded Post
- DDHA 8503 Week 2: System Description
- DDHA 8503 Week 3: Causal Loop Analysis
- DDHA 8503 Week 4: Environmental Scan
- DDHA 8503 Week 5: Stakeholder Analysis
- DDHA 8503 Week 7: Scenario Set
- DDHA 8503 Week 8: Intervention Design
- DDHA 8503 Week 9: Consequence Review
- DDHA 8503 Week 10: Alignment Audit
- DDHA 8503 Week 11: Strategic Plan
- DDHA 8303 Week 6: Single-Site Claims Post
- DDHA 8203 Week 6: Tradeoff Discussion Post
- DDHA 8113 Week 6: Followership Discussion Post
- DDHA 8103 Week 6: Candor Versus Exposure Post
DDHA 8503 Week 6 questions, answered
Where can I find a free DDHA 8503 Week 6 sample paper?
The full boundary post and both replies on the primary care messaging system appear on this page free of charge.
Where does the DDHA 8503 Week 6 example draw the boundary?
Around the group's fourteen clinics, nurse triage pool and patient portal, with the record system's design and payer rules held fixed.
What does the boundary hide?
About 19,000 automated notifications a week, shaped by vendor defaults, which may matter more than several causes inside the line.
Does the post claim the boundary is neutral?
No; it calls the boundary a choice suited to the question while rejecting the idea that all choices are equally arbitrary.
How do the replies move classmates' boundaries?
One argues for including inpatient discharge timing; the other argues for excluding payer formulary policies.