How a Structured Heart Failure Monitoring Program Changed the Way We Care for Patients

By Alanna Miller, DNP, AGACNP-BC
Lead Advanced Practitioner of Cardiac Electrophysiology, Penn Medicine

Heart failure rarely begins with a hospitalization.

In many cases, physiologic changes occur days or even weeks before a patient recognizes symptoms severe enough to seek medical attention. For years, we have had implantable devices capable of detecting those changes early. Like many electrophysiology and device programs, we had access to valuable heart failure diagnostic data. The challenge wasn't collecting the information, it was consistently translating that information into clinical action.

At Penn Presbyterian Medical Center, our electrophysiology program remotely monitors more than 5,500 patients with implantable cardiac devices. HeartLogic alerts were available within routine device transmissions, but like many remote monitoring programs, we faced a familiar question: what happens next when a heart failure alert appears?

Like many remote monitoring programs across the country, we faced challenges related to alert burden, staffing constraints, workflow variability, and ownership of device-generated data. Clinical decisions were thoughtful and patient-centered, but they were often being made without a standardized framework to ensure consistency and scalability.

The issue was never a lack of effort. The issue was building a system that could reliably turn data into action.

Building a More Structured Approach

As we began exploring ways to improve heart failure remote monitoring, it became clear that success would require more than technology alone.

We brought together electrophysiology physicians, heart failure specialists, APPs, nurses, and administrative leaders to develop a standardized workflow that everyone could follow. Our goal was to create a reliable process that could identify patients earlier and support timely intervention before heart failure decompensation. 

To operationalize the program at scale, we partnered with Octagos to incorporate structured clinical review support and workflow infrastructure into the process. Their Atlas AI platform and clinical review team helped filter routine transmissions, prioritize clinically relevant alerts, and reduce the administrative burden associated with large-scale remote monitoring. This allowed our clinicians to focus their attention where it was needed most while maintaining a manageable workload.

The workflow established clear thresholds, clear responsibilities, and consistent documentation.

Key components included:

• HeartLogic score greater than 16 triggered patient outreach and symptom assessment.
• HeartLogic score greater than 20 prompted escalation through a standardized management pathway.
• Patients continued to be monitored closely until recovery.
• Clinical encounters were documented using a structured template to ensure consistency across providers.

The workflow itself was intentionally straightforward. The impact came from standardization and consistency.

What We Learned

We launched an eight-week pilot involving 88 HeartLogic-enabled patients.

During that period, 78 alerts were generated, and more than 90% resulted in patient outreach within three days. These results are explored in more detail in our full heart failure monitoring case study. What we found was that managing these alerts was operationally feasible. The average clinician time required per actionable alert was approximately 12.5 minutes.

One of the most important lessons was that technology alone does not solve workflow challenges. Atlas AI and Octagos' clinical review infrastructure helped us efficiently manage incoming data, while our clinical protocols ensured that patients received timely and appropriate follow-up. Together, those components created a model that could scale without requiring additional clinical staffing. Successful programs require clear processes, defined ownership, and the ability to consistently act on the information being generated.

Shifting From Reactive to Proactive Care

For me, the most significant change wasn't a metric. It was the shift in how we interact with patients.

Historically, many heart failure interventions occurred after patients experienced worsening symptoms, called the office, or presented to the emergency department. By that point, we were often responding to a problem that had already progressed.

Now, we have opportunities to reach out first. Those conversations often begin with a simple question: "Your device data is showing some changes. How have you been feeling lately?"

Patients are frequently surprised that we're calling before they feel particularly sick. But those early conversations create opportunities to intervene sooner and help patients avoid more serious deterioration. They also build trust. Patients know someone is paying attention.

The Role of APPs

As an Advanced Practice Provider, one of the things I appreciate most about this work is the unique role APPs play in making programs like this successful.

APPs often sit at the center of remote monitoring workflows, coordinating care across specialties, communicating with patients, implementing protocols, and helping translate data into meaningful clinical action. We are frequently the bridge between technology, clinical decision-making, and patient care.

As remote monitoring programs continue to evolve, I believe APP leadership will be increasingly important in designing workflows that are both clinically effective and operationally sustainable.

Scaling the Program

What began as a pilot has continued to grow. Our monitored heart failure population expanded from 18 CardioMEMS patients to more than 150 actively managed heart failure patients without adding dedicated clinical staff. We also identified hundreds of additional patients whose implanted devices have heart failure diagnostic capabilities that can be incorporated into future workflows.

Perhaps the most meaningful outcome was that we were able to expand the program substantially without proportionally increasing staffing demands. In an environment where workforce shortages, increasing patient volumes, and clinician burnout are significant concerns, scalability matters just as much as clinical effectiveness.

Leveraging technology-enabled triage, clinical review support, and standardized workflows allowed us to grow the program while maintaining a sustainable model for our care team.

Remote monitoring has tremendous potential, but that potential can quickly be undermined when clinicians are overwhelmed by large volumes of nonactionable data. Effective programs must balance sensitivity with sustainability, ensuring that care teams can focus their attention where it matters most.

As remote monitoring programs continue to expand nationally, demonstrating both clinical value and operational sustainability will be essential for long-term success.

Looking Ahead

The next phase of our work includes integrating additional device-based heart failure diagnostics into the program and continuing to refine our workflows as new technologies become available.

What we've learned is that technology alone isn't enough. The data has been there for years. The real challenge is building systems that allow care teams to use that information consistently, efficiently, and at scale.

As remote monitoring volumes continue to grow, I believe many programs will face the same challenge we encountered. The limiting factor is no longer access to data, but the operational infrastructure required to act on it consistently.

For years, healthcare has focused on generating more patient data. The next challenge is determining how to use that data in ways that are clinically meaningful, operationally sustainable, and scalable across increasingly complex patient populations.

The future of remote monitoring won't be defined by who has the most data. It will be defined by who can consistently turn data into action.