MMHA 6600 Week 11 Handoff Tool Adoption Memo Example

Healthcare Informatics and Technology Management Walden University Free custom sample in 24 to 48h

This MMHA 6600 Week 11 adoption memo example measures uptake of an electronic shift handoff tool six months after go-live, using four traces anyone can count: opened at handoff, updated, read by the receiver and used at the bedside. Walden MMHA 6600 closes the MHA informatics course with evaluation, and the memo finds nurses using the tool for most patients and physicians for well under half. Citing Greenhalgh and colleagues on adoption as routine use and Holden and Karsh on perceived usefulness, it explains the gap through physician interviews. Two workarounds are judged by need and risk, following Koppel and colleagues: printed annotated sheets are kept, while a physicians' shared list in the messaging product is replaced by a cross-cover view. Starmer and colleagues frame the goal of consistent use by both professions.

CourseMMHA 6600 Healthcare Informatics and Technology Management
WeekWeek 11
Paper typeAdoption review memo
LengthAbout 890 words, 5 pages
FormatMemo, APA 7 citations
SchoolWalden University
ProgramMaster of Healthcare Administration (MHA)
UpdatedOctober 2026

Free sample paper for MMHA 6600 Week 11

1

Memorandum

To: Chief Nursing Officer and Medical Staff Informatics Committee, Bramble Creek Hospital

From: Informatics Project Lead (MMHA student)

Date: Month Day, Year

Re: Six-month adoption review of the electronic shift handoff tool on medical-surgical units

 

Summary

Six months after go-live, the electronic shift handoff tool is used on most handoffs but not in the way it was designed. Nurses open it and update it for most patients; physicians use it far less. Two workarounds have spread: nurses print the tool and write on the printout, and night physicians keep a separate shared list in the messaging product. I recommend keeping the first workaround and building it into the tool, and replacing the second with a change to the tool that meets the need behind it. Adoption is defined in this memo by traces anyone can count, not by survey impressions.

What this page is doingThe summary gives the finding, the two workarounds and the recommendation, so a reader who stops here still knows what to decide.
2

How Adoption Was Measured

Saying a tool is adopted means little unless adoption is defined in observable terms. I used four traces, each available from the record's logs or from direct observation over two weeks on three units. Every percentage in Table 1 is invented to show the method and should be replaced by the hospital's own log extract.

Defining adoption this way follows the view that a technology is adopted when it becomes part of routine work, which can be observed, rather than when it is installed (Greenhalgh et al., 2017).

Table 1

Adoption Traces at Six Months (Illustrative)

TraceDefinitionNursesPhysicians
Opened at handoffTool opened within 30 minutes of shift change for the patient88%41%
UpdatedAt least one field edited during the shift74%29%
Read by receiverReceiving clinician opened the patient's entry within 30 minutes81%35%
Used at bedsideObserved in use during the verbal handoff22%9%

Nurses open, update and read the tool for most patients; physicians do so for well under half. Almost nobody uses the screen at the bedside.

What this page is doingDefining adoption by traces with explicit definitions makes the numbers checkable and avoids arguing about impressions.
3

Why Physicians Use It Less

Interviews with eight hospitalists pointed to two reasons. The tool's fields were designed around nursing handoff, with sections for lines, drains and mobility, and physicians found the physician section too short for overnight contingency plans. Night physicians also cover patients across units, and the tool is organized by unit, so a cross-cover physician must open three unit lists. Perceived usefulness and fit with work are among the strongest predictors of whether clinicians use a technology (Holden & Karsh, 2010). For physicians, the tool scores poorly on both.

What this page is doingThe explanation comes from users' own accounts and is linked to a well-studied predictor of technology use.
4

The Two Workarounds

Workarounds are often treated as noncompliance. Some are better understood as users adapting a tool to work it did not anticipate, while others create risks of their own (Koppel et al., 2008). Each workaround here was judged on two questions: does it meet a real need, and does it create a safety or privacy risk?

The printed sheet is useful reinvention. Nurses use the tool as intended at handoff and then carry a paper copy that fits how they move through a shift; the information starts in the record, and the risk is small. The physicians' shared list is different. It meets a need the tool does not, a cross-unit view with room for contingency plans, but it holds clinical information outside the record where nobody else can see or audit it.

Table 2

Workarounds Judged

WorkaroundNeed it meetsRisk it createsJudgment
Nurses print the tool and annotate the printout during the shiftQuick notes while moving between rooms; the screen is not at the bedsideLow: printout stays on unit and is shredded at end of shift under existing policyKeep and support
Night physicians keep a shared list in the messaging productOne list across units with free-text contingency plansHigh: list sits outside the record, is not reconciled with orders and persists after dischargeReplace

The first workaround is a sensible adaptation; the second solves a real problem in an unsafe place.

What this page is doingJudging each workaround by need and risk avoids both blanket bans and blanket acceptance.
5

Recommendations

First, keep the printed sheet and improve it: add a print layout designed for annotation, with space beside each patient, and confirm the shredding procedure on every unit. Second, replace the physicians' shared list by changing the tool: add a cross-cover view that lists all of a physician's patients regardless of unit and expand the physician section to include if-then contingency plans. Once that view exists, ask the messaging product administrator to discourage shared patient lists through policy and product settings. Third, keep measuring the same four traces at nine and twelve months, adding physician use of the new cross-cover view. Structured handoff programs have been associated with fewer medical errors when they are used consistently (Starmer et al., 2014), so the goal is consistent use by both professions, not only nurses.

What this page is doingEach recommendation answers a finding, and the final one commits to the same measures so progress can be compared.
6

Risks of the Recommended Changes

A cross-cover view could become a second place to keep the same plan if physicians copy text between sections, so the build team should show contingency plans in one field that appears in both views. Expanding the physician section adds length, and a longer form may lower nurse reading of it; the nine-month traces will show whether that happens. Finally, discouraging shared lists in the messaging product will meet resistance until the new view is live, so the policy change should follow the build rather than precede it.

Decisions Requested

I ask the committee to approve the cross-cover view and the expanded physician section for the next build cycle, and the Chief Nursing Officer to approve the annotation print layout.

References

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), e367. https://doi.org/10.2196/jmir.8775

Holden, R. J., & Karsh, B.-T. (2010). The technology acceptance model: Its past and its future in health care. Journal of Biomedical Informatics, 43(1), 159-172. https://doi.org/10.1016/j.jbi.2009.07.002

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

Starmer, A. J., Spector, N. D., Srivastava, R., West, D. C., Rosenbluth, G., Allen, A. D., Noble, E. L., Tse, L. L., Dalal, A. K., Keohane, C. A., Lipsitz, S. R., Rothschild, J. M., Wien, M. F., Yoon, C. S., Zigmont, K. R., Wilson, K. M., O'Toole, J. K., Solan, L. G., Aylor, M., . . . Landrigan, C. P. (2014). Changes in medical errors after implementation of a handoff program. New England Journal of Medicine, 371(19), 1803-1812. https://doi.org/10.1056/NEJMsa1405556

MMHA 6600 Week 11 instructions, in plain terms

Adoption reviews ask you to evaluate whether a new system is being used and how. Define adoption in observable terms, such as log events or watched behavior, rather than survey impressions. Report results by user group, since uptake often differs. Explain gaps using users' own accounts and a model of technology acceptance. Look for workarounds and judge each on whether it meets a real need and whether it creates risk. Recommend keeping useful adaptations and replacing risky ones by changing the system. Commit to repeating the same measures so progress can be compared. Write as a memo with a summary, short sections and specific decisions requested.

How the MMHA 6600 Week 11 example is put together

The memo's summary gives the uptake finding, the two workarounds and the recommendation. Table 1 defines four traces and reports them for nurses and physicians. A paragraph cites Greenhalgh and colleagues to justify defining adoption by routine use. A section explains low physician use through interviews and Holden and Karsh. Table 2 judges two workarounds on need, risk and verdict, citing Koppel and colleagues. Recommendations improve the print layout, add a cross-cover view and repeat the traces, with Starmer and colleagues on consistent handoff use. A risks section addresses duplicate plans and form length. The memo closes with two decisions. Throughout, numbers are labeled illustrative and the method is what the memo asks leaders to adopt.

Reading the MMHA 6600 Week 11 rubric

Adoption memos are assessed on measurement and judgment. Defining adoption with observable traces earns the measurement credit, and reporting them by user group earns more. Explaining differences with evidence from users, linked to an acceptance model, shows analysis. The judgment share goes to evaluating workarounds fairly, on need and risk, rather than banning them all. Recommendations that change the system to meet the need behind a risky workaround show design thinking. Committing to repeated measures demonstrates follow-through. Memo structure, brevity and a clear request matter. Citations should support the definitions and judgments, and every one must appear in the reference list. A short risks section on the recommended changes adds credit, because new views can create new problems.

MMHA 6600 Week 11 help: mistakes that cost marks

Adoption reviews often rely on a satisfaction survey. Count behavior instead, using logs and short observations. Report each user group separately. Talk to the group using the tool least; their reasons usually point to a design gap. Treat workarounds as information: ask what need each one meets and what risk it creates. Keep the safe ones and fix the system for the risky ones. Promise to repeat the same measures. We can help you define adoption traces for a system at your organization and write a review memo that turns workarounds into design requests leaders can approve. Share the trace definitions with the build team early, so the logs capture what you need.

Get a MMHA 6600 Week 11 example written to your instructions

Send the final-week prompt and your rubric, plus the technology your organization installed if the assignment is built around your own setting; an adoption memo returns in 24-48h with the first at no cost. The handoff tool and the hospital around it are composites, and any usage data from your own system stays with you.

More MMHA 6600 papers and MHA samples

MMHA 6600 Week 11 questions, answered

Where can I find a free MMHA 6600 Week 11 sample paper?

The handoff tool adoption memo is published here, with its trace table and workaround table.

How does the MMHA 6600 Week 11 memo define adoption?

By four countable traces: opened at handoff, updated, read by the receiving clinician and used at the bedside.

Why do physicians use the handoff tool less?

Its physician section is too short for contingency plans, and cross-cover physicians must open several unit lists.

Which workaround is kept?

Nurses' printed and annotated handoff sheets, which meet a real need with low risk.

Which workaround is replaced, and how?

The physicians' shared list in the messaging product, replaced by a cross-cover view and a larger physician section in the tool.