17.4 Organizational Change Management and Stakeholder Relationships

17.4 Organizational Change Management and Stakeholder Relationships

Quick Answer: Task A.20 is organizational change management—stakeholder analysis, communication, training, and resistance—applied to people and work. It is not Chapter 13 technical change control (RFC, CAB, back-out). Apply ADKAR, Kotter, and Lewin as HIT lenses. Task A.18 is ethical relationships with clinicians, administrators, vendors, and community partners.

Two CPHIMS stems will use the word change. One is a hallway edit to a dose-range table. That is Domain 3 task C.2: request, assess, authorize, build in non-production, test, implement, prove a rollback. The other is a unit that will not stop using the paper downtime form three months after go-live. That is A.20. Mix them and you will pick the town hall when the exam wanted the change-advisory board, or the CAB when the exam wanted a coalition and reinforcement.

Chapter 16 already covered ethical principles (A.10). A.18 is how those principles live in ongoing relationships. Chapter 18 will cover roles, education programs, portfolios, and vendor contracts. This section is the human system that sits between strategy and the live build.

CPHIMS practicePractice questions with detailed explanations

A.20 is people-change; C.2 is bit-change

A perfectly authorized patch can still fail adoption. A brilliant town hall does not authorize a production medication-library edit. Write that sentence until it is automatic.

The handbook’s A.20 examples are the work sequence, not a brand name: stakeholder analysis, communication planning, training, and resistance management. Models help you remember the sequence. HIMSS does not publish a CPHIMS-official ADKAR score, Kotter checklist, or Lewin template. If the stem names a model, apply it. If it does not, still do the work.

ADKAR applied to HIT

ADKAR diagnoses one person or role along the adoption path.

If ambulatory physicians skip a new portal-message standard, do not buy another classroom hour first. Test Awareness (do they know the access aim and the harm of lost messages?) and Desire (does the coverage compact give time back, or only add clicks?). Knowledge without Desire is a full classroom and an empty practice environment.

Kotter applied to HIT

Kotter sequences the organization.

1. Urgency that is real: harm, access, survey, or information-blocking exposure—not “the vendor contract expires Friday” as fake urgency to skip a CAB.
2. Guiding coalition that can actually move work: CMIO, CNO, pharmacy, HIM, revenue, and a unit director—not only the CIO and a vendor-friendly medical director.
3. Vision as a future-state workflow sentence, not a logo.
4. Communicate the same sentence on many channels. A.12 artifacts live here.
5. Empower / remove obstacles. Delete the paper form, fix the identity bug, give superusers protected time. A vision with the old path still easier is decoration.
6. Short-term wins that operations recognizes: one unit’s BCMA scan rate, one clinic’s completed-message time—not “we completed training hours.”
7. Sustain. Do not declare victory at go-live. Hypercare, defect burn-down, and content governance continue.
8. Anchor. Job descriptions, privileging, policies, and onboarding so the new work survives the next manager.

A Kotter coalition that is only IT is not a coalition. A Kotter “win” that is only an IT scorecard is not a win (Chapter 15).

Lewin applied to HIT

Lewin’s three movements keep you from skipping the ends.

• Unfreeze. Make the current state impossible to romanticize: show the duplicate MRN, the missed allergy, the 38-day wait. Stop the unofficial workaround that makes the old world livable. A.7 constraints belong in this conversation so people know what will not be magically funded.
• Change. Install the new process and the new build together. This is where C.2 technical change and A.20 people-change meet but do not merge. The RFC still happens. The communication and Desire work still happen.
• Refreeze. Policy, downtime procedure, order-set governance, and removal of the old form. If the old path remains, you did not refreeze; you ran a pilot forever.

Big-bang go-lives often skip unfreeze (no one let go of the workaround) and skip refreeze (no one owned the standard). Phased go-lives fail the same way if each wave re-opens the old form “just for this unit.”

Resistance is data, not a personality diagnosis

A.20 resistance management starts with Chapter 15 environment assessment. Independent surgeons protecting implant choice are not “change-averse.” Night shift that missed training is not resistant; they are untrained. A union that was not given notice is a legal constraint. A clinic that lost two hours to the last go-live is remembering. Name the reason. Then pick the lever: coalition, time back, process redesign, or escalation. Do not pick “more email.”

Stakeholder analysis for A.20 is more than an org chart: influence, impact, current ADKAR stage, and what a miss costs that role. Communication planning assigns who says what, through which channel, how often, and how you will know it landed. Training design is role-based and environment-real—the C.3 methods—placed after Awareness and Desire, not instead of them.

A.18: ethical relationships, not networking theater

Establish and maintain relationships with clinicians, administrators, vendors, and community partners. Ethical means purpose-limited and conflict-disclosed.

A vendor can be a respected partner and still sit outside facilitation of your scorecard, outside your board narrative, and outside your change-advisory vote. Clinical relationships are not a sales channel. Partner relationships do not waive HIPAA, 42 CFR Part 2 where it applies, or the organization’s conflict-of-interest policy. Recertification still expects ethics and COI hours; the exam expects you to recognize the relationship failure before it becomes a COI case.

In an FQHC, community partners may be the outreach clinic and the county. In an academic center, the partner may be a research institute that wants identifiable data “just for feasibility.” Same A.18 test: purpose, minimum necessary, written terms, no informal PHI.

Scenarios and exam traps

Scenario. Ambulatory physicians skip a new portal-message standard. Training attendance was high. Check Awareness and Desire before you repurchase classroom time. If they do not know the lost-message harm, or if coverage time was never given back, Knowledge was never the deficit.

Scenario. A nurse manager wants a medication-library dose range fixed “today” and offers to announce it at the afternoon huddle. The huddle is A.20 communication. The library edit still needs an RFC, a non-production path, pharmacy authorization, and a back-out—Chapter 13. Do not let urgency theater collapse the two systems.

Scenario. The guiding coalition for a BCMA program is the CIO, two analysts, and a vendor executive. Rebuild the coalition around nursing, pharmacy, and a unit that actually passes meds. Kotter without operators is a steering committee photo.

Scenario. A vendor offers dinner and a ghostwritten requirements packet during selection, and asks to present the board slides. A.18 refuses the gift, writes requirements with operations, and keeps the vendor out of the score and the trustee narrative (section 17.2). Friendship is not a BAA.

Scenario. An HIE partner wants “a quick extract for a grant” without a data-use term. Purpose limitation and a written agreement are the relationship. Informal PHI is not partnership.

Watch these traps:

1. Picking a town hall when the stem is a production edit (C.2).
2. Picking a CAB when the stem is resistance, Desire, or reinforcement (A.20).
3. Treating training hours as completed change.
4. Leaving the old form in the drawer and calling Lewin done.
5. A coalition of IT plus the vendor.
6. Gifts, ghostwritten requirements, or surprise secondary use dressed as relationship-building.

/practice/cphimsPractice questions with detailed explanations