A practice may already know which patients would benefit from more support between visits. The harder question is whether their Medicaid coverage supports the service the practice plans to deliver. That answer requires more than finding the state on a list of places that reimburse for telehealth.
Medicaid can cover remote patient monitoring and chronic care-management services, but there is no single national coverage rule for CCM and RPM. Payment depends on the state, the patient’s Medicaid program or managed care plan, the service, and the billing provider. Practices should verify CCM and RPM separately, including eligible patients, payable codes, authorization requirements, and restrictions on overlapping services.
At 1bios, our approach starts with a simple idea: You already have the patients. We bring the operation. For a practice serving Medicaid patients, that operation needs to reflect the coverage arrangements that actually apply to its panel. Patient outreach, care delivery, documentation, and billing handoffs should follow a verified program design.
Medicaid operates within federal requirements, but states have substantial flexibility in how they cover and reimburse services delivered through telehealth. That flexibility includes decisions about covered services, eligible providers, and payment methods. CMS explains these distinctions in its guidance on Medicaid telehealth reimbursement and provider requirements.
The practical result is that “Medicaid covers RPM” may describe several different arrangements. One state may reimburse eligible practitioners for remote physiologic monitoring, while another offers a more restricted home telemonitoring benefit. Coverage may also depend on a particular diagnosis, provider category, or managed care arrangement.
For your practice, the useful question is more specific: Does this patient’s coverage reimburse this service when delivered and billed by our organization? Record the answer for the relevant plan, provider type, and date of service. A general statement about statewide telehealth access cannot answer all three.
Medicaid coverage for chronic care management requires a distinction between care-management services and separately payable CCM billing codes. A program may coordinate care for people with chronic conditions without using the same payment structure as Medicare CCM. Before building a monthly CCM billing workflow, confirm which service and payment arrangement the patient’s Medicaid coverage supports.
For example, Medicaid health homes provide services such as comprehensive care management, care coordination, and transitional care. These services operate through state-approved programs with their own participation and payment arrangements. A health-home benefit should therefore not be treated as proof that an independent practice can separately bill a particular CCM code.
The verification should identify the precise code, eligible billing provider, documentation requirements, and any restrictions involving other care-management services. Ask whether the work is paid separately or included in another payment arrangement. Save the applicable policy and any written payer clarification with the practice’s billing instructions.
Medicaid can cover RPM, but the benefit’s scope matters as much as its availability. CMS includes remote patient monitoring within its description of technologies used to deliver Medicaid telehealth services. States then establish the applicable coverage and reimbursement arrangements within federal requirements.
A covered monitoring benefit may have separate rules for patient eligibility, devices, provider participation, treatment management, and authorization. The state may also distinguish home health monitoring from services billed by a physician practice. Confirm which category applies before choosing devices or building the enrollment workflow.
Device coverage also needs its own review. A plan’s coverage of a blood pressure monitor or continuous glucose monitor does not, by itself, establish payment for every associated monitoring and management service. Match the equipment, clinical work, and proposed billing to the applicable policy.
The state entries below distinguish documented RPM coverage pathways from questions that remain unresolved. They also identify whether the reviewed sources establish separate physician-practice CCM payment. “Not confirmed” means the available evidence did not settle the question; it does not mean the service is excluded.
Some identified pathways are limited to home-health agencies, health homes, particular clinics, or a named managed-care plan. Separate physician-practice CCM payment remains unresolved across much of this directory, so the entries should not be read as a completed determination of CCM coverage in every state. Each practice still needs to match the patient’s benefit, its own provider enrollment, and the intended service to the applicable payment rules.
Alabama has an RPM pathway through the Alabama Department of Public Health, Medicaid, and the University of South Alabama for qualifying patients with conditions including diabetes, hypertension, and congestive heart failure. The ADPH program description does not establish that every physician practice can independently bill the standard RPM code family. Separate physician-practice CCM coverage was not confirmed in this review, so practices should verify CCM independently from eligibility for this RPM program.
Alaska's published RPM coverage proposal is explicitly labeled a draft. It should not be used as proof that the proposed patient criteria or billing arrangements are in effect. This review did not establish current, separately billable physician-practice RPM or CCM coverage, so obtain an effective coverage policy and code-level confirmation before building either service into projected Medicaid revenue.
Arizona's AHCCCS telehealth policy includes remote patient monitoring within its coverage framework for contractors and fee-for-service programs. Practices should match the proposed service and equipment to the applicable covered benefits and telehealth code set rather than assume all RPM components are payable. This RPM policy does not establish separate CCM payment, which needs its own code and contract review.
This review did not establish a statewide, separately billable physician-practice RPM or CCM benefit in Arkansas. Proposed changes and program-specific services should be checked against the applicable Arkansas Medicaid provider manual and the patient's coverage arrangement. A draft Medicaid systems review is background material, not sufficient authority for a coverage or billing decision.
California's Medi-Cal telehealth guidance identifies RPM coverage in fee-for-service and managed care, subject to patient, ordering-provider, and service requirements. Practices should verify the relevant benefit scope and billing instructions, including any age-specific pathway, before enrollment. CCM requires a separate determination, and Medi-Cal Enhanced Care Management should not be treated as interchangeable with physician-billed CCM.
Colorado expanded its RPM benefit effective July 1, 2025, as described in its provider bulletin. The expansion does not remove the need to match the patient's condition, provider type, and service components to current Health First Colorado billing rules. Separate CCM coverage was not confirmed in this review and should not be inferred from the RPM expansion.
Connecticut practices should use the Connecticut Medical Assistance Program's provider resources to verify the specific CCM and RPM codes they intend to bill. This review did not establish a general, separately billable benefit for either service. Telehealth coverage, collaborative care coverage, or a grant supporting remote monitoring does not by itself answer whether a practice's CCM or RPM claim is payable.
Delaware's practitioner manual includes RPM criteria for patients with unstable or uncontrolled conditions requiring frequent monitoring. Eligibility also involves practical considerations such as the patient's ability to participate, caregiver assistance where needed, and a suitable home environment. The RPM provisions do not settle separate CCM coverage, so verify that service with Delaware Medicaid or the patient's managed-care plan.
The District's January 2023 telemedicine guidance explicitly lists RPM among excluded services. Practices should check for a later implementing policy or an applicable separate benefit before treating RPM as reimbursable, rather than relying solely on legislation authorizing telehealth. This exclusion does not determine CCM coverage, which was not independently confirmed in this review.
Aetna Better Health of Florida's post-public-health-emergency guidance states that RPM continues after the emergency flexibilities ended. This is useful evidence for that plan, but practices should obtain the current code, provider, and authorization rules for the patient's actual Florida Medicaid coverage. Separate CCM reimbursement was not established by that guidance and needs its own verification.
Georgia's general telehealth coverage should not be read as automatic coverage of monthly RPM services. Use the current manuals and fee information in the Georgia Medicaid provider portal to verify each RPM and CCM code, together with the patient's managed-care policy where applicable. This review did not confirm a general physician-practice RPM benefit or current separate CCM payment.
Hawaii practices should verify CCM and RPM under the patient's specific QUEST Integration plan rather than rely on a broad telehealth definition. A plan's provider manual, such as the 2026 'Ohana QUEST manual, is a starting point for that review. This research did not establish a statewide, separately billable physician-practice benefit for either service, so request code-specific confirmation before forecasting collections.
Idaho's Medicaid basic-plan rules make an exception for remote monitoring within their treatment of asynchronous services. The applicable provider handbook and code rules still determine which services are payable and under what circumstances. CCM requires a separate benefit review, and the RPM provision should not be used to establish CCM coverage.
Illinois has published coverage instructions for remote fetal nonstress testing under fee-for-service and managed care. That specific service should not be presented as proof that the full physiologic RPM code family is covered for other conditions. General physician-practice RPM coverage and separate CCM payment were not established in this review and need code-level verification.
Indiana's Telehealth and Virtual Services module describes a shared RPM coverage and authorization framework for fee-for-service and managed care. Practices should review the current covered-code list, authorization requirements, prescriber's order, and plan-of-care documentation, while home-health agencies must follow their own billing instructions. Separate CCM coverage was not established by this RPM policy and should be verified independently.
Iowa illustrates why a code's appearance in Medicaid documents does not always establish standard physician-practice CCM coverage. An approved Iowa state plan amendment uses 99490 within an integrated health-home payment arrangement. Practices should verify whether they qualify for that arrangement or a separate CCM benefit, and this review did not establish a general physiologic RPM benefit.
Kansas has been identified in policy research as offering home telehealth through specific service arrangements, but this review did not complete primary-source verification of the current benefit. Practices should obtain the applicable KMAP home-health or waiver manual and confirm which organization is permitted to furnish and bill the service. Until that review is complete, neither general physician-practice RPM payment nor separate CCM reimbursement should be represented here as confirmed.
Kentucky's telehealth regulation establishes RPM coverage with patient, ordering-provider, and furnishing-provider requirements. Its eligibility rules distinguish pregnancy-related participation from other qualifying conditions, for which additional risk factors apply. The regulation does not by itself resolve separate CCM reimbursement, so practices should verify CCM codes and applicable managed-care requirements independently.
Louisiana has an RPM pathway documented in an approved Healthy Blue in-lieu-of-service policy. That finding should be described as plan-specific rather than extended to all Louisiana Medicaid members or every practice. Separate CCM coverage was not established by this policy, and participation, authorization, and billing arrangements require confirmation with the responsible payer.
MaineCare's telehealth rule covers telemonitoring through certified home-health agencies for members meeting its eligibility requirements. The rule uses a bundled monthly telemonitoring payment and requires supporting documentation in the plan of care before services begin. This home-health benefit does not establish independent physician-practice RPM or separate CCM reimbursement.
Maryland's RPM regulations set out provider qualifications, patient eligibility, covered services, and authorization requirements. Practices should establish that the patient and furnishing organization meet those requirements before treating RPM as billable. Separate CCM coverage was not confirmed in this review and should be evaluated independently of the RPM benefit.
MassHealth's physician bulletin on RPM establishes coverage subject to specified conditions and billing instructions. Practices should confirm that their provider type and claim format fit those instructions rather than assume that professional and facility billing are interchangeable. CCM payment requires a separate, setting-specific review, especially when comparing independent physician practices with community health centers.
Michigan's Medicaid telemedicine policy includes RPM for qualifying acute and chronic conditions, with requirements addressing the device and patient instruction. Practices should use the current Michigan telemedicine resources and code information to check the components they intend to furnish and bill. The RPM policy does not establish separate CCM coverage, which remains a distinct code and payer verification task.
Minnesota's physician-services guidance includes RPM for specified clinical circumstances rather than unrestricted use for every diagnosis. Practices should consult the Minnesota Health Care Programs physician-services manual for patient criteria and billing limits. Separate physician-billed CCM was not confirmed in this review, and a care-coordination payment arrangement should not automatically be treated as the same benefit.
Mississippi's telemedicine administrative code includes RPM as a distinct service with its own coverage requirements. Practices should verify the applicable eligibility, authorization, device, and documentation provisions against any later policy updates before enrollment. Separate CCM payment was not established by this RPM rule and should be checked independently.
Missouri law provides for home telemonitoring subject to specified conditions, including implementation and funding provisions. The statute alone does not establish which RPM services an independent practice may currently bill or how it must enroll. This review did not resolve current physician-practice RPM implementation or separate CCM reimbursement, so both require operational confirmation from MO HealthNet or the responsible plan.
Montana's Medicaid telehealth statute provides a framework for covered services delivered remotely. It does not by itself establish that every monthly RPM or CCM code is separately payable to a physician practice. This review did not confirm either benefit at that level, so use current provider manuals and code-specific payment information before including them in a program budget.
Nebraska requires a fresh policy check because a reported 2026 RPM expansion may supersede older summaries stating that coverage is unavailable. Obtain Provider Bulletin 26-04 through the Nebraska Medicaid bulletin service and confirm its effective date, qualifying patients, and covered codes before relying on the expansion. The original bulletin could not be verified directly in this review, and separate CCM coverage also remains unconfirmed.
Nevada's managed-care workshop materials discuss exploring or encouraging RPM. That discussion is not an implemented coverage policy and should not be used to claim that RPM is payable. This review did not verify current physician-practice RPM or separate CCM coverage from an operative primary source, so check the applicable Medicaid services manual and plan policy.
New Hampshire issued a provider notice establishing RPM coverage effective October 1, 2023. Practices should verify the current covered-code list and the patient's fee-for-service or managed-care billing requirements before enrollment. The RPM notice does not establish separate CCM payment, which needs an independent benefit review.
New Jersey practices should distinguish enacted and implemented benefits from proposed legislation concerning RPM. For example, Assembly Bill 2201 is not sufficient on its own to establish current Medicaid payment. This review did not verify a general physician-practice RPM benefit or separate CCM coverage, so confirm the patient's NJ FamilyCare plan policy and any applicable program-specific payment arrangement.
New Mexico's professional-services rules address Medicaid services delivered through telemedicine. A general telemedicine provision does not by itself establish separate payment for monthly RPM or CCM. Practices should obtain code-specific confirmation from the responsible Medicaid payer, including whether the proposed work is separately reimbursed or included in another payment arrangement.
New York's March 2026 Medicaid Update describes changes to RPM coding, with different implementation dates for fee-for-service and managed care. Practices should also review subsequent telehealth-manual updates for the date of service. Separate physician-practice CCM payment was not established in this review, and New York Health Home services should not be represented as interchangeable with CCM.
North Carolina addresses RPM in Clinical Coverage Policy 1H. Practices should distinguish automated RPM from self-measured services and match the patient, provider, and proposed codes to the policy's requirements. Separate CCM coverage was not confirmed by this RPM policy and needs its own payer and code review.
North Dakota's telehealth policy should not be treated as proof of coverage for every remote-monitoring code. Specific services such as self-measured blood-pressure support require their own review and do not establish the full physiologic RPM benefit. This research did not confirm general physician-practice RPM or separate CCM payment, so verify the intended codes using the state's current coverage resources.
Ohio's FQHC and rural-health-clinic payment rule addresses RPM outside the prospective payment system. That clinic-specific provision should not be generalized into identical billing instructions for every independent physician practice. Practices should verify the applicable provider category and RPM codes, while separate CCM reimbursement remains unconfirmed in this review.
Oklahoma practices should confirm whether each proposed RPM component is a compensable SoonerCare service rather than rely on the availability of telehealth generally. The Oklahoma Health Care Authority's provider resources provide the route to current policies and payment information. This review did not establish a general, separately billable physician-practice RPM or CCM benefit, so obtain a service-specific determination before forecasting revenue.
Oregon practices should check the current Oregon Health Plan guidance and the patient's coordinated care organization before treating RPM as a payable service. The state has discussed RPM in earlier Medicaid advisory materials, but those materials are not a substitute for current coverage instructions. This review did not complete primary-source verification of current physician-practice RPM or separate CCM payment, so both findings remain unresolved.
Pennsylvania's telemedicine guidance describes changes affecting Medical Assistance managed-care coverage. Those broader changes do not, by themselves, establish which RPM codes a particular practice can bill. Current separate RPM and CCM payment should be checked against the patient's delivery system, provider enrollment, and service-specific rules, because this review did not settle those questions.
Rhode Island's telemedicine definitions include remote monitoring, but a definition alone does not establish reimbursement for each RPM component. Practices should review the patient's Medicaid plan policy and obtain confirmation for the intended provider type and codes. This review did not establish general physician-practice RPM or separate CCM coverage, so neither should be assumed from broad telemedicine language.
South Carolina's 2025 telehealth report states that its Medicaid program reimburses providers using RPM hardware and software. The report does not replace service-specific instructions identifying eligible patients, participating providers, and billable components. Practices should confirm the applicable benefit and billing pathway, and separate CCM reimbursement remains unconfirmed in this review.
South Dakota's telemedicine billing manual contains RPM eligibility and documentation requirements. Practices should use the current manual rather than assume that earlier public-health-emergency notices still determine coverage, and FQHCs and rural health clinics should check their specific billing instructions. Separate CCM coverage was not established by this RPM manual and requires independent verification.
Tennessee practices should distinguish general physiologic RPM from specific services such as remote fetal testing. Use current TennCare provider and managed-care communications alongside the patient's plan policy to identify the applicable benefit. This review did not establish general physician-practice RPM or separate CCM payment, and coverage of a particular remote test should not be generalized to either service.
Texas Medicaid has a home-telemonitoring benefit with patient and provider requirements. An approved Texas state plan amendment addresses home telemonitoring for FQHCs and rural health clinics, illustrating why the furnishing organization's enrollment matters. Practices should verify their own billing pathway separately, and this RPM finding does not establish separate CCM reimbursement.
Utah's general Medicaid provider manual has identified RPM among services not reimbursed under its telehealth provisions. Practices should check the latest manual and any applicable separate benefit before relying on an exception or subsequent change. CCM is a separate coverage question and should be verified through the state's code-level resources rather than inferred from this RPM exclusion.
Vermont's adopted telehealth rule describes home telemonitoring for qualifying patients, including specified chronic conditions. Practices should verify the required order, plan of care, and furnishing-provider arrangements before assuming they can bill the service directly. Separate physician-practice CCM coverage was not established by the telemonitoring rule.
Virginia Medicaid covers RPM and has issued updated telehealth instructions addressing the benefit. Practices should use the current guidance rather than rely solely on the original 2022 coverage announcement, particularly when evaluating qualifying clinical circumstances and provider requirements. Separate CCM payment was not confirmed in this review and needs its own fee-for-service or managed-care determination.
Washington's home-health telemedicine rule provides a pathway for qualifying monitoring services under that benefit. Apple Health also operates a Health Home program, but participation in that program is different from billing standard physician-practice CCM. Verify the appropriate provider enrollment and payment arrangement for each service rather than assume either pathway applies to every practice.
West Virginia's practitioner telehealth policy governs covered services delivered through that modality. This review did not establish a separate physician-practice physiologic RPM benefit from that policy, and general telehealth authorization should not be treated as code-level payment confirmation. Separate CCM reimbursement also remains unresolved and should be checked against current Medicaid and plan-specific instructions.
Wisconsin identifies RPM among its Medicaid telehealth services. Practices should use the applicable ForwardHealth instructions to confirm provider qualifications, patient eligibility, covered components, and billing requirements. Separate CCM payment was not established by this general RPM guidance and should be verified independently.
Wyoming practices should verify RPM and CCM against the current CMS-1500 provider manual and code-level payment information. Historic reimbursement comparisons or new grant-funded monitoring initiatives do not establish a current, separately billable physician-practice benefit. This review did not confirm current general RPM or separate CCM coverage, so obtain the applicable policy before using either service in a Medicaid revenue forecast.
Coverage verification should produce an answer the care team and billing team can both use. A general note saying “Medicaid eligible” does not explain whether a particular CCM or RPM service is payable. The record should identify the benefit, the responsible payer, and the conditions the practice must meet.
The following checkpoints are a recommended operational process. Individual requirements come from the applicable state, plan, provider agreement, and service policy. Assign a person to resolve unanswered questions before the practice represents a service as covered.
Start with the patient’s current eligibility record and plan assignment. Identify whether the claim would go to fee-for-service Medicaid, a managed care plan, or another payer under the applicable coordination rules. Repeat the check when coverage changes and at the intervals required by the relevant program.
A patient’s Medicaid card is not a substitute for identifying the service’s billing pathway. Record the plan, member identifier, effective dates, and the source used to verify the benefit. Route disagreements between the eligibility response and the policy to the billing team for resolution.
Describe the work the practice intends to deliver before choosing a billing code. For RPM, that includes the device, data transmission, clinical review, patient communication, and treatment-management activities. For CCM, it includes the covered care-management service, care plan, personnel, documentation, and any applicable time requirements.
Then compare that workflow with the actual policy. If a requirement is unclear, obtain clarification rather than applying a Medicare rule by default. Keep the answer specific to the patient’s plan and the proposed billing provider.
Ask whether the patient already receives relevant care management or monitoring from another organization. Identify the program and payer arrangement rather than assuming that two services with different names cannot overlap. Have the billing team review the applicable restrictions before separate claims are prepared.
Care teams should also distinguish the activities they perform for each service. Documentation needs to show what actually happened and support any allocation of time required by the payer. A single interaction should not become two billable services merely because the patient is enrolled in both programs.
A verified benefit still needs an operating process that can deliver the covered service consistently. Someone must explain participation to the patient, maintain the required records, and identify when circumstances change. For RPM, the process also needs ownership of device activation, missing readings, technical problems, clinical review, and escalation.
Consider a practice enrolling patients from two Medicaid plans. Both plans may support remote monitoring, but the practice should not assume that provider participation, authorization, or billing instructions are identical. The enrollment record should identify which approved workflow applies to each patient.
This affects the choice between internal staffing and a partner-supported model. A practice evaluating in-house and outsourced CCM should define responsibility for payer questions, documentation review, and unresolved billing issues. The same responsibility mapping belongs in an RPM staffing and operating-model decision.
Consider a patient whose Medicaid plan has an RPM benefit and whose clinician recommends monitoring. During enrollment review, the practice identifies an authorization requirement but cannot find an approval in the record. The coordinator assigns the question to the designated authorization owner and records what remains unresolved.
The team should not mark the patient as financially cleared on the strength of the general coverage policy. It should resolve the authorization question and coordinate any necessary clinical care while that review occurs. If approval is received, the team records its effective dates and conditions before completing the applicable enrollment steps.
This example is a recommended operational approach, not a statement that every Medicaid RPM benefit requires authorization. Its purpose is to show how a coverage finding becomes an accountable task. The same approach can be used for an unresolved provider-participation question or a CCM payment restriction.
Build the financial model around verified payment arrangements and expected collections. A Medicare fee schedule, another state’s payment amount, or a vendor’s national reimbursement estimate is not a reliable substitute. Separate fee-for-service patients from managed care arrangements when the payment terms or workload differ.
Include the work needed to maintain coverage records and resolve exceptions. Authorization follow-up, enrollment changes, documentation review, and billing questions use staff time even when they do not produce a separately payable service. Device costs and clinical coverage also continue to matter when a patient does not complete a billable month.
The practice should define what happens when coverage changes during participation. Assign responsibility for reviewing the new arrangement, communicating with the patient, and coordinating continuity of care. Avoid building the program around an assumption that every enrolled patient will generate the same monthly revenue.
A partner discussion should start with the Medicaid programs and patient populations the practice actually serves. Ask which responsibilities the proposed agreement includes and which remain with the practice. Require specific answers about enrollment, clinical communication, documentation, and billing handoffs.
The scope should also explain who investigates coverage questions and who follows up on missing authorizations or rejected claims. Documentation support, claim submission, and denial management are distinct functions. Do not assume that an agreement covering one includes the others.
For 1bios, the conversation starts with the patients your practice already serves and the work required to support them between visits. The operating model should reflect your clinical responsibilities and verified payer arrangements. The agreement should make ownership of that work clear before enrollment begins.
These questions address the distinctions that matter when a practice turns coverage information into an enrollment and billing workflow. Use the answers alongside the relevant state entry and the patient’s current plan instructions. A state-level finding is a starting point for verification, not a determination that a particular claim is payable.
Medicaid may support both services, but coverage must be verified separately. A state or plan’s RPM policy does not establish that a particular CCM code is payable. Check the patient’s coverage, billing provider, service requirements, and restrictions before planning to bill either service.
Practices should not assume that every plan uses identical administrative or billing instructions. A statewide benefit may still require review of the applicable plan’s provider guidance and participation arrangements. Confirm the instructions that apply to the patient and the proposed date of service.
The terms can describe related clinical work, but they do not necessarily describe the same benefit or payment arrangement. Medicaid health homes and other care-management programs have their own participation and reimbursement structures. Confirm whether the practice is delivering a separately payable CCM service or participating in another care-management arrangement.
General telehealth coverage does not, by itself, establish payment for a specific RPM service. The practice must identify the covered monitoring benefit and its provider, patient, technology, and billing requirements. A policy covering video visits should not be used as the sole basis for an RPM claim.
The answer depends on whether both services are covered and whether the applicable billing rules permit the combination. Review concurrent-billing restrictions, existing care-management arrangements, and the documentation supporting each service. Do not count the same work twice or assume that Medicare’s rules automatically apply.
The device and the associated clinical work may fall under different coverage and payment rules. Confirm the equipment benefit as well as the service used to review data and manage the patient’s care. A covered device alone is not enough to establish payment for the entire RPM workflow.
Treat the finding as unresolved rather than concluding that the service is covered or excluded. Review the current provider manual, fee schedule, bulletins, and applicable managed care guidance, then request clarification when necessary. Record the source and effective date of the answer before using it in enrollment or billing instructions.