Overview: The Care Management Program Landscape

Medicare's care management programs represent one of the most significant shifts in healthcare payment in the past decade. They move reimbursement away from the traditional fee-for-service model — which pays for procedures and visits — toward a model that rewards ongoing, proactive patient management.

For healthcare organizations, these programs create a compelling opportunity: generate recurring monthly revenue for the care coordination work that good practices are already doing, while building the infrastructure for value-based care success.

The programs covered in this guide:

- Chronic Care Management (CCM) — the foundational care management program for patients with multiple chronic conditions - Advanced Primary Care Management (APCM) — a primary care-focused evolution of CCM with complexity-based billing - Remote Patient Monitoring (RPM) — continuous monitoring of physiological data via connected devices - Behavioral Health Integration (BHI) — integrated behavioral health services within primary care - Remote Therapeutic Monitoring (RTM) — monitoring of therapeutic response for musculoskeletal and respiratory conditions - Principal Illness Navigation (PIN) — patient navigation for serious illness and complex chronic conditions - Community Health Integration (CHI) — community health worker services addressing social determinants of health

Each program has specific eligibility criteria, documentation requirements, billing rules, and operational considerations. This guide provides an educational overview of each program. Always verify current CMS guidelines and consult with a qualified healthcare compliance professional before implementing billing for any care management program.

Chronic Care Management (CCM)

Chronic Care Management is the foundational Medicare care management program. It reimburses providers for at least 20 minutes per month of non-face-to-face care management services for patients with two or more chronic conditions expected to last at least 12 months or until death.

Clinical purpose:

CCM supports patients with complex chronic conditions — diabetes, heart failure, COPD, hypertension, depression, and others — by providing structured, ongoing management between office visits. The program covers care planning, medication management, care coordination, and 24/7 patient access to a care team member.

Appropriate use cases:

CCM is appropriate for Medicare patients with two or more qualifying chronic conditions who would benefit from structured care management. Practices with large panels of complex chronic disease patients — primary care, internal medicine, geriatrics, cardiology — are typically the best candidates for CCM implementation.

Operational workflow:

Successful CCM implementation requires: patient identification and enrollment (with documented consent), comprehensive care plan development, monthly care management activities meeting minimum time thresholds, documentation of all care management activities, and compliant billing.

Documentation considerations:

CCM documentation must capture: patient consent, the comprehensive care plan, time spent on care management activities (minimum 20 minutes per month for standard CCM), the nature of care management services provided, and any care coordination communications. Time must be documented contemporaneously.

For detailed billing codes, reimbursement rates, and implementation guidance, see the Knowledge Center — the CCM infographic (Vol. 3) provides a comprehensive visual reference.

Advanced Primary Care Management (APCM)

Advanced Primary Care Management is a newer Medicare program designed specifically for primary care practices. It builds on the CCM framework with a complexity-based billing structure that better reflects the actual work of primary care management.

Clinical purpose:

APCM supports the primary care relationship as the foundation of coordinated, patient-centered care. It reimburses primary care practices for the ongoing management of Medicare patients with chronic conditions, with billing tiers based on the complexity of the patient's conditions.

Key differences from CCM:

APCM is specifically for primary care practices and uses a different billing structure than CCM. The program is designed to support the shift toward advanced primary care — practices that provide comprehensive, coordinated, accessible care as the foundation of the healthcare system.

Operational workflow:

APCM implementation follows a similar workflow to CCM — patient identification, enrollment with consent, care plan development, monthly care management activities, documentation, and billing. The key operational difference is the complexity-based billing tier determination.

For detailed eligibility criteria, CPT codes, and implementation strategies, see the Knowledge Center — the APCM infographic (Vol. 1) provides a comprehensive visual reference.

Remote Patient Monitoring (RPM)

Remote Patient Monitoring is a Medicare-reimbursed service that allows healthcare providers to monitor patients' physiological data — blood pressure, blood glucose, weight, oxygen saturation, and other vitals — using connected devices in the patient's home.

Clinical purpose:

RPM transforms episodic care into continuous monitoring. Instead of waiting for a patient's next office visit to identify a deteriorating condition, RPM enables providers to detect trends in real time and intervene before a crisis occurs. For patients with hypertension, diabetes, heart failure, and other conditions where physiological monitoring is clinically meaningful, RPM can significantly improve outcomes.

Appropriate use cases:

RPM is appropriate for patients with conditions that benefit from ongoing physiological monitoring — hypertension, diabetes, heart failure, COPD, obesity, and others. Practices with large panels of these patients, and the operational capacity to review monitoring data and respond to alerts, are strong candidates for RPM.

Operational workflow:

RPM implementation requires: device selection and procurement, patient enrollment and device setup, data review workflows (minimum 16 days of data per month for billing), clinical response protocols for out-of-range values, and compliant billing documentation.

Documentation considerations:

RPM documentation must capture: patient consent, device setup and education, days of data transmission, time spent reviewing data and communicating with patients, and clinical responses to monitoring data.

For detailed billing codes, device requirements, and implementation guidance, see the Knowledge Center — the RPM infographic (Vol. 2) provides a comprehensive visual reference.

Behavioral Health Integration (BHI)

Behavioral Health Integration is a Medicare program that reimburses primary care practices for integrating behavioral health services into primary care. It recognizes that mental health and substance use conditions are among the most prevalent and undertreated conditions in primary care settings.

Clinical purpose:

BHI supports the integration of behavioral health screening, assessment, care planning, and treatment into primary care — using a collaborative care model that includes the primary care provider, a behavioral health care manager, and a consulting psychiatrist.

Appropriate use cases:

BHI is appropriate for primary care practices that serve patients with depression, anxiety, substance use disorders, and other behavioral health conditions. The program is designed to improve access to behavioral health care by embedding it in the primary care setting where most patients already receive care.

Operational workflow:

BHI implementation requires: a designated behavioral health care manager (typically a social worker, counselor, or nurse), a consulting psychiatrist relationship, systematic behavioral health screening, a registry to track patient outcomes, and structured care management activities.

Documentation considerations:

BHI documentation must capture: behavioral health screening results, care plan elements, care manager activities and time, psychiatric consultation, and patient outcomes on validated measurement tools.

For detailed implementation guidance, see the Knowledge Center — the BHI infographic (Vol. 5) provides a comprehensive visual reference.

Remote Therapeutic Monitoring (RTM)

Remote Therapeutic Monitoring is a Medicare program that reimburses for the monitoring of therapeutic response to treatment for musculoskeletal and respiratory conditions. It is distinct from RPM in that it monitors therapeutic data (pain, function, adherence) rather than physiological data (vitals).

Clinical purpose:

RTM supports the ongoing management of patients with musculoskeletal conditions (back pain, joint conditions, post-surgical recovery) and respiratory conditions (asthma, COPD) by monitoring their response to treatment and adherence to therapeutic programs between office visits.

Appropriate use cases:

RTM is appropriate for orthopedic practices, physical therapy practices, pulmonology practices, and primary care practices managing patients with musculoskeletal and respiratory conditions. It is particularly valuable for post-surgical patients and patients in rehabilitation programs.

Operational workflow:

RTM implementation requires: patient enrollment and device/app setup, data collection on therapeutic response and adherence, regular data review, clinical response to concerning trends, and compliant billing documentation.

For detailed billing codes and implementation guidance, see the Knowledge Center — the RTM infographic (Vol. 15) provides a comprehensive visual reference.

Principal Illness Navigation (PIN)

Principal Illness Navigation is a newer Medicare program that reimburses for patient navigation services for patients with serious illness or complex chronic conditions. It recognizes that patients facing serious illness — cancer, heart failure, advanced COPD, end-stage renal disease, and others — face unique navigation challenges that require dedicated support.

Clinical purpose:

PIN supports patients in navigating the healthcare system during serious illness — helping them understand their diagnoses, access appropriate specialists, coordinate care across multiple providers, connect to community resources, and adhere to complex care plans. The program is designed to reduce the burden on patients and families during the most challenging periods of their healthcare journey.

Appropriate use cases:

PIN is appropriate for practices serving patients with serious illness or complex chronic conditions who face significant navigation challenges. Oncology practices, cardiology practices, nephrology practices, and primary care practices with high-complexity patient panels are strong candidates.

Operational workflow:

PIN implementation requires: identification of eligible patients, enrollment with consent, assignment to a qualified navigator, structured navigation activities meeting minimum time thresholds, documentation of navigation activities, and compliant billing.

Documentation considerations:

PIN documentation must capture: patient consent, the nature of navigation services provided, time spent on navigation activities, and outcomes of navigation interventions (appointments scheduled, resources connected, care plan adherence).

Community Health Integration (CHI)

Community Health Integration is a Medicare program that reimburses for community health worker services addressing social determinants of health — the non-clinical factors that profoundly affect health outcomes, including housing instability, food insecurity, transportation barriers, social isolation, and financial stress.

Clinical purpose:

CHI recognizes that clinical care alone cannot address the full range of factors that determine health outcomes. Community health workers serve as bridges between healthcare organizations and the communities they serve — connecting patients to social services, community resources, and support systems that address the root causes of poor health.

Appropriate use cases:

CHI is appropriate for practices serving populations with significant social needs — federally qualified health centers, safety-net practices, practices in underserved communities, and any practice whose patient population faces significant social determinants of health challenges.

Operational workflow:

CHI implementation requires: identification of patients with social needs (typically through systematic screening), enrollment with consent, assignment to a qualified community health worker, structured community health worker activities, documentation, and compliant billing.

The broader significance of CHI:

CHI represents a significant expansion of Medicare's recognition that health is shaped by social and economic factors, not just clinical ones. Organizations that build CHI programs are positioning themselves at the forefront of a broader shift toward whole-person care — and building relationships with the communities they serve that extend far beyond the clinical encounter.

Implementing Care Management Programs: The AJ Pakpour Approach

Implementing care management programs successfully requires more than understanding the billing rules. It requires building the operational infrastructure — workflows, staff roles, documentation systems, quality metrics, and compliance frameworks — that makes programs sustainable and scalable.

The implementation framework:

Assessment begins with understanding your patient population, your current operational capacity, and which programs are the best fit for your practice. Not every program is right for every practice. The right starting point depends on your patient panel, your staff capabilities, your technology infrastructure, and your compliance readiness.

Design translates program requirements into specific workflows, role descriptions, documentation templates, and quality metrics. This is where most implementation failures occur — organizations understand the program requirements but do not translate them into operational reality.

Training ensures that every team member understands their role, the documentation requirements, and the compliance obligations. Training is not a one-time event — it is an ongoing process that adapts as programs evolve and staff changes.

Launch implements the designed workflows with a defined patient cohort, monitors performance closely, and makes rapid adjustments based on early results.

Scale expands the program systematically as operational confidence grows, maintaining quality and compliance as volume increases.

AJ Pakpour works with healthcare organizations at every stage of this process — from initial assessment through sustainable scale. The goal is not just to launch a program, but to build the infrastructure for long-term success.