Study guide
17.4 Organizational Change Management and Stakeholder Relationships
Certified Professional in Healthcare Information and Management Systems CPHIMS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Eligibility Pathways and Qualifying Experience 1.3 Scoring, Retakes, and Recertification 1.4 Domain-Weighted Study Strategy
2 Healthcare Organizations and Relationships
2.1 Hospitals, Clinics, Ambulatory, and Community Organizations 2.2 Payers, Regulators, Research, and Academic Organizations 2.3 Interrelationships, HIE, and Continuity of Care 2.4 HIT Professional Roles and Organizational Structures
3 Policy, Accreditation, and Care Trends
3.1 Privacy and Security Law: HIPAA and HITECH 3.2 Interoperability Policy and Information Blocking 3.3 Accreditation, Patient Rights, and Environments of Care 3.4 Telehealth, Portals, Wearables, and Population Health
4 Healthcare Applications
4.1 Clinical Applications 4.2 Administrative and Financial Applications 4.3 Consumer-Facing Applications 4.4 Business Intelligence Applications
5 Technology Infrastructure
5.1 Networks and Communications 5.2 Data Integration Architectures 5.3 Infrastructure Privacy and Security 5.4 Cloud, Devices, and Identity Infrastructure
6 Clinical Language, Terminologies, and Metrics
6.1 Clinical Vocabulary 6.2 Healthcare IT Vocabulary 6.3 Clinical Terminologies: SNOMED CT, LOINC, RxNorm, and ICD 6.4 Clinical Metrics and Operational Measures
7 Clinical Effectiveness and Workflows
7.1 System Functionality for Clinical Effectiveness 7.2 Workflows, Order Sets, and Pathways 7.3 Safety, Quality, and Clinical Informatics Design
8 Informatics Analytics
8.1 Analytics Tools, Reports, Tables, and Graphs 8.2 Interpreting Clinical and Operational Outcomes 8.3 Predictive Models in Care and Operations
9 Clinical Content and Decision Support
9.1 Clinical Content Lifecycle 9.2 Clinical Decision Support Types and Design 9.3 CDS Governance, Alert Management, and Knowledge Maintenance
10 Analysis, SDLC, and Improvement Methods
10.1 Systems Development Life Cycle 10.2 Project Management: Needs, Gap, and Requirements 10.3 Process Improvement: DMAIC and PDCA 10.4 Process Maps, Flow Diagrams, and Gap Analysis
11 Analysis: Solutions and the Business Case
11.1 Disparate Data Sets and Alternate Solutions 11.2 Strategic Alignment and Cost-Benefit Analysis 11.3 Proposals, RFPs, RFIs, SLAs, SOWs, and NDAs
12 Systems Design
12.1 Interoperability of Software, Hardware, Networks, and Devices 12.2 Design Compliance and Incorporating Industry Trends 12.3 Business Continuity and Disaster Recovery Design 12.4 Emerging Technologies and Data Governance
13 Selection, Implementation, Support, and Maintenance
13.1 Solution Selection Activities 13.2 Technical Change Management, Training, and Support 13.3 Implementation: Scope, Schedule, Budget, and Quality 13.4 Maintenance, Operations, and Problem-Trend Analysis
14 Testing, Evaluation, Privacy, and Security
14.1 Testing Methodology and Internal Controls 14.2 Validation and Benefits Realization 14.3 Privacy and Security Policies, Access, and Safeguards 14.4 Vulnerabilities, Roles, Data Controls, and Ongoing Validation
15 Strategy and IT Planning
15.1 Contributing to Organizational Strategic Planning 15.2 Assessing the Organizational Environment 15.3 Forecasting Technical and Information Needs 15.4 IT Strategic Plans and Departmental Objectives
16 Performance, Policy, Ethics, and Analytics
16.1 Evaluating Performance Against SLAs and Indicators 16.2 User Satisfaction and Service Effectiveness 16.3 Policies, Legal Compliance, and Ethical Principles 16.4 Comparative Analytics and Presenting Recommendations
17 Communication, Stakeholders, and Change
17.1 Promoting Stakeholder Understanding of IT Opportunities and Constraints 17.2 Business Communications and Consultative Technology Services 17.3 Facilitating Groups, Consensus, and Conflict Resolution 17.4 Organizational Change Management and Stakeholder Relationships
18 People, Projects, Vendors, and Finance
18.1 HIT Roles, Job Descriptions, and Staff Competency 18.2 Educational Strategies and Maintaining IT Competencies 18.3 Managing Projects and Portfolios 18.4 Vendor Contracts, Budgets, and Risk Management
17.4 Organizational Change Management and Stakeholder Relationships
Key Takeaways Explain This Topic AI
Domain 4 task A.20 is employ organizational change management—stakeholder analysis, communication planning, training design, and resistance management—not the RFC/CAB path in Chapter 13 task C.2.
Apply ADKAR, Kotter, and Lewin to HIT as lenses: ADKAR diagnoses the person, Kotter sequences the coalition, Lewin names unfreeze-change-refreeze. HIMSS does not require one official model.
Training is ADKAR Knowledge and Ability. If Awareness and Desire are missing, more classroom will not create adoption.
Task A.18 is establish and maintain ethical relationships with clinicians, administrators, vendors, and community partners—purpose-limited, conflict-disclosed, and never a gift- or ghostwriting-based shortcut.
A town hall does not authorize a production medication-library edit. A CAB does not create Desire. Keep the two “change” words on their own stems.
Last updated: August 2026
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.
Practice the distinction at CPHIMS practice . Adoption and resistance also appear on CPHQ as improvement work. Legal and partner data-sharing constraints appear on RHIA . CPHIMS wants the correct change system and a clean relationship.
A.20 is people-change; C.2 is bit-change
Cue in the stem Home First move
Production, RFC, CAB, freeze, back-out, environment, emergency change Chapter 13 C.2 technical change Stop the hallway edit; open an RFC
Sponsor, coalition, resistance, communication plan, reinforcement, culture A.20 organizational change Diagnose who must adopt and why they will not
Superuser, CBT, classroom, elbow support Chapter 13 C.3 and A.20 Knowledge/Ability Match method to role; do not skip Awareness
Gift, ghostwritten requirements, BAA-as-favor, physician access sold to a vendor A.18 relationships Disclose, separate, or refuse
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.
Element HIT meaning Typical miss
Awareness Why this workflow is changing, with local harm or access data A go-live date announced as if it were a reason
Desire A reason to participate that survives inbox math and RVU reality “Because the CIO said so”; ignored medical-staff compact
- Knowledge Role-based training in a realistic environment One lecture for night shift, ED, and HIM
- Ability Can perform at the elbow, in gloves, with dirty data Tip sheets in production as the only support
Reinforcement Old path dies; leaders round; measures continue after hypercare Confetti at go-live; paper form still in the drawer
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 .
Urgency that is real: harm, access, survey, or information-blocking exposure—not “the vendor contract expires Friday” as fake urgency to skip a CAB.
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.
Vision as a future-state workflow sentence , not a logo.
Communicate the same sentence on many channels. A.12 artifacts live here.
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.
Short-term wins that operations recognizes: one unit’s BCMA scan rate, one clinic’s completed-message time—not “we completed training hours.”
Sustain. Do not declare victory at go-live. Hypercare, defect burn-down, and content governance continue.
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.
Relationship Ethical practice Exam fail
Clinicians / medical staff Shared design, honest click-count, no fake “clinical mandate” for a vendor goal Trading physician access for a pilot; hiding documentation burden
Nursing / allied Protected superuser time; night shift in design Superusers pulled back to staffing with no backfill
Administrators / board Aim-first advice; residual honesty A sidecar digital story that conceals displaced work
Vendors BAA and contract, not friendship; they do not write the scored requirements they will bid; no gifts that buy access Ghostwritten RFP; vendor-run CAB; sponsored dinner during selection
Community / HIE / academic partners Purpose limitation, minimum necessary, written data-use Surprise secondary use; “we’re all in this together” as a substitute for a data-use agreement
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.
Loading diagram... Keep A.20 people-change beside C.2 bit-change; A.18 keeps the relationships clean
Study heuristic: A.20 / A.18 misses (relative emphasis, not official weights)
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:
Picking a town hall when the stem is a production edit (C.2).
Picking a CAB when the stem is resistance, Desire, or reinforcement (A.20).
Treating training hours as completed change.
Leaving the old form in the drawer and calling Lewin done.
A coalition of IT plus the vendor.
Gifts, ghostwritten requirements, or surprise secondary use dressed as relationship-building.
If you can split people-change from bit-change, place the person on ADKAR, and keep vendor and partner relationships purpose-limited, you are in A.20/A.18 territory. Drill those stems at /practice/cphims .