CT reimbursement intelligence
Connecticut Medicaid & Medicare Reimbursement for RPM, CCM & TCM
Use this page as a structured planning reference for Connecticut. Medicare code families provide a national baseline; Medicaid program, managed-care, provider-type, and setting rules require state and plan-level verification.
- Reviewed
- Refresh by
- Workbook
- File verified · 22.1 KB
Connecticut policy summary. Connecticut reimbursement planning requires a strict separation between statutory telehealth authority and current CMAP payment policy. Connecticut General Statutes Sec. 17b-245g includes remote patient monitoring within the broad definition of telehealth, but CMAP does not treat that definition as a blanket coverage or fee-schedule rule. The live CMAP telehealth page says the CMAP Telehealth Table is the complete list of procedure codes approved to be rendered via telehealth, and the current CMAP Telehealth FAQs describe covered telehealth operationally as synchronized audiovisual telemedicine and, where specified by DSS, synchronized audio-only service. Connecticut Office of Health Strategy planning materials further state that Connecticut Medicaid does not reimburse remote patient monitoring. Accordingly, do not model Connecticut Medicaid revenue from Medicare RPM codes 99453, 99454, 99445, 99457, 99458, 99470 or 99091 unless current DSS/CMAP code-level authority can be produced for the applicable date of service and provider type. If a service is delivered through telehealth, verify the exact code in the current Telehealth Table and then separately confirm provider type and specialty, underlying covered-service rules, reimbursement methodology or fee schedule, medical necessity, authorization, modifiers, documentation and service-specific limitations. Collectibility has a separate claims-lifecycle gate. The current CMAP Publications page still points providers to Chapter 5, Claim Submission Information, which requires claims to be submitted within one year of the actual date of service. For HUSKY A, B, C and D medical, dental, FQHC and behavioral-health services, Chapter 5 also describes defined one-year exception windows tied to a prior non-timely-filing denial, an other-insurance denial, or retroactive eligibility. Those exception rules do not turn an otherwise non-covered RPM code into a benefit, so coverage verification and timely filing must both pass independently. Current CMAP operations also require active program participation, accurate provider-file information and secure portal access; multi-factor authentication has been mandatory since August 1, 2026. The current 2026 Messages Archive now shows September 18-25 provider-file maintenance and September 23 claim reprocessing tied to PCMH enrollment and site status, reinforcing that enrollment, service-location and provider-file accuracy are active claims-collectibility controls rather than background administrative details. On September 17, 2026, CMS announced a $50 million Connecticut Rural Health Transformation investment for four rural hospital systems that includes telehealth, AI-enabled monitoring, chronic-disease management, and other delivery improvements. Treat that award as implementation capital, not reimbursement authority: grant-funded technology or workflow expansion does not establish that a Medicare-style RPM CPT code is payable by HUSKY Health. Treat the legacy Connecticut workbook as planning material only when it agrees with current DSS code-level and fee-schedule authority.
Freshness window: recheck the official source by October 1, 2026, or sooner after a material payer change. Effective/source context: Connecticut law includes remote patient monitoring within the broad statutory definition of telehealth, but that definition is not itself a payment rule. Current CMAP operational materials say covered telehealth is delivered through synchronized audiovisual telemedicine and, where DSS specifies, synchronized audio-only service, and the live Telehealth Table remains the complete code-level list for telehealth payment. Connecticut Office of Health Strategy planning materials also state that Connecticut Medicaid does not reimburse remote patient monitoring. The current CMAP Publications page still designates Provider Manual Chapter 5 as the controlling general claim-submission reference; Chapter 5 requires claims to be submitted within one year of the actual date of service, subject to defined exceptions. Treat RPM payment as unverified unless DSS/CMAP publishes current code-level authority, and treat timely filing as a separate collectibility gate even when the underlying service is otherwise covered. The current CMAP 2026 Messages Archive shows September 23 claim reprocessing tied to PCMH enrollment and site status, so provider enrollment and service-location data remain active payment controls. Primary reimbursement policy source: Connecticut Medical Assistance Program - Telehealth Information and current Telehealth Table rules
Supporting sources checked Connecticut Medical Assistance Program - Telehealth FAQs · Connecticut Medical Assistance Program - Provider Fee Schedule Download · Connecticut Medical Assistance Program - Provider Manual Chapter 5: Claim Submission Information and timely-filing rules · Connecticut General Statutes Sec. 17b-245g - Medicaid telehealth definition and reimbursement · Connecticut Office of Health Strategy - Statewide Health Care Facilities and Services Plan · Connecticut Medical Assistance Program - current provider responsibilities and enrollment status requirements · Connecticut Medical Assistance Program - 2026 important messages and provider-file / portal-security notices · CMS - September 17, 2026 Connecticut Rural Health Transformation investment; telehealth and AI-enabled monitoring implementation funding
Implementation funding - not reimbursement authority
Connecticut RHTP funding can finance deployment without creating CPT payment
CMS announced September 17, 2026 that a $50 million Connecticut Rural Health Transformation investment will support four rural hospital systems and includes telehealth, AI-enabled monitoring, chronic-disease management, and other care-delivery improvements. Treat the award as implementation capital: it does not establish HUSKY Health coverage, a Medicaid fee, or managed-care payment for a specific RPM, CCM, or TCM code.
CMS - September 17, 2026 Connecticut Rural Health Transformation investmentLegacy workbook check: matching CT workbook physically verified in the WordPress media library. The official policy source above has been checked; legacy workbook values still require value-level validation before operational use.
October 1, 2026 eligibility transition: verify the member on the date of service
Federal Medicaid and CHIP matching rules change for certain noncitizen eligibility categories beginning October 1, 2026. CMS instructed states to redetermine potentially affected current beneficiaries by that date. State implementation and any state-funded coverage pathways can differ, so this notice does not replace Connecticut eligibility guidance. For RPM, CCM, and TCM collectibility, re-check the member's active eligibility, payer, delivery system, and managed-care assignment for the actual date of service rather than carrying a pre-transition result forward.
October 1, 2026 coding and claim-edit transition: use date-of-service rules
CMS has released FY 2027 ICD-10-CM codes for patient encounters from October 1, 2026 through September 30, 2027, plus the October 2026 HCPCS quarterly file, which CMS updated September 23, 2026. RPM, CCM, and TCM are billed with CPT/HCPCS service codes, but diagnosis coding and effective-dated HCPCS changes can affect medical-necessity edits, authorization, claim routing, risk adjustment, and claim acceptance. For dates of service on or after October 1, use the diagnosis and HCPCS sets applicable to that date and check Connecticut Medicaid and the member's managed-care plan for any separate claims-system or companion-guide instructions.
CMS has also posted Medicare and Medicaid National Correct Coding Initiative updates effective October 1, 2026, with Q4 change files posted September 1, 2026 and Medicare practitioner and hospital PTP production files posted September 2. The October releases include procedure-to-procedure edits, medically unlikely edits, and Medicare add-on-code edits. Do not infer that an RPM, CCM, or TCM code became covered, noncovered, payable, or denied merely because it appears in an NCCI file; evaluate the exact code pair, units, modifier indicator, payer, provider, and date of service. CMS expressly notes that a code's presence in a Medicaid NCCI edit does not establish coverage by a state Medicaid program.
What to verify in Connecticut
Build the reimbursement picture in layers
Medicare baseline
Confirm the applicable physician fee schedule, MAC/locality, clinician QP or non-QP status, code descriptors, supervision rules, device/data requirements, time thresholds, and any annual coding changes.
Connecticut Medicaid program
Review the current fee schedule, provider manual, telehealth or remote-monitoring guidance, eligible provider types, places of service, and billing limitations.
Managed care
Do not assume state-level policy equals MCO payment. Verify plan contracts, prior authorization, care-management benefits, alternative payment methods, and value-based arrangements separately.
Claims lifecycle
Check timely-filing, clean-claim, corrected-claim, reconsideration, appeal, recoupment, and payer-specific denial-recovery windows before treating an otherwise covered service as collectible.
Eligibility & coordination
Verify member eligibility and plan assignment for the date of service, then confirm Medicare, commercial insurance, other third-party liability, crossover, and payer-of-last-resort rules when they apply.
Revenue model
Model payer mix, eligible patient volume, realistic utilization, staffing, device/platform expense, contract-specific reimbursement, denial leakage, and realistic collection timing only after the policy and claims assumptions are verified.
Verified Medicare baseline
CY 2026 national policy, checked
CMS finalized CY 2026 Physician Fee Schedule policy effective January 1, 2026. CMS currently describes Medicare RPM as connected-device monitoring for acute or chronic conditions, with digitally uploaded physiologic data and program-specific service requirements. CMS's current fraud-prevention guidance tells providers to furnish all three main RPM components — education/setup, device supply, and treatment management — rather than treating an isolated setup event as a complete monitoring program. The 2026 RPM code set added CPT 99445 and 99470 for lower-day and lower-time monitoring scenarios. CMS's current Medicare RPM guidance also says an ordering physician or other qualified health care provider is not required for RPM services and ordering-provider information is not required on the Medicare claim; do not carry that Medicare claim-field rule into Connecticut Medicaid, an MCO, or an internal clinical protocol without confirming that payer's own ordering, referral, enrollment, and documentation requirements.
This Medicare baseline is national. It does not establish Connecticut Medicaid or MCO coverage, payment, provider eligibility, or billing rules.
September 2026 CMS billing-risk signal
Apply claim-integrity checks before projecting RPM revenue
CMS's Healthcare Fraud Prevention Partnership September 2026 analysis reviewed high-risk RPM/RTM outliers from January 2025 through May 2026 and flagged patterns involving excessive frequency, initial setup without subsequent monitoring, and services billed during inpatient or skilled-nursing-facility stays. These are program-integrity risk signals, not new Connecticut coverage rules. Use them as workflow controls, then apply the state and plan-specific rules above.
CMS HFPP September 2026 RPM/RTM analysis →Quarterly PFS timing safeguard
For a date of service of October 15, 2026, the applicable 2026 Medicare release is October 2026 (RVU26D / PFREV26D). Use the PFS release applicable to the actual date of service, not simply the newest file CMS has posted.
2027 Medicare policy watch · proposal only
Do not apply proposed CY 2027 RPM rules to 2026 dates of service
CMS's CY 2027 Physician Fee Schedule proposed rule would change remote-monitoring operations if finalized, including a separately reportable initiating visit when RPM or RTM begins, an established-patient requirement for RTM, and limits on payment when clinical-staff monitoring work is performed by contractors rather than staff employed by the billing practice. CMS also proposed valuation changes and sought comment on a possible future four-G-code bundled structure. The public comment period closed September 14, 2026; these provisions remain proposals unless CMS adopts them in a final rule. For current Connecticut planning, keep using CY 2026 Medicare requirements plus the state and plan rules above for the actual date of service.
Code families
RPM, CCM, and TCM planning reference
These code families identify the services that should be checked against current Medicare and Connecticut Medicaid rules. Inclusion here does not mean every code is payable by every payer or provider type.
Remote Patient Monitoring
99453 · 99454 · 99445 · 99457 · 99458 · 99470 · 99091
Verify device eligibility, data collection/transmission requirements, treatment-management time, interactive communication, supervision, and billing frequency. For 2026 Medicare planning, 99445 covers the 2-15-day device-supply tier and should not be reported with 99454 for the same monitoring period; verify payer-specific adoption before applying that rule to Medicaid or an MCO.
Chronic Care Management
99490 · 99439 · 99491 · 99437 · 99487 · 99489 · G0506
Verify patient eligibility, initiating-visit and comprehensive care-plan requirements, qualifying clinical staff time, complexity, add-on logic, consent, and overlapping-service rules. Medicare may allow HCPCS G0506 once with a qualifying initiating visit when the billing practitioner personally performs extensive assessment and care planning beyond the usual initiating-visit work; do not assume the same pathway applies to Medicaid or an MCO.
Transitional Care Management
99495 · 99496
Verify discharge eligibility, interactive contact timing, medical decision-making level, face-to-face visit timing, and payer-specific post-discharge requirements.
From reimbursement to implementation
Connect policy assumptions to a practical N9+ care workflow
Dr. Miltie can help organizations evaluate where remote physical examination, virtual clinician access, funding strategy, and reimbursement-supported care models fit together.