| Course | DDHA 8601 Technology and Innovation in Healthcare |
|---|---|
| Week | Week 1 |
| Paper type | Doctoral discussion post with two replies |
| Length | About 640 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 8601 Week 1
Week 1 Discussion: Why Staff Work Around Technology
Passed Every Acceptance Test, Routed Around by Week Three: Why a Teaching Clinic's Schedulers Went Back to a Paper List
The new scheduling system at our teaching clinic was never rejected; it was routed around, and the reasons sit in the work rather than in the software. The clinic is a composite internal medicine practice where 36 residents see patients under faculty supervision. The system passed every acceptance test the vendor and our information technology team ran. Three weeks after go-live, the front desk was keeping a handwritten list on a clipboard, and by the second month that list held most of the clinic's urgent follow-up bookings.
The first piece of evidence is what schedulers did with patients discharged from the hospital who needed a visit within seven days. The system releases resident appointment templates four weeks ahead, built from the residents' rotation calendar. Rotations change monthly, and the calendar is often finalized late, so the slots a discharged patient needed frequently did not yet exist in the system. Schedulers wrote these patients on the clipboard and booked them by hand once a slot appeared, sometimes calling the patient twice. Koppel et al. (2008), studying workarounds to bar-code medication systems, found that workarounds most often arose where the technology's assumptions did not match the actual sequence of work, and this is a clean example: the system assumed the calendar would exist before demand did.
The second is what the charge nurse did about supervision. First-year residents may see patients only when a supervising physician is in the clinic. The system had no field for preceptor presence, so it would happily book a first-year resident into a slot with no supervisor. The charge nurse began marking the paper schedule each morning with which slots were safe, and schedulers checked the paper before trusting the screen. Debono et al. (2013), in a review of nurses' workarounds, describe them as a response to blocks in the flow of work that also protect patients, which is how staff here described this one in their own actions: they did not complain about the system, they simply stopped relying on it for this decision. Greenhalgh et al. (2017) warn that technologies often fail not at adoption but afterward, through quiet abandonment when they do not fit the complexity of the work.
The paper list will stop being useful when the system can hold slots tied to a named preceptor's presence and release them within three days rather than four weeks.
Reply to Tamsin
Tamsin, you described your hospital's new bed-board as a failure because nurses still phone bed management, and you concluded that training was the problem. Your own account suggests otherwise. You wrote that the bed-board shows a bed as clean when environmental services marks it, but nurses phone to ask whether the room has also been restocked, which the board does not track. That is the same pattern as our clipboard: the work contains a step the system does not represent. Koppel et al. (2008) found that more training rarely removes a workaround whose cause is a mismatch between the technology and the task. Would adding a restocking status end the calls?
Reply to Obinna
Obinna, I agree that the electronic sign-out tool on your unit was worked around, but I would question your view that the workaround is harmless. Residents on your unit keep a parallel paper sign-out because the tool truncates long problem lists. That protects patients during the shift, but it also means the electronic record of handoffs is incomplete, and anyone auditing a missed task later will find a record that does not reflect what was said. Debono et al. (2013) note that workarounds can protect patients in the moment while creating risks elsewhere. The question for your leaders may be whether to fix the truncation or to accept paper as the record.
References
Debono, D. S., Greenfield, D., Travaglia, J. F., Long, J. C., Black, D., Johnson, J., & Braithwaite, J. (2013). Nurses' workarounds in acute healthcare settings: A scoping review. BMC Health Services Research, 13, Article 175. https://doi.org/10.1186/1472-6963-13-175
Greenhalgh, T., Wherton, J., Papoutsi, C., Lynch, J., Hughes, G., A'Court, C., Hinder, S., Fahy, N., Procter, R., & Shaw, S. (2017). Beyond adoption: A new framework for theorizing and evaluating nonadoption, abandonment, and challenges to the scale-up, spread, and sustainability of health and care technologies. Journal of Medical Internet Research, 19(11), Article e367. https://doi.org/10.2196/jmir.8775
Koppel, R., Wetterneck, T., Telles, J. L., & Karsh, B.-T. (2008). Workarounds to barcode medication administration systems: Their occurrences, causes, and threats to patient safety. Journal of the American Medical Informatics Association, 15(4), 408-423. https://doi.org/10.1197/jamia.M2616
The Walden DDHA 8601 Week 1 instructions
The opening thread of this course wants an explanation of why people work around a technology. State your position in the first line instead of summarizing the reading. Support it with evidence of what staff did, not what they said they thought, ideally from a setting you know. Put a dated citation under each piece of evidence so readers can see how current the support is. Explain the mismatch between the system's assumptions and the actual sequence of work. Finish with the condition that would make the workaround unnecessary, which turns the post into something testable. Each reply should name the classmate and offer evidence, preferably drawn from that classmate's own example, for a different reading.
Inside the DDHA 8601 Week 1 example
The first paragraph states the position and describes the clinic, the residents and the clipboard that appeared three weeks after go-live. The second paragraph describes how schedulers handled patients discharged from the hospital who needed a visit within a week, and ties it to Koppel and colleagues' finding about mismatched assumptions. The third paragraph describes how the charge nurse marked supervised slots each morning, drawing on Debono and colleagues' view of workarounds as protective, and adds Greenhalgh and colleagues' warning about quiet abandonment. A one-sentence closing names the condition for retiring the paper list. One reply shows a classmate that missing restocking status, not training, explains phone calls about beds. The other adds an audit risk to a parallel paper sign-out.
DDHA 8601 Week 1 rubric: what earns full marks
In this thread, graders look for a position and for evidence of behavior. A post that reports on the reading or describes feelings about technology earns less than one that shows what staff actually did and why. Dated citations matter in an informatics course, where evidence ages quickly, and placing them under each claim makes the reasoning easy to check. Credit rises when the explanation identifies a specific mismatch between system design and work sequence. A testable closing condition shows analytic maturity. Replies are graded on whether they engage a classmate's argument with new evidence rather than agreement, and on courtesy and directness. Participation deadlines and correct APA formatting apply throughout.
DDHA 8601 Week 1 help from the desk
The weak version of this post says staff resisted change or needed more training. Look harder at what the system assumed about the work. Observe or recall what people did, such as a list, a sticky note or a phone call, and trace it to a step the system does not represent. Keep the post short; two pieces of evidence are enough. Date your sources in the text so readers see their age. End with a condition someone could check. In replies, find the evidence in your classmate's own example that points elsewhere. We can also draft a version of this post around a workaround you have watched in your own organization.
Get a DDHA 8601 Week 1 example written to your instructions
The desk writes this thread again from the prompt and rubric your own section posted, not from the version shown here. First custom sample costs nothing, returns inside 24-48 hours, and arrives formatted for submission. Its clinic stays a composite one, because your employer's scheduling records are not ours to reproduce.
More DDHA 8601 papers and DHA samples
- DDHA 8601 Week 2: Workflow Assessment
- DDHA 8601 Week 3: Technology Evaluation
- DDHA 8601 Week 4: Adoption Analysis
- DDHA 8601 Week 5: Cost of Ownership Analysis
- DDHA 8601 Week 6: Interoperability Discussion Post
- DDHA 8601 Week 7: Interoperability Brief
- DDHA 8601 Week 8: Implementation Plan
- DDHA 8601 Week 9: Downtime Plan
- DDHA 8601 Week 10: Benefits Measurement
- DDHA 8601 Week 11: Business Case
- DDHA 8503 Week 1: Fix That Faded Post
- DDHA 8303 Week 1: Researchable Questions Post
- DDHA 8203 Week 1: Clinic Constraint Post
- DDHA 8113 Week 1: Authority Versus Influence Post
DDHA 8601 Week 1 questions, answered
Where can I find a free DDHA 8601 Week 1 sample paper?
The workaround post on the teaching clinic's scheduling system, with both replies and references, is free on this page.
What does the DDHA 8601 Week 1 example argue?
That the scheduling system was routed around rather than rejected, because it assumed things about the work that were not true.
What evidence does the post use?
A clipboard list for discharged patients needing follow-up and a daily paper marking of slots with a supervising physician present.
When would the paper list stop being useful?
When the system can hold slots tied to a named supervisor's presence and release them within three days instead of four weeks.
Why do the replies reject training as the explanation?
Workarounds caused by a mismatch between system and task rarely disappear with more training, as the cited workaround research found.