CMS’s Bid to Close a Compliance Gap May Widen Tech Chasm

The following is a thought leadership article expressing the views of Mordy Eisenberg, chief growth and product officer/co-founder, TapestryHealth, a data-driven medical care organization operating in the long-term care space and focused on reducing hospitalizations.

Remote monitoring needs stronger accountability, not an employment mandate that makes proven care models harder to operate.

CMS is right to scrutinize remote patient monitoring.

Any rapidly growing area of healthcare deserves clear clinical standards, meaningful oversight, and safeguards against waste and abuse. Remote patient monitoring and remote therapeutic monitoring should be no exception.

But CMS’s proposed response risks confusing two very different things: clinical accountability and employment structure.

As reported in the news, CMS is considering restricting Medicare payment for remote monitoring services performed by clinical staff employed by third-party organizations. More than 200 healthcare organizations have urged CMS not to finalize the proposed restrictions without further analysis and stakeholder engagement.

The concern is not merely about reimbursement. It is about whether healthcare organizations—especially smaller, rural, and operationally constrained practices—will continue to have the infrastructure required to deliver remote monitoring at scale.

From my perspective, CMS is trying to solve the right problem with the wrong policy.

Remote Monitoring Is an Operating Model

One of the biggest misconceptions about remote monitoring is that it is primarily a technology.

It is not.

The device may collect the data, but data collection is only the beginning. Effective remote monitoring requires an operating system built around that data:

• Device provisioning and logistics.

• Patient onboarding and education.

• Consistent review of incoming information.

• Identification of clinically meaningful changes.

• Communication with patients, caregivers, and facility staff.

• Documentation of interventions.

• Escalation to the appropriate practitioner.

• Coordination with the broader care team.

A device does not prevent a hospitalization. A dashboard does not recognize that a subtle change in blood pressure, oxygen saturation, weight, or heart rate represents the beginning of a clinical decline.

That value comes from the clinical workflow surrounding the technology.

The proposed policy appears to assume that the safest way to preserve accountability is to require the clinical staff performing these functions to be directly employed by the billing practitioner or practice. But an employment relationship does not automatically create better oversight, stronger documentation, or superior patient outcomes.

A clinician does not become more accountable simply because their name appears on a particular payroll.

The Adoption Chasm Is Operational

Healthcare leaders often talk about innovation as if adoption were primarily a purchasing decision.

It is not.

Buying technology is relatively easy. Redesigning clinical workflows, training staff, integrating new information into care delivery, maintaining patient engagement, and sustaining performance over time are much harder.

That is the adoption chasm.

Large health systems may have the capital, workforce, and management infrastructure to build comprehensive remote-monitoring operations internally. Many independent practices, rural providers, and post-acute organizations do not.

These organizations already face limited clinical capacity, fragmented technology environments, reimbursement pressure, and significant administrative demands. Telling them they must directly employ an entire remote-monitoring workforce does not make adoption safer. It may make adoption economically and operationally impossible.

It is similar to requiring a health system to employ its own cloud engineers before it can use cloud computing.

Healthcare routinely relies on specialized organizations for laboratory services, imaging, cybersecurity, revenue-cycle operations, pharmacy support, and other critical functions. The issue is not whether every person involved receives a paycheck from the same organization.

The issue is whether responsibilities are clearly defined, clinicians are appropriately supervised, information reaches the right practitioner, and the patient receives high-quality care.

Remote monitoring should be judged by the same standard.

This Matters in Post-Acute Care

The operational consequences may be especially significant in skilled nursing and senior care.

These environments care for clinically complex patients while operating under persistent staffing and financial pressure. Directors of nursing and facility teams are already managing medication changes, falls, infections, behavioral issues, documentation requirements, family communication, and survey readiness.

Remote monitoring can provide another layer of clinical visibility, but only if the supporting workflow operates consistently.

If CMS removes access to specialized clinical infrastructure, the work does not disappear. It shifts back to physicians, practices, and facility teams that may not have the staffing or systems to absorb it.

Some organizations will attempt to build the capability internally. Others will reduce enrollment, limit their programs, or leave remote monitoring altogether.

The result could be a widening divide between large organizations capable of internalizing the model and smaller providers serving vulnerable populations.

That is not modernization. It is consolidation by regulation.

Disclosure Matters

For transparency, TapestryHealth’s model is not affected by this proposed restriction.

That is important because this position is not about defending our own reimbursement structure or preserving a model that depends on the current rule.

It is about recognizing a larger policy problem.

A regulation can be commercially neutral for one organization and still be operationally harmful to the healthcare system. In fact, those of us who are not directly threatened by the proposal have a responsibility to speak plainly about its broader consequences.

The question should not be whether one organization benefits or loses. The question should be whether the policy improves access, accountability, clinical quality, and total cost of care.

Regulate Performance, Not Payroll

CMS has legitimate tools available to strengthen remote monitoring without dictating how every practice must structure its workforce.

It can establish clearer expectations for:

• Practitioner supervision.

• Clinical escalation protocols.

• Documentation and auditability.

• Patient consent and engagement.

• Data integrity.

• Minimum service requirements.

• Demonstrated medical necessity.

• Vendor and practitioner accountability.

• Measurement of clinical outcomes.

Those safeguards would address the quality and integrity of the service itself.

A direct-employment requirement addresses organizational structure. It assumes that ownership of labor is the same as control over care delivery.

It is not.

Healthcare organizations can—and should—remain clinically accountable for services supported by specialized partners. The answer is to strengthen that accountability, not eliminate the partnership model.

The Wrong Side of the Chasm

Remote monitoring is at an important stage of adoption.

The industry has moved beyond proving that physiological data can be collected outside a traditional clinical setting. The challenge now is turning that data into a reliable, scalable clinical intervention.

Crossing that chasm requires more than technology. It requires specialized workflows, trained teams, clear escalation pathways, and operating discipline.

CMS should be helping healthcare organizations build and access that infrastructure—not creating rules that make it available only to organizations large enough to own every component.

Program integrity matters. Clinical accountability matters. Responsible oversight matters.

But if a policy makes remote monitoring harder to adopt without demonstrating that it will improve outcomes, CMS may inadvertently protect the integrity of a billing code while weakening the care model behind it.

The better question is not, “Who employs the clinical staff?”

It is, “Who is accountable for the patient—and can they prove that the model works?”

That is the standard CMS should enforce.

Comments or questions? Contact Patrick Connole at pconnole@parkplacelive.com.