Change Management in Healthcare: A Practical Playbook

Last updated: July 13, 2026

Key Takeaways for Cardiology Change Leaders

• Fragmented multi-OEM CIED and RPM portals create workflow inefficiencies, alert fatigue, and CPT billing gaps that structured change management can resolve.
• Applying Kotter’s 8-step and Lewin’s 3-stage models gives cardiology practices a clear, sequential path for vendor-neutral platform adoption.
• Real-world examples show measurable gains, including up to 80% faster critical-alert response, less manual data entry, and higher first-pass CPT claim acceptance when teams follow these frameworks.
• Leadership tactics such as early clinical champions, patient-outcome messaging, and visible executive sponsorship are critical to overcoming resistance and sustaining adoption.
• Cardiology groups ready to streamline their transition can contact Rhythm360 to design a tailored change-management playbook.

Kotter's 8-Step Change Model for RPM and CIED Rollouts

Dr. John Kotter of Harvard Business School introduced his 8-step change model in 1995 based on observations of hundreds of transformation efforts. In healthcare, hospitals have successfully applied Kotter's model to major transformations including electronic medical record rollouts. The steps below map directly to a vendor-neutral RPM/CIED platform implementation.

1. Create urgency. Quantify the current cost of fragmentation. Clinical staff spend 30–40% of their time on data retrieval rather than patient care when logging into separate systems. Present missed critical-alert data, denied claims volumes, and staff burnout metrics to clinical and administrative leadership.
2. Build a guiding coalition. Assemble a cross-functional team that includes electrophysiologists, device technicians (CCTs), practice administrators, billing staff, and IT leads. Designating change champions, respected individuals who drive momentum and encourage peer buy-in across departments, is vital at this stage.
3. Form a strategic vision. Define the unified-platform end state in concrete terms. Describe a single dashboard displaying all CIED and RPM data, automated CPT documentation, and bi-directional EHR integration. Connect this vision to patient safety outcomes as well as efficiency gains.
4. Communicate the vision. Effective communication starts well before go-live, uses multiple channels, and repeats messages 5–7 times while acknowledging uncertainty honestly. Use town halls, department huddles, and written FAQs that all carry the same core message.
5. Enable action by removing barriers. Identify structural obstacles such as OEM portal access credentials, legacy data export formats, EHR integration timelines, and staff scheduling constraints during training. Assign a named owner and a resolution deadline for each barrier.
6. Generate short-term wins. Pilot the unified platform with one device cohort or one OEM's patient population first. Publicize early results, such as faster transmission review times, fewer login steps, and first clean CPT claims, to build momentum across the broader team.
7. Sustain acceleration. Use pilot-phase data to expand enrollment to additional OEM populations and add RPM service lines for heart failure and hypertension. Kotter's research identifies the consolidating-gains phase as typically requiring 24–36 months in complex professional organizations.
8. Institute the change. Anchor the unified platform in onboarding protocols, performance metrics, and quality review cycles. Remove legacy portal access from standard workflows to prevent reversion. Tie platform utilization to accountability structures at the department level. While Kotter's model outlines the operational steps for change, Lewin's complementary framework focuses on the psychological pacing that keeps those changes in place.

Lewin's 3-Stage Model for Cardiac Monitoring Workflow Stability

Kurt Lewin's 3-stage model remains one of the most widely used change frameworks in healthcare due to its simplicity and psychological grounding. Lewin never developed the three-step change model; it emerged after his death and is sometimes incorrectly traced to his 1947 article 'Frontiers in Group Dynamics.' Applied to a multi-OEM data-silo transition, the three stages operate as follows.

1. Unfreeze. Make the pain of the current state visible and undeniable. Present rework costs from manual data transcription, denied claims rates tied to incomplete CPT documentation, and alert-fatigue incident logs. Andrew Beaser, MD, Associate Professor of Medicine at the University of Chicago Medicine, described pre-implementation workflows as "a major challenge and incredibly difficult." Share peer-level clinical testimony alongside operational data to reduce emotional resistance. Conduct a force-field analysis that lists driving forces such as patient safety risk, revenue leakage, and staff burnout, along with restraining forces such as fear of workflow disruption, training time, and EHR integration uncertainty.
2. Change. Introduce the unified platform through a phased rollout. Define future-state workflows, role responsibilities, and technology enablers before training begins. Effective change-stage tactics include pilot clinics, role-based training, daily huddles, on-site coaches, and a weekly escalation process to triage issues while publicizing quick wins such as fewer billing denials. For CIED monitoring, train device technicians on the unified dashboard first, then expand to clinical reviewers and billing staff.
3. Refreeze. Stabilize the new workflows by embedding them in policy and performance systems. Organizations applying Lewin’s model to EHR rollouts have achieved high adoption by integrating compliance into performance systems and eliminating outdated workflows. For RPM/CIED transitions, update standard operating procedures, revise dashboard KPIs to reflect unified-platform metrics, and remove OEM portal shortcuts from clinical workstations.

Case Example: Multi-OEM Data-Silo Transition in an EP Practice

A mid-sized electrophysiology practice managing patients with devices from four OEMs illustrates how these frameworks work in daily operations. Before consolidation, device technicians logged into four separate portals each day, manually reconciling transmission data and transcribing findings into the EHR. Critical alerts from weekend transmissions often waited until Monday morning review.

The practice applied Kotter's urgency step by auditing six months of transmission logs and identifying a pattern of delayed responses to atrial fibrillation alerts. Leaders paired this data with CPT claim denial rates for 93298 and 93299 to build the business case for a unified platform. A guiding coalition of two EPs, the practice administrator, the lead CCT, and the billing manager formed within two weeks.

During the Lewin Change stage, the practice piloted the unified platform with one OEM's patient cohort for 30 days. Teams held role-based training sessions for CCTs, clinical reviewers, and billing staff, each anchored to actual daily workflows rather than generic software navigation. The most common reason healthcare software implementations fail is that vendor training focuses on software features rather than how the tool integrates into specific clinical and administrative workflows.

Post-implementation, the practice documented faster critical-alert response, fewer manual data entry hours per week, and improved first-pass claim acceptance rates for remote monitoring CPT codes. Gaurav A. Upadhyay, MD, FACC, FHRS, Professor of Medicine and Director of the Pacing & Defibrillation Device Clinic at the University of Chicago Medicine, observed: "We have improved billing and accountability for our patients after the integration."

Leadership Strategies for Cardiology Change Management

Physician buy-in is the single highest-leverage variable in cardiology platform transitions. A March 2025 Sermo survey of over 1,000 physicians found that only 45% believe healthcare leaders are adequately prepared to manage rapid changes in healthcare, and the top barriers cited were lack of resources or support (31%) and resistance from staff or colleagues (24%).

Effective leadership tactics for RPM/CIED platform adoption include these four focused actions.

• Designate clinical champions early. Cultivating respected peers within each department who are enrolled early, given advanced platform access, and positioned as internal advocates is endorsed by the American Medical Informatics Association to reduce peer-to-peer resistance.
• Frame change around patient outcomes. Resistance to AI-enabled tools often arises when they make a provider's job more difficult or add screen time that reduces patient interaction, according to Andrew Beam, PhD, of Harvard T.H. Chan School of Public Health. Lead messaging with clinical benefit, such as earlier arrhythmia detection and fewer missed events, before discussing operational efficiency.
• Create psychological safety for feedback. Involving employees from the planning stage through implementation increases acceptance and commitment to change, per a 2026 PLOS One study of hospital managers. Use structured feedback loops at 30, 60, and 90 days post-go-live to surface friction points before they become entrenched workarounds.
• Maintain visible executive sponsorship. An executive sponsor who visibly champions the initiative, removes obstacles, and holds the organization accountable is a consistent differentiator in successful healthcare technology implementations.

Readiness and Implementation Planning for RPM/CIED Rollouts

Before go-live, practices benefit from a structured readiness assessment across four domains.

• EHR integration timeline. Confirm bi-directional integration specifications with your EHR vendor (Epic, Cerner, Athenahealth, eClinicalWorks, or others via HL7) and establish a realistic cutover date. When planning your timeline, note that Rhythm360's implementation process, including EHR integration, typically takes from a few days to a few weeks, which supports aggressive but achievable milestones.
• Staff training readiness. Clinicians receiving comprehensive onboarding training report higher platform satisfaction, per KLAS Arch Collaborative data. Develop role-stratified curricula for CCTs, clinical reviewers, and billing staff before scheduling any sessions.
• Data-quality audit. Inventory all active OEM patient populations, transmission schedules, and existing CPT billing documentation. Flag gaps in historical data that could affect first-month reporting accuracy on the unified platform.
• Phased rollout milestones. Define go/no-go criteria for each phase, including pilot cohort transmission accuracy, staff login utilization rates, and CPT claim acceptance rates. Three measurable indicators of technology adoption are Speed of Adoption, Utilization Rate, and Proficiency Level. Track all three from day one.

Common Pitfalls in Cardiology Technology Transitions

Several failure patterns recur across cardiology platform transitions and can be anticipated.

• Multi-portal overload during transition. Running legacy OEM portals in parallel with a new unified platform for extended periods creates dual-entry burden and slows adoption. Set a firm sunset date for legacy portal access within the rollout plan.
• Alert fatigue during cutover. When engineers and clinicians are exposed daily to hundreds of false-positive critical alerts, they exhibit normalization of deviance, writing scripts to auto-clear categories of alerts or routing them to folders checked only weekly. Configure and validate AI-powered alert triage that filters non-actionable notifications before full patient population migration.
• Unclear billing ownership. CPT code documentation for remote monitoring requires defined accountability for review, signature, and submission. Ambiguity at any step produces claim denials. Assign billing workflow ownership during the guiding-coalition formation stage, not after go-live.
• Underestimating training needs. Organizations underinvesting in change management are more likely to miss adoption targets.
• Skipping the refreeze stage. Skipping steps in Kotter's model is a common reason change initiatives fail; staff revert to old habits within weeks when urgency or coalition-building steps are bypassed. Sustained adoption requires policy updates, metric realignment, and removal of legacy workflow artifacts.

Measurement and Ongoing Optimization for Cardiac Monitoring Programs

Cardiology practices gain the most value when they track four categories of metrics from go-live onward.

• Clinical metrics. Monitor critical-alert response time, targeting the reduction levels achieved in successful pilots, along with transmission review completion rates and the rate of earlier clinical interventions. Andrew Beaser, MD, at the University of Chicago Medicine, noted: "We are able to address these issues earlier; rather than waiting for a 3-month visit, we can call patients in for evaluation." UCM reviewed more than 73,000 reports annually through Rhythm360 in 2025, averaging more than 18,000 reports per quarter.
• Operational metrics. Track staff hours saved on data retrieval per week, login utilization rates across all user roles, and super-user support ticket volume trends. Organizations that define success clearly at the outset and measure performance against specific clinical, operational, and financial outcomes are up to 5x more likely to meet or exceed them.
• Financial metrics. Measure first-pass CPT claim acceptance rates for remote monitoring codes, total billable events captured per month, and revenue recovered from previously undocumented transmissions. A practice enrolling 200 patients in an RPM program typically generates $144K–$204K in annual revenue (or up to ~$300K in optimistic cases) at $60–$150 per patient per month via CPT codes 99453–99458.
• Compliance metrics. Monitor HIPAA audit trail completeness, data transmissibility rates, and documentation turnaround times for signed reports. Rhythm360 achieves greater than 99.9% transmissibility through redundant data feeds, computer vision, and AI-powered extrapolation.

Request a walkthrough of Rhythm360's metrics module to see how the administrative dashboard surfaces clinical, operational, and billing metrics in a single real-time view.

Conclusion: Turning Change into Measurable Cardiac Care Improvement

Fragmented OEM portals, manual transmission workflows, and disconnected billing documentation represent change management problems rather than pure technology problems. Kotter's 8-step model provides the sequential structure to build urgency, assemble coalitions, and anchor new behaviors in cardiology practice culture. Lewin's 3-stage model provides the psychological pacing to unfreeze established routines, execute a phased platform transition, and refreeze unified workflows into policy and performance systems.

Used together, these frameworks help cardiology practices achieve up to 80% faster critical-alert response times and measurable improvements in CPT code capture, while reducing the workflow disruption that derails many healthcare technology initiatives. Gaurav A. Upadhyay, MD, at the University of Chicago Medicine, summarized the value of a unified approach: "That was a big piece for us, to have an integrated review of data from trained personnel."

Rhythm360 by RhythmScience is a vendor-neutral, HIPAA-compliant platform built as the endpoint of this kind of structured transition. It consolidates data from all major device manufacturers into a single AI-powered dashboard with bi-directional EHR integration and automated CPT documentation.

Talk with the Rhythm360 team to shape a change management playbook tailored to your cardiology practice.

Frequently Asked Questions

What is change management in healthcare, and why does it matter for cardiology practices?

Change management in healthcare is the structured process of planning, executing, and sustaining clinical, operational, and technological transitions while protecting patient safety, staff well-being, and financial performance. For cardiology practices, it matters because technology transitions, particularly the move from fragmented OEM portals to a unified cardiac monitoring platform, involve simultaneous changes to clinical workflows, billing documentation processes, staff roles, and EHR data flows. Without a structured approach, practices risk alert fatigue during cutover, CPT documentation gaps, staff burnout, and reversion to legacy workflows. Applying proven frameworks such as Kotter's 8-step model and Lewin's 3-stage model gives practice leaders a repeatable, evidence-based method for managing these transitions with measurable outcomes.

How does Kotter's 8-step model apply specifically to RPM and CIED platform adoption?

Kotter's model maps directly to the operational realities of a multi-OEM cardiac monitoring transition. The urgency step uses quantified data, including delayed alert response times, denied CPT claims, and staff hours lost to portal switching, to build the case for change. The guiding coalition brings together electrophysiologists, CCTs, practice administrators, and billing staff as co-owners of the transition. Vision and communication steps ensure every role understands what the unified platform will look like in daily practice. Barrier removal addresses EHR integration timelines and legacy data export formats. Short-term wins from a pilot cohort build momentum before full population migration. The final anchoring step embeds the unified platform in onboarding, performance reviews, and quality metrics so that reversion to OEM portals becomes structurally difficult rather than simply discouraged.

What is Lewin's change model, and how does it differ from Kotter's approach in healthcare settings?

Lewin's 3-stage model, Unfreeze, Change, Refreeze, focuses on the psychological and behavioral dimensions of transition. The Unfreeze stage disrupts the current state by making existing pain visible through data and peer testimony, which reduces the emotional attachment staff have to established routines. The Change stage introduces the new platform through phased rollout, role-based training, and visible leadership support. The Refreeze stage stabilizes the change by embedding new behaviors into policy, performance metrics, and workflow design so that adoption does not erode over time. Kotter's model is more sequential and action-oriented, suited to building organizational momentum across a large initiative. Lewin's model is more useful for pacing and stabilization, particularly when staff have experienced prior failed technology transitions and carry residual skepticism. In practice, the two frameworks are complementary, with Kotter driving the enterprise-level change program and Lewin guiding the human-centered pacing within each phase.

What are the most common pitfalls when adopting a unified cardiac monitoring platform?

The most common pitfalls fall into four categories. First, running legacy OEM portals in parallel with the new platform for too long creates dual-entry burden and slows adoption, so a defined sunset date for legacy access is essential. Second, alert fatigue during the transition period, when both old and new notification systems are active simultaneously, can cause clinicians to dismiss or delay acting on critical alerts, so AI-powered triage must be validated before full migration. Third, unclear ownership of CPT billing documentation produces claim denials that undermine the financial case for the platform, so billing accountability must be assigned during coalition formation, not after go-live. Fourth, underinvestment in training, particularly role-specific, workflow-anchored training for CCTs, clinical reviewers, and billing staff, leads to workarounds that become permanent and prevent the practice from realizing the platform's full clinical and financial potential.

How does Rhythm360 support a structured change management process for cardiology practices?

Rhythm360 is designed to reduce the organizational friction of a multi-OEM transition. Its vendor-neutral architecture consolidates data from all major device manufacturers, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, into a single dashboard, which eliminates the need for multiple portal logins from day one of go-live. Bi-directional EHR integration with Epic, Cerner, Athenahealth, eClinicalWorks, and others via HL7 removes the manual transcription step that consumes the most staff time during legacy workflows. AI-powered alert triage filters non-actionable notifications and prioritizes clinically significant events, directly addressing the alert-fatigue risk that peaks during platform transitions. Automated CPT documentation supports billing staff in capturing remote monitoring codes accurately and consistently. The platform's implementation timeline, from a few days to a few weeks including EHR integration, is structured to minimize the parallel-operation period that drives dual-entry burden. Optional 24/7/365 oversight by certified cardiac technicians supervised by physicians provides a clinical safety net during the transition period while internal staff build proficiency on the new system.