Prepared for Florida Cardiovascular Partners · 2026 Remote Care Strategy Review · Confidential — not for distribution
Cardiovascular Service Line Optimization · Stuart · Port St. Lucie · Tradition · Vero Beach · Sebastian · Jupiter · Palm Beach Gardens

A Scalable, Profitable Remote Care Service Line
for Florida Cardiovascular Partners.

The group's billing entity is a participant taxpayer identification number in an ENHANCED-track accountable care organization — the Shared Savings Program's two-sided downside option, in its fourth agreement period. A remote monitoring program and a chronic care management program are already live and publicly marketed, and the monitoring FAQ names congestive heart failure as a qualifying population. So this is not a whitespace argument. It is a depth, completeness and coverage argument across seven sites and four counties — made without disparaging what is already in place.

$0
24-Month Net Reimbursement
0%
24-Month Practice Margin
0
Hospitalizations Avoided
0
Unique Patients in Active Remote Care at Month 24

Source: the companion CoachCare Value Analysis workbook, MAC locality FL • 09102-03, auto-resolved from the Stuart headquarters ZIP 34996.

The Starting Position

This Is Not a Whitespace Account — and This Page Is Written That Way.

Most documents of this kind open a gap: no monitoring program, no care-management program, no between-visit workflow. That is not the situation here, and pretending otherwise would be falsified in the first meeting. Both programs exist, both are publicly marketed, and both appear to be billed rather than given away. Everything that follows treats them as real and as an asset, and asks a narrower question — how deep, how complete, how uniform across seven sites.

★ Verified — the practice's own service page

A remote monitoring program, already live

A complimentary blood-pressure monitor based on the patient's condition, delivered direct to the home and arriving preconfigured — "No smartphone, Wi-Fi connection, or mobile application is required" — with automatic transmission of readings and access to a dedicated remote nurse. The program's own FAQ names congestive heart failure as a qualifying population and discusses Medicare coverage and patient cost-share ahead of enrollment.

★ Verified — the practice's own service page

A care-management program, branded "Connected Care"

A personalized care plan and a dedicated care manager covering scheduling, symptom monitoring, medication questions, refills, referral coordination and lab results — by phone and text, with no application to download and no website to log into. It is explicitly multi-condition, naming high blood pressure, heart disease, diabetes, arthritis and chronic pain.

✓ Verified — CMS ACO Participants file

ENHANCED-track two-sided downside risk

The group's legal entity appears as a participant taxpayer identification number in PBACO Holding, LLC (ACO A1001) — a physician-led Shared Savings Program organization in its fourth agreement period with 822 participant taxpayer identification numbers, current agreement start January 1 2025, retrospective assignment, and ENHANCED_Track set. Under two-sided risk a bad year produces an invoice, not a missing bonus.

✓ Verified — the live patient portal

Your own record, in your own tenant

Global navigation links on every page to a live NextGen Patient Experience Platform portal — NextGen's hosted portal, tightly coupled to NextGen Enterprise. The tenant slug encodes the legacy professional-association form of the Stuart cardiology name plus an internal client identifier, so the relationship predates the December 2025 rebrand. No migration in flight, no competing build queue, and no tenant-ownership question.

The hard part of a remote care program is not the technology. It is the operating habit — enrollment that actually happens, a triage inbox somebody owns, an escalation standard written down, and billing that captures what was delivered. Two of the hardest inputs to that habit already exist here: a working device-and-nurse workflow, and a patient population conditioned to receive care between visits. What is not established from any public source is how deep that workflow runs, how completely it bills, and whether it reaches all seven sites equally.

The 2026–2027 Payment Environment

Two-Sided Downside Risk Today. A Specialty-Model Question for 2027.

Two CMS positions bear directly on this practice. One is live today and carries real downside. The other begins in five months and is currently recorded against legal entities the group acquired. Both come from CMS primary files.

ENHANCED

Two-Sided Downside Risk — the Sharpest Fact Here

The group's billing entity is a participant taxpayer identification number in PBACO Holding, LLC (ACO A1001), a physician-led Medicare Shared Savings Program organization with a service area spanning six states. The record carries an initial start of July 1 2012, a current agreement start of January 1 2025, a fourth agreement period, low-revenue status, retrospective assignment, the skilled-nursing three-day-rule waiver — and the operative field, ENHANCED_Track = 1. 822 participant taxpayer identification numbers sit on the same organization identifier.

The ENHANCED track is the program's highest risk-and-reward option: an organization on it shares savings at the highest rate and owes CMS money when spending exceeds the benchmark. That is categorically different from an upside-only arrangement. Avoidable admissions, readmissions and emergency department visits stop being missed upside and become a charge — which turns remote monitoring and care management from a revenue program with a quality halo into margin defense with a revenue program attached.

Correction A widely used commercial firmographic file records a different, health-system-affiliated Florida accountable care organization for this practice. The CMS file does not support that: that organization's participant list contains exactly four entities, all belonging to the same health system, and this group's legal name is not among them. The likely origin is an affiliation-based inference from a hospital relationship. Worth correcting in the practice's own records.

Preliminary CY2027 list
ASM · −9/+9%

Two Physicians Named — Under Legacy Entities, Not the Group's Own

Two of the group's physicians are named on the CMS preliminary CY2027 participant list for the Ambulatory Specialty Model, under the pre-acquisition legal entities of the Vero Beach and Sebastian sites — not under the group's own billing entity. Both sit in the Heart Failure cohort and both carry the CY2027 small-practice flag. The Vero Beach listing sits under TREASURE COAST CARDIOVASCULAR INSTITUTE INC; the Sebastian listing sits under a solo-physician professional association carrying that physician's own name, which this page does not reproduce. The group's own billing entity, STUART CARDIOLOGY GROUP LLC, returns zero rows in that file.

CMS states the payment adjustment runs −9% to +9% in the first two performance years, rising toward −12% to +12% by the final performance year. Performance year 1 is calendar 2027, and that performance lands as a payment adjustment in 2029. The design is budget-neutral and scored against peers treating the same condition; participation is mandatory for attributed clinicians.

Preliminary · 19 of 25 This is the CY2027 preliminary participant file (dataset modified 2026-02-04, retrieved 2026-08-03); CY2028–CY2031 flags are null. The check is complete for 19 of the group's 25 physicians — six could not be resolved to a National Provider Identifier and remain open.

Billing Tailwind
CY2026

Short-Window RPM Is Now Billable

New codes 99445 (the monthly device-supply amount for 2–15 days of data, where 16 or more were previously required) and 99470 (the first 10 minutes of monthly management time, where the floor had been 20) convert the days after a cardiac discharge and the days after a device or valve procedure from unfunded care into billable events.

There is an account-specific reason to raise this early, and it is not a criticism. A monitoring program designed before 2026 was necessarily built around a 16-day data threshold and a 20-minute time floor, because nothing else was payable. A program built to those thresholds has no mechanism to bill the two-week window after a discharge or an implant — the window in which a readmission is still preventable and, under two-sided risk, the window with the most avoidable cost in it. It is a policy change that arrived in 2026, and it is worth asking whether the current configuration has been revisited since.

What the specialty model grades — and why the entity question matters
  • Four categories Quality, Cost, Care Improvement Activities and Promoting Interoperability. Quality and cost are scored per clinician; care improvement activities and interoperability are scored at the group level — so half the scorecard turns on infrastructure decisions rather than individual effort.
  • Participants are identified by taxpayer identification number and National Provider Identifier That is precisely why a designation recorded against a pre-acquisition entity is a live question rather than a footnote. Model obligations follow the identifier pair, not the brand.
  • Both possible answers carry work If those physicians now bill under the group's own taxpayer identification number, the CY2027 attribution may not follow them — and the practice may be carrying obligations nobody owns, or may have quietly shed them. If the legacy entities are still active, the group is running two separately-identified participant entities inside one brand, with the reporting burden that implies.
  • The small-practice flag is itself a signal That an entity sitting inside a 40-clinician group is still flagged as a small practice indicates CMS is not yet seeing those sites as part of the group.
  • A collaborative care arrangement with primary care is required This group has no primary-care panel of its own, so that arrangement is an electronic artifact built with external referring physicians — a shared care plan, structured monthly reporting back, and explicit task ownership.
  • Timeline Five performance years beginning January 1 2027, payment years 2029 through 2033.
What is verified about the footprint — and what is deliberately absent
  • Seven active locations, four counties, three statistical areas Stuart (headquarters), Port St. Lucie, Tradition, Vero Beach, Sebastian, Jupiter and Palm Beach Gardens — across Martin, St. Lucie, Indian River and Palm Beach counties. An eighth site relocated into the Stuart headquarters in July 2026; eight remains the practice's own marketing figure, seven is what the location pages expose.
  • Forty referring clinicians 25 physicians — 24 cardiologists and one vascular specialist — plus 15 advanced practice providers, counted individually from the practice's own profile pages on 2026-08-03. Roughly 190 employees, per the practice's own rebrand announcement.
  • Sponsor-backed since 2023, rebranded 2025-12-01 Unresolved The practice describes itself on every page as part of a national clinician network it abbreviates on its own materials, and routes hiring there rather than to the practice. The corporate identity behind that abbreviation could not be resolved from any public source. One frequently assumed candidate was tested and ruled out on a decisive negative: this practice does not appear on that company's own published partner-practice list.
  • The commercial consequence is concrete If remote monitoring and care management were standardized above the practice, the buying unit is not the practice. Establishing where that decision sits is the first qualification question in this account, ahead of any pricing conversation.
  • One ZIP, three statistical areas The Value Analysis auto-resolves MAC locality FL • 09102-03 from the Stuart headquarters ZIP 34996, and every modeled dollar on this page uses it.
Heart Failure
Hypertension
Post-Discharge
Structural Heart & Device
Build vs. Partner

The Programs Already Running — Credited First, Then Measured

The build-versus-buy question is already answered here, and it was answered in the right direction. Cellular devices, drop-shipped logistics, a dedicated remote nurse and a dedicated care manager are the components most groups spend a year assembling. The remaining question is a yield question, and it is arithmetic rather than philosophy.

ProgramWhat the practice's own page statesWhat that establishes
Remote patient monitoring Tracks key health data between appointments — blood pressure readings, body weight measurements, or other cardiovascular indicators. A complimentary blood-pressure monitor based on the patient's condition. Direct delivery of the device to the home. Automatic transmission of readings to the care team. Access to a dedicated remote nurse. Devices arrive preconfigured, with no smartphone, Wi-Fi connection or mobile application required. Cellular devices, not application-paired. "Preconfigured, no smartphone or Wi-Fi" is the signature of a cellular cuff. Drop-shipped logistics implies a fulfilment partner — practices rarely build direct-to-home device fulfilment themselves. And the FAQ discusses Medicare coverage and patient cost-share ahead of enrollment, which means it is billed, not a free perk.
Chronic care management, branded "Connected Care" Additional access to the healthcare team between appointments. A personalized care plan and a dedicated care manager. Scheduling, symptom monitoring, medication questions, prescription refills, referral coordination and lab results. Contact by phone or text; no application to download and no website to log into. Supports high blood pressure, heart disease, diabetes, arthritis, chronic pain and other long-term concerns. A real, staffed, multi-condition care-management service. The cost disclosure — coverage varies, some patients may have a cost-sharing responsibility — is consistent with a billed program. The deliberate absence of any portal or application is a defensible service-design choice, and it is also a constraint on documentation rigour and time capture.

Read verbatim from the practice's two dedicated public service pages, retrieved 2026-08-03.

No vendor is named here, because none could be identified. A full inspection of both program pages found no remote-monitoring vendor script, pixel, iframe or asset of any kind. The only third-party hosts referenced anywhere are the practice's own electronic-record patient portal, a patient intake-and-payments platform, and the practice's own content-management host. That absence is itself informative: a fully telephonic, nurse-delivered service with no patient-facing web application leaves exactly this footprint — and that is what both pages describe. Whether the nurse is the practice's own employee or a partner's staff, and whether one platform or two sit behind the programs, is not publicly discoverable.

Where a Partnered Model Adds Depth Rather Than Duplication

The credible argument is not novelty. It is scale, completeness and uniformity — and it rests on what the public pages describe and on what they do not.

DimensionWhat the public description coversWhere the depth question sits
Billing ladderDevice supply and nurse review are described. Nothing on the pages speaks to escalation workflow, documented management minutes, or the time-tier rungs.The classic failure mode of a device-led monitoring program is billing the device-supply base and leaving 99457, 99470, 99458 and the PCM family uncaptured. That is not an accusation — it is the single most common finding in this kind of audit, and it is checkable in one report from the practice's own billing system.
ModalityBlood pressure is named explicitly; body weight is named as an option.Weight is the heart-failure signal. A blood-pressure-first program is built for hypertension; a heart-failure cohort needs daily weight with threshold alerting as the primary stream. Given the CY2027 Heart Failure finding, that is a specific and answerable question.
Short windowsNothing on either page addresses the post-discharge or post-procedure window.99445 and 99470 only became billable in CY2026. A program configured before then had no reason to build a two-week pathway — and the two weeks after a discharge is where avoidable readmission cost concentrates.
Coverage across seven sitesThe pages describe the programs at brand level; nothing establishes per-site coverage.Two sites still surface in a CMS file under their pre-acquisition legal entities. Uniform program coverage across a four-county, seven-site footprint is a reasonable thing to verify rather than assume.
Documentation and time capturePhone and text, with no portal and no application, by design.Time-based codes are audited on documented time. A low-technology contact model is clinically defensible and operationally sound; it makes automated, billing-grade time capture harder, and that is where an integrated engine contributes most.
Census and yieldUnknown. Marketing a program establishes nothing about enrolled penetration.This is the first number to ask for, and it reframes the entire conversation. A program at 200 enrolled patients across 40 clinicians and a 26,035-patient modeled base is a pilot; a program at 2,000 is an operation. The strategy differs completely between those two answers.

The Three Honest Outcomes, Named in Advance

All three are legitimate. Six questions distinguish them in one conversation, which is a better use of a first meeting than a pitch.

Outcome 1

Co-exist

The existing program keeps the population it serves well, and the service line adds what it does not reach: the heart-failure weight stream, the short post-discharge and post-implant windows, the sites with thinner coverage, and billing completeness on the management-time rungs.

Outcome 2

Displace

The existing arrangement turns out to be a thin pilot, and a full-service model replaces it with more census, more codes and uniform coverage across all seven sites under one operating standard rather than seven local habits.

Walk away

The program is already at scale, billing the full ladder, uniform across seven sites — and the decision sits above the practice anyway. That would be a good outcome to discover, and it is worth saying so.

The six questions that decide it. 1 · Where does the decision sit — the practice, or the organization above it? 2 · What is the enrolled census today, by program and by site? 3 · Which codes are actually being billed — is management time captured beyond device supply, are the add-on rungs used, and has anything been billed in the 2–15 day window since CY2026 made it payable? 4 · Is the program uniform across all seven sites, including Vero Beach and Sebastian — the two sites that arrived with their own legal entities and the two carrying the CY2027 Heart Failure designation? 5 · Does monitoring data flow into the electronic record as discrete elements, or sit in a separate system? 6 · Is remote device interrogation billed separately, and by whom?
The Operating Model

One Service Line, Three Sequenced Layers

A named service line with its own owner, P&L and scorecard, following the Medicare patient from the hospital bed back into the practice and then across the year. Built once for seven sites, and reused for every lever the group already carries.

1 · At Discharge — TCM
  • What Structured 30-day post-discharge management: interactive contact within two business days, medication reconciliation, and a face-to-face visit inside the window.
  • Why here The group performs catheterization, valve procedures, device and loop-recorder implants, carotid endarterectomy and vascular surgery across three admitting hospitals. That generates a continuous stream of discharges belonging to this practice, and those 30 days are outpatient cardiology.
  • Discovery question The practice's website says nothing about a post-discharge program — one of the more valuable questions to ask in the first conversation.
2 · The First Two Weeks — Short-Window RPM
  • What A 2–15-day device supply and first-10-minute management bundle (99445 · 99470) placed on the patient at discharge or at implant, before the 30-day clock runs out.
  • Why here CY2026 is the first year this window is cleanly billable. Post-discharge weight, blood pressure and symptom data are where decompensation is either caught or missed — and under an ENHANCED-track arrangement a readmission inside that window is a direct charge, not a missed bonus.
  • Cheapest addition of all The enrollment relationship, the device logistics and the nurse already exist. The question is whether the trigger is a discharge or a clinic visit.
3 · Across the Year — RPM + PCM
  • RPM Device-based physiologic monitoring — weight, blood pressure, pulse — as the continuous early-warning and titration layer, with daily weight as the primary stream for heart failure rather than blood pressure alone.
  • PCM Principal Care Management for the single high-risk cardiac condition. In a cardiology panel the dominant condition genuinely is the cardiac one — the clinical situation the code family was written for, and the monthly billing chassis underneath guideline-directed titration.
  • Modeled The Value Analysis models RPM and PCM only. Transitional care management is identified and deliberately excluded from every financial figure, and sits as upside on top.
Why chronic care management is carried at zero in the model — a design choice, not an omission. It is the multi-condition instrument of primary care, and the modeled stack is the specialty stack. The practice's existing "Connected Care" program is explicitly multi-condition — its own page names high blood pressure, heart disease, diabetes, arthritis and chronic pain — so it already occupies precisely that space. The two are complements rather than competitors: PCM bills the cardiac condition monthly at specialty depth while the existing program handles the multi-condition wrapper. What they cannot be is billed for the same patient in the same month — which, alongside the rule that only one practitioner may bill remote physiologic monitoring for a given patient in any 30-day period, is exactly why an attribution policy has to be written down. With a monitoring program already enrolling and referring primary-care physicians managing many of the same people, that rule is being tested today, independent of anything on this page.
The staffing answer, up front. CoachCare operates the engine — enrollment outreach, device logistics, 24/7 monitoring, escalation, and billing-ready documentation — while the practice's physicians govern the protocols and make every clinical decision. Launch requires no new practice headcount. The forecast also assumes one on-site enrollment specialist funded by CoachCare: that specialist is CoachCare's expense and embedded value, and is never a deduction from practice margin. One planning note specific to this footprint — a single on-site specialist covering seven sites across roughly seventy miles will concentrate at headquarters unless the rotation and a telephonic lane are designed deliberately.

The CY2026 Billing Stack

ServiceCodes~CY2026 MagnitudeCardiovascular UseIn the model?
Transitional Care Management99495 · 99496~$200 / ~$280Every cardiac and post-procedure discharge across the three admitting hospitalsNo — upside
RPM setup & device supply99453 · 99454 · 99445 (new)~$20 setup · ~$52/mo99445 makes the 2–15-day post-discharge and post-implant window billableYes
RPM treatment management99457 · 99470 (new) · 99458~$52 · ~$26 · ~$41 add'lMonthly review, titration and escalation — the rungs that carry most of the yieldYes
Principal Care Management99424 · 99425 · 99426 · 99427~$79 / ~$57 · ~$60 + ~$50Single high-risk cardiac condition — heart failure or resistant hypertensionYes

Magnitudes shown are national non-facility approximations for orientation. The Value Analysis below uses CY2026 rates auto-resolved by MAC carrier and locality for ZIP 34996 — FL • 09102-03 — not these national figures.

One Build, Every Lever

The same infrastructure — enrollment, devices, alert triage, escalation, documentation, billing capture — powers each thing the group already carries. Read the list one way and it is six separate projects, each with its own budget line and its own reason to be deferred. Read it the other way and it is one asset.

Two-sided downside exposure
Avoidable utilization is a direct charge, not foregone upside. Avoidable admissions, readmissions and emergency department visits land on a shared-savings result the group's own taxpayer identification number sits inside. The service line supplies the mechanical chain that moves it — a monitored census, a threshold that fires, a nurse who reaches the patient the same day, and an outpatient intervention inside the week. Modeled at ~421 avoided hospitalizations over 24 months. How savings and losses are allocated among 822 participants is contractual and not public.
The CY2027 specialty-model question
Start where the designation sits. Both preliminary CY2027 Heart Failure listings sit at Vero Beach and Sebastian — the two most recently added, geographically furthest sites, and the ones most likely to have inherited a different program configuration. A monitored heart-failure census produces both the between-visit intervention that moves cost and the documentation the quality measures are scored from; one shared care plan across seven offices is the group-level artifact the model asks for.
The post-discharge window
Three admitting hospitals, three discharge feeds, and no shared record with any of them. Cleveland Clinic Martin North Hospital (CCN 100044), Jupiter Medical Center (100253) and St. Lucie Medical Center (100260) — CMS overall star ratings 3, 4 and 1 respectively. The single most common point of failure in a transitional-care program is not knowing who was discharged yesterday, and it is harder here than at a single-hospital practice. None of this requires a hospital's agreement to begin: the transitional-care and short-window monitoring revenue is the practice's own, billed under its own taxpayer identification number.
Procedural and device throughput
A monitored pathway is what keeps a post-procedure patient attached to this practice rather than transferring the relationship with the referral. Structural heart is live, an electrophysiology service implants pacemakers, generators and loop recorders, and a new ambulatory surgery center plus in-office positron-emission-tomography imaging are shifting volume into the outpatient setting. The physiologic layer sits alongside — not inside — device interrogation: 93294–93298 reads the implanted device's own telemetry, 99453 onward reads patient-generated data from a separate connected device. Different benefits over different data; the design rule is that the same data stream is never billed twice.
Capacity across seventy miles
The between-visit work is absorbed as delivered hours rather than clinic slots. The forecast models 67,354 care-team hours over 24 months — roughly 32.4 full-time-equivalents of monitoring, outreach, escalation and documentation carried by the service line rather than by practice staff, alongside 303,122 care-management tasks, 75,780 chart updates and 45,468 patient conversations. For a group with no identifiable population-health department, spread across seven sites in four counties, that is the layer that makes uniform coverage possible.
One operating standard, not seven local habits
A practice that has grown this quickly is exactly the kind that discovers its program inventory is not uniform across its sites. Two sites still surface in a CMS file under their pre-acquisition legal entities; the patient-portal tenant still carries a legacy legal name. That is integration debt, and it is normal after a rapid expansion — but it is also the argument for one enrollment workflow, one shared care plan, one escalation standard and one per-site scorecard rather than a blended average that hides exactly the coverage gap worth finding.
Integration · NextGen Enterprise

A Stable NextGen Tenant, and You Own It Outright

Every remote care program lives or dies on whether the data lands in the chart the clinicians already use. Here that chart is a long-standing NextGen tenant the practice controls itself — no migration in flight, no competing build queue, and no health system whose IT organization has to approve the scope.

What is established
  • Verified — direct, not inferred The practice's global navigation links, on every page, to a live NextGen Patient Experience Platform portal — NextGen's hosted patient portal, tightly coupled to NextGen Enterprise. A practice does not run that portal without running NextGen. Retrieved 2026-08-03.
  • Verified — the tenant predates the rebrand The portal's tenant slug encodes the legacy professional-association form of the Stuart cardiology name plus an internal client identifier, so the NextGen relationship is older than the December 2025 rebrand and the tenant record still carries the prior legal name.
  • Verified — the adjacent stack A patient intake-and-payments platform powers the practice's online bill-pay. Beyond that and the practice's own content-management host, no third-party clinical or monitoring platform appears in any page source across the home, patient-support, prepare-for-visit, insurance, referral or careers pages — and no competing electronic-record fingerprint appears anywhere.
  • Why that is good news here The practice controls its own record, unlike a group hosted inside a health system's instance. NextGen integration is a well-trodden path, and the only caveat worth flagging is that the tenant still carries a legacy legal name — the same pattern as the specialty-model finding: the brand moved faster than the underlying records did.
What this means for scoping — stated honestly
  • The sharpest technical finding in the account Discovery question Both program pages state there is no application to download and no portal to log into. That strongly suggests device readings and nurse contact time may not be flowing into NextGen as discrete, structured elements today — they may live in a separate system, or in call notes. If so, it has consequences for audit defensibility, for quality reporting, and for the electronic collaborative care arrangement the specialty model requires.
  • Integration scope No interface cost, timeline or capability is priced into the forecast. Integration capabilities are CoachCare-provided; connector, product version and delivery timeline are defined in contracting.
  • Why automated claim generation matters here specifically At a modeled 6,826 active program enrollments at month 24 across seven offices and 40 referring clinicians, the monthly billing task is thousands of per-patient, per-code, time-documented claims — 151,561 billed units over 24 months. No back office assembles that by hand, and the failure mode is not a rejected claim; it is a program that quietly stops billing what it delivers. That is the exact failure mode the depth questions above ask about.
  • What the integration delivers Enrollment as one order inside the existing chart rather than a separate login — which is what makes uniform enrollment across seven sites achievable; live enrollment and device status at the point of the next clinical decision; vitals, evidence of care and care plans written back on a monthly cadence; and claims generated from the monitoring record rather than assembled by hand.
The practice Seven offices · four counties 25 physicians · 15 advanced practice providers Clinical governance stays here THE PRACTICE'S OWN CHART NextGen Enterprise A single tenant the practice owns — no health-system instance, no migration in flight, no build queue Patient Experience Platform portal live · tenant predates the rebrand orders · flags vitals · notes COACHCARE Remote care engine Enrollment · device logistics 24/7 monitoring · escalation Time capture · claims-ready documentation No new practice headcount TO CONFIRM IN DISCOVERY 1 · Do device readings and nurse contact time reach the chart as discrete, structured elements today? 2 · Connector scope and product version   ·   3 · Per-site enrollment coverage across all seven offices

The Value Analysis on this page does not assume any particular integration depth. No interface cost, timeline or capability is priced into the forecast.

The Clinical Twin of the Value Analysis

Clinical Governance & Escalation

The economics prove the service line pays. This proves it is safe and disciplined. Every reading a patient takes routes through one shared escalation engine with defined thresholds, defined trends, defined routing and a defined documentation standard, so the practice never carries surveillance liability it did not agree to. This group already runs an electrophysiology service and a nurse-delivered monitoring program, so it will have strong, well-informed opinions about alert triage. That is the right conversation to have, and this is the floor it starts from.

One shared escalation engine

Both programs in this service line — remote physiologic monitoring and principal care management — route through the same logic. The engine is program-agnostic; the thresholds are set with the practice's physician lead, not by vendor defaults.

1

Critical value → escalate immediately

A reading at a critical threshold escalates regardless of whether the patient reports symptoms. There is no "wait and see" branch on a critical value, and no client preference can suppress it.

2

Out of range → retake, then symptom check

A non-critical out-of-range reading is worked rather than forwarded: confirm technique, retake, then run a structured symptom check. Most out-of-range readings resolve here — which is exactly why the practice's inbox stays clean.

3

Trend is defined objectively

An out-of-range trend is not a judgment call. It is three consecutive readings at least one hour apart for blood pressure or glucose, or three readings within seven days for heart rate. A confirmed trend escalates on the same footing as a threshold breach.

4

Unreachable is not a dead end

If the patient cannot be reached, the attempt is documented and a voicemail and callback request are left — and if the reading was critical or a confirmed trend, the escalation proceeds anyway. Silence never downgrades a clinical finding.

5

Every escalation is documented the same way

Six fields, every time, so the record is auditable and any event can be reconstructed.

VitalFindingsMethodContactOutcomeFollow-up
The emergent pathway — non-negotiable
  • Triggers Chest pain · new shortness of breath · signs of stroke · syncope · worst-ever headache · sudden swelling. Any of these reported during an outreach call activates the emergent protocol immediately.
  • Action 911 is called with the patient still on the line — the call is not ended and handed off.
  • If refused If the patient declines emergency services, they are routed to the clinic and the refusal is documented; if the situation warrants it, CoachCare activates 911 regardless.
  • The guarantee CoachCare's urgent and emergent policy supersedes any client-specific escalation preference. A practice can shape routing for everything else. It cannot lower the floor on an emergency.
Three-way routing — so the practice sees signal, not noise
  • Emergency Emergent symptoms or a critical value with clinical instability → 911, with the practice notified.
  • Non-critical A confirmed out-of-range reading or trend without emergent features → routed to the defined practice team member named in the escalation matrix, within the agreed window.
  • Stable / resolved Worked, retaken, resolved, patient asymptomatic → documented as an FYI in the record, not pushed as an alert. This is the branch that decides whether a program is sustainable in a practice that already runs a nurse-monitored inbox.
  • Named, not assumed The routing matrix — who receives what, in what window, and who covers after hours — is agreed with the practice before the first patient enrolls, and agreed per site across a seven-office footprint rather than once at headquarters.

The post-discharge three-touch cadence

Triggered automatically by any emergency-room visit or hospitalization reported in the last 60 days. This is the readmission-prevention spine — and the mechanism behind the ~421 hospitalizations avoided in the forecast below. It matters here specifically: under an ENHANCED-track arrangement, a readmission inside that window is a direct charge against a shared-savings result the practice's own taxpayer identification number sits inside.

Touch 1 · Day 1–2

Stabilize

Confirm the patient is home and safe, reconcile discharge medications against what is actually in the house, verify follow-up appointments exist, and confirm the monitoring device is set up and transmitting. Clinical alerts documented and escalated per the engine above.

Touch 2 · Day 5–8

Detect

The window where post-discharge decompensation typically declares itself. Symptom review, daily weight and blood-pressure trend review against the readings already flowing in, adherence check, and escalation on any confirmed threshold or trend.

Touch 3 · Day 12–14

Secure

Confirm the follow-up visit happened, close open issues, verify the patient understands the escalation path, and hand the patient into the longitudinal monitoring panel so the 30-day window closes with continuity rather than a cliff.

Continuity and discharge governance

Patients do not silently fall out of the program, and the practice is notified at every decision point.

A

Unreachable → escalate on a fixed cadence

A patient who stops responding is escalated to the practice first, then re-escalated every 30 days — not quietly dropped and not left accruing.

B

A hard backstop

If no instruction is received from the practice, discharge proceeds at 180 days. The clinic is notified in every case, and discharges generally process in the first week of the following month.

C

The practice always decides

Clinical discharge criteria, escalation thresholds and routing are the practice's to set. CoachCare executes them consistently and documents the execution — it does not overrule clinical judgment, with the single exception of the emergent floor above.

D

Auditable by design

Because every escalation carries the same six documented fields, any episode can be reconstructed end-to-end — which is what a risk-bearing accountable care position and a scored CMS specialty model both actually require.

Escalation thresholds, the routing matrix and the discharge criteria are configured with the practice's physicians during protocol design — the logic above is the standard operating floor, not a substitute for that design session. And one note specific to this group: if a device clinic is already triaging remote interrogation alerts, the staff who do that work are the natural operators of a physiologic program. The hardest habit is already in place; treat remote-monitoring governance here as a conversation with experts, not an education.
CoachCare Value Analysis · Modeled for Florida Cardiovascular Partners

The Value Analysis

A 24-month forecast for a two-program service line — remote physiologic monitoring and principal care management — across the group's seven offices, 40 referring clinicians, one CoachCare-funded on-site enrollment specialist, and CY2026 rates auto-resolved for MAC locality FL • 09102-03. Transitional care management revenue, shared-savings performance, avoided-admission savings and procedural throughput are not in these numbers. They are upside on top.

Enrolled Services Under Active Management

Monthly active enrollment by program · physician referrals (8 per clinician per month across 40 referring clinicians at 80% acceptance) plus one on-site enrollment specialist at 80 per month and a small telephonic stream, net of a 1.5% monthly discharge rate. Both arms are enrollment-limited, not ceiling-limited: RPM reaches 5,100 against a ceiling of 6,834 and PCM 1,725 against 6,639 — so month 24 is not a steady state and both curves are still climbing.

Monthly Economics — Net Reimbursement, Fees, Practice Margin

Net reimbursement after a 14% blended realization discount for payer mix and collection, against CoachCare fees. Month 1 is modeled at $1,578 of practice profit — the first profitable month is month 1. There is no J-curve here and no month in which the program is a net cost, because CoachCare funds the enrollment engine, the devices and the monitoring staff.

24-Month Net Reimbursement Mix

$8.35M total across the two-program stack. RPM is the volume engine at roughly three-quarters of net reimbursement; PCM is the longitudinal chronic layer and the arm with by far the most headroom — 1,725 enrolled at month 24 against a 6,639 ceiling.

The Financial Summary

LineYear 1Year 224-Month
RPM net reimbursement$1,566,230$4,780,527$6,346,757
PCM net reimbursement$485,850$1,519,784$2,005,635
Total net reimbursement$2,052,080$6,300,311$8,352,391
CoachCare fees$1,189,500$3,630,141$4,819,641
Practice net (after fees)$862,580$2,670,171$3,532,751
Practice margin42.03%42.38%42.30%
Includes one on-site enrollment specialist staffed at CoachCare's expense — embedded value already reflected in the fees above, never a deduction from practice margin.

Month-1 practice profit is $1,578; the first profitable month is month 1. By month 24 the program is modeled at $670,760 of monthly net reimbursement and $284,424 of monthly net to the practice. The full model is available as a companion workbook.

151,561

Billed Claims / Units

Recurring, subscription-like professional-fee volume over 24 months — on top of the existing procedural, device and imaging book, not instead of it.

662,476

Physiologic Readings

A continuous clinical picture of the heart failure, hypertension, post-discharge and post-implant populations between visits — with daily weight, not blood pressure alone, as the heart-failure stream.

~421

Hospitalizations Avoided

On the order of $6.3M of avoided acute cost at an assumed $15K per admission — and under two-sided downside risk, avoidable utilization is a direct charge rather than foregone upside.

32.4

FTE-Equivalent Absorbed

67,354 care-team hours of monitoring, outreach, escalation and documentation carried by the service line rather than by practice staff, across seven offices in four counties.

Test the Assumptions Yourself

Scenario Explorer

Every input below is an assumption, and every assumption is arguable. Move them and the 24-month forecast recomputes live. At the modeled settings this engine reproduces the companion Value Analysis workbook exactly, so any disagreement you have with the output is really a disagreement with an input, which is a much more productive conversation.

Build Your Own Forecast

Defaults are the modeled scenario. Enrollment ceilings are recomputed as panel × eligibility × conversion; RPM eligibility is 75% of the in-scope panel and PCM 85%.
24-mo net reimbursement
$8.35M
24-mo practice net
$3.53M
Margin %
42.3%
Enrolled services at M24
6,826
Hospitalizations avoided
~421

"Enrolled services" counts active program enrollments; a patient enrolled in both programs counts twice. At month 24 the model's 6,826 enrolled services correspond to 5,618 unique patients once dual enrollment is deduplicated. Because both arms are pace-limited rather than ceiling-limited, the referral and enrollment sliders move this forecast far more than the panel does — which is the real planning insight in this account.

Implementation

Diagnose in 30 Days.
First Census by Day 90.

Because programs already exist here, the first thirty days are diagnostic rather than constructive: census, code mix and per-site coverage before anything is built. CoachCare then operates the engine — enrollment outreach, device logistics, 24/7 monitoring, escalation and billing-ready documentation — while the group's physicians govern the protocols and make every clinical decision. Launch requires no new practice headcount, and the on-site enrollment specialist in the model is funded by CoachCare.

0–30 Days

Diagnose Before You Build

Establish where the remote-care decision sits — the practice, or the organization above it. Audit the existing programs for enrolled census, code mix and per-site coverage. Resolve the taxpayer-identification-number question at Vero Beach and Sebastian in writing, close the six unresolved physician identifiers, and confirm MAC locality site by site rather than assuming the Stuart ZIP prices the whole footprint.

31–90 Days

Charter, Stand Up, First Billable Enrollment

Service line chartered with its own P&L and a named physician lead. Attribution and coordination policy written before the next enrollment, not after the next denial — including the device-interrogation boundary. NextGen integration built; alert thresholds and the escalation matrix set by the physician lead; the on-site enrollment specialist placed with a defined seven-site rotation and a telephonic lane behind it; a discharge-notification process agreed with each of the three admitting hospitals.

91–180 Days

Start at the Northern Sites, Then Everywhere

Counter-intuitive but supported by the account's own structure: begin at Vero Beach and Sebastian, where both CY2027 listings sit and where uniform coverage is least likely, rather than at headquarters. Post-discharge across all three admitting hospitals follows, then the remaining five sites on the same protocol. Open a second enrollment pathway — both arms are pace-limited, so referral throughput, not eligibility, is the binding constraint.

181–365 Days

Enter 2027 With Results, Not Plans

Monthly per-site scorecard running — census, capture rate, revenue per patient-month, escalation volume, readmission signal — never a blended average that hides the coverage gap. Capture rate and readmission delta reported into the accountable care organization. The final CY2027 participant list re-verified the week CMS publishes it, and the transitional care management decision taken on its own merits.

About CoachCare

The Experience to Get It Right

The service line described on this page runs on infrastructure already proven at national scale.

500,000+

Patients Managed

Over 400 managed conditions for more than 500,000 patients.

10,000+

Clinicians on the Platform

Providers running remote care programmes day to day.

1,000+

Implementations

Successful program implementations.

5M+

Claims Generated

Care plan coding and billing generating over five million claims.

100M+

Vitals Recorded

Over 100 million vitals recorded and more than four million care actions enabled.

Policy Watch · CMS-1848-P

2027 Proposed Rule Insights

CMS's CY2027 Physician Fee Schedule proposed rule, published July 16, 2026, proposes to reprice remote physiologic monitoring. Here is what it reaches, what it leaves alone, and how the operating model behind this service line absorbs it.

1

The Proposal Is Confined to RPM

CMS's remote-monitoring proposals sit in one code family: RPM. CCM, PCM, and TCM are not part of them. That distinction lands directly on this forecast — PCM carries $2,005,635 of the modeled $8,352,392 in 24-month net reimbursement, and the TCM touch at discharge is outside the proposal entirely. Neither is in scope.

2

CoachCare Is Building the Contingencies Now

The delivery model has more than one shape, and CoachCare is preparing each so the service line's economics hold wherever the rule settles. One unbundles the program into its parts — SaaS platform, device logistics, and program enablement — priced as components. Another engages CoachCare to run the staffing itself, an MSO-style arrangement in which the practice owns the clinical program and the billing while CoachCare carries the labor model. Neither requires re-architecting the service line described on this page.

3

ACCESS Moves Remote Care to Risk-Based PMPM

Alongside the fee schedule, CMS's ACCESS Model pays remote care as a risk-based per-member-per-month arrangement rather than per code: recurring per-beneficiary payments, half of each one withheld and reconciled against outcome attainment. Cardiometabolic care is among its four clinical tracks. What earns under that structure — controlled pressures, titrated therapy, decompensations caught early — is what this service line is built to produce.

What the Proposal Actually Takes Off This Forecast

This forecast repriced code by code at CMS's CY2027 proposed values, at this practice's own MAC locality rather than national averages. Same enrollment, same phasing plan — only the rates move.

−20.5%
The headline per-code cut — device supply (99454 / 99445), the code the proposal reprices hardest.
−8.4%
The RPM patient-year, because device supply is only 31% of it — the management codes barely move.
−6.5%
The whole service line, because PCM carries 24.0% of the forecast and is not in scope.
RPM alone — the only code family in scope$6,346,757 over 24 months
−$530,387
−8.4% of RPM
The whole service line — RPM + PCM$8,352,392 over 24 months
−$541,639
−6.5% of the whole

Both bars run on the same dollar scale, so the red slice is nearly the same width in each — the same dollars, measured against a larger base. The empty track on the top bar is the care-management revenue RPM alone does not include.

RPM, retained at CY2027 proposed rates The proposed reduction PCM — not in scope

Repriced at this locality's own geographic adjusters. The RPM reductions fall almost entirely on practice expense, so the untouched work component carries more weight in some localities than others; the same repricing at national rates would be −8.8% on RPM. Of the $541,639, RPM accounts for $530,387 and the care-management arm for $11,252.

Where the Proposal Lands, Code Family by Code Family

CY2026 versus CMS's published CY2027 proposed values, shown at national non-facility amounts so they can be read against CMS's own tables. This practice's locality-adjusted amounts differ; the repricing above uses the local figures.

Code familyWhat CMS proposedCY2026CY2027 proposedChange
In scope — remote physiologic monitoring
99454 / 99445 · device supplyPractice expense recrosswalked$52.11$41.38−21%
99457 · management, first 20 minDirect practice expense removed$51.77$49.59−4%
99458 · management, each addl 20 minDirect practice expense removed$41.42$40.39−2%
99453 · setup and patient educationCrosswalked; one-time per patient$21.71$20.03−8%
Not in scope — the codes the proposal does not reach
99424–99427 · PCMNo structural change proposed$67.80$67.00−1%
99495 / 99496 · TCMNot addressed by the proposalOutside the remote-monitoring provisions entirely

National non-facility amounts; CY2027 values are CMS's own published proposals in Addendum B of CMS-1848-P. The care-management rows show the lead code in each family; every code in those families moves within about 4% in either direction, which is ordinary annual movement rather than a repricing. The RPM reductions are also phased — section 1848(c)(7) of the Act caps any one code's total-RVU reduction at 19% in a single year, and CMS publishes the affected codes, so CY2027 is a single-digit year for a typical program and the remainder arrives no earlier than CY2028.

None of this is final. CMS-1848-P is a proposed rule. Comments are due September 14, 2026, the final rule is expected in early November, and it takes effect January 1, 2027. CoachCare is leading the advocacy — filing comments, putting the device cost and pricing evidence in front of CMS that the rule itself states the agency does not have, and helping practices file their own. This practice gets the final rates, and the model rerun against them, the week they publish.