You already earned this revenue. You just never billed it.
Castle Connect ingests every pacemaker, ICD, and loop recorder transmission, applies the 91-day rule automatically, and tells billing exactly which remotes are billable — and which ones should have been billed already. Your device technician keeps the clinical review; this handles everything around it.
- 31%
- Capture rate measured
- $16,335
- Unbilled, identified
- 220
- Periods never claimed
Findings from one live cardiac device clinic: 1,366 transmissions reconciled against 8,640 claim lines across 454 patients. Your own numbers will differ — the audit below measures them.
Most practices are already earning this revenue. They just aren't capturing it.
Remote device monitoring is one of the most under-billed services in cardiology. The transmissions are coming in. The clinical work is happening. The documentation and billing simply falls through the gaps.
- Transmissions pile up unreviewed
- Scheduled and alert-driven transmissions arrive across every vendor portal. Without a single queue, they sit unread past the filing window.
- Billable events never get billed
- Each qualifying remote interrogation is a reimbursable CPT event. Missed reviews mean 93294–93298 revenue quietly walks out the door.
- Overdue patients go dark
- Patients who miss a scheduled remote check aren't just a compliance risk, they're lost recurring revenue and unmonitored clinical exposure.
From raw transmission to billed encounter — one workflow.
Ingest every transmission
HL7 feeds land in one normalized inbox — no portal hopping, no re-keying, and the raw message kept for audit.
Apply the billing rules
The 91-day rule, 31 days for loop recorders, in-office interrogations that close the window — applied automatically so only genuinely billable remotes reach the queue.
Chase what's missing
Patients past due for a remote surface immediately, with the contact details staff need to bring them back before the revenue lapses.
Bill on completion
The right CPT code is attached the moment review completes, then handed off to billing — nothing left uncaptured.
A 400-device panel can leave six figures on the table every year.
Every device is billable roughly four times a year. Miss one period per patient and a mid-sized panel loses tens of thousands — quietly, with no rejection notice, because a claim that is never filed never comes back.
- 4×/yr
- Billable periods per device
- 91 days
- Between billable remotes
- 90 days
- Commercial filing window
The codes the engine assigns
- 93294Remote pacemaker / CRT-P interrogation, per 90 days
- 93295Remote ICD / CRT-D interrogation, per 90 days
- 93296Remote monitoring technical support, per 90 days
- 93298Remote loop recorder (ILR) interrogation, per 30 days
Eligibility follows Novitas LCD L34833 and Article A56602 with NCD 20.8.1. Reimbursement varies by payer and locality, so Castle Connect uses your own fee schedule rather than an assumed one.
Everything your device clinic needs to run monitoring like a revenue engine.
Billing eligibility, decided
One queue of remotes that are actually billable, ordered by filing deadline, with the reason attached when one is not.
Overdue tracking
Automatically surface patients past their scheduled remote check and drive outreach before revenue and monitoring lapse.
Billing handoff
The correct CPT code is attached on completion and exported to your billing workflow — capture becomes the default, not the exception.
Vendor ingestion
Abbott Merlin.net HL7 today, normalized into one schema. Medtronic CareLink and Boston Scientific LATITUDE are next; the parser layer is per-vendor by design.
Find the patients you lost
Devices still transmitting from patients never seen again. Each one re-engaged restores roughly four billable remotes a year.
Audit trail
Every billing decision and outreach attempt is timestamped and attributable, so a claim can be defended long after it was filed.
Find out what you missed before you commit to anything.
Send two exports and we reconcile them period by period: every transmission your devices sent, against every claim you actually filed. You get the gap, the patients behind it, and the method — not a projection built on someone else's averages.
Every ambiguity resolves against the number rather than for it. Where the data can't settle a period, the report says so and excludes it.
- What you send
- Device transmissions with dates and device type, and your charges export at CPT level on service date. Both are standard reports.
- What comes back
- Billable periods with no matching claim valued at your own rates, capture rate by month and by device type, and a report that states its own method and limits.
Patient data protected. Every claim defensible.
Monitoring revenue only counts if it holds up. Castle Connect is engineered for the security and documentation standards cardiology practices are held to.
- HIPAA-aligned handling of PHI, under a signed business associate agreement
- Row-level security enforced in the database, not just the application
- Timestamped, attributable audit trail on every billing action
- Standards-based HL7 v2.5 ingestion, with the raw message retained