CMS Interactive Communication Requirement for RPM: What Counts and What Doesn\u2019t

What CMS means by \u201cinteractive communication\u201d

CMS defines interactive communication in the Medicare Physician Fee Schedule for CPT 99457 and 99458 as real-time, two-way engagement between clinical staff and the patient or caregiver that discusses physiologic data from a monitoring device, current symptoms, medication adherence, or the patient\u2019s care plan. The definition is deliberately technology-agnostic: CMS does not prescribe a specific communication platform, device, or staff role. What matters is the structure and content of the exchange, not the channel through which it occurs.

This technology neutrality is meaningful in practice. It means that a telephone call with an AI-powered system, a video visit, a live portal chat session, or a face-to-face conversation can all qualify as interactive communication \u2014 as long as the exchange is real-time, two-way, and clinically substantive. Providers designing Remote Patient Monitoring programs have latitude to choose the modality that best fits their patient population, workflow, and scale requirements.

The two-way requirement is the most commonly misunderstood aspect. Interactive communication is not a monologue. The patient or caregiver must actively participate \u2014 responding to clinical questions, reporting symptoms, confirming medication adherence, or signaling concerns. A staff member who leaves a detailed voicemail about blood pressure trends has not engaged in interactive communication in the CMS sense because the patient has not responded in real time. This distinction separates billable interactions from the many outreach attempts that do not satisfy the requirement.

Real-time vs. asynchronous

\u201cReal-time\u201d in the CMS context means both parties are engaged simultaneously during the same interaction. A telephone call, a video visit, and a live portal chat session where the patient and staff member are both active at the same moment all qualify as real-time. Asynchronous exchanges \u2014 email messages sent and read hours apart, patient portal messages with delayed responses, or care summaries sent to the patient without a response \u2014 do not qualify without a real-time component.

Device data review is the clearest example of asynchronous activity that does not satisfy the interactive communication requirement. When clinical staff review blood pressure readings, weight trends, or glucose logs that a device uploaded overnight, that review happens hours or days after the data was generated. It is a clinically valuable activity \u2014 and CMS separately reimburses it under CPT 99091 for some workflows \u2014 but it does not accumulate toward the 20-minute interactive communication threshold that drives CPT 99457 and 99458 billing.

Practices that conflate data review time with interactive communication time in a single undifferentiated note create audit risk. If a documentation entry says \u201creviewed device data and spoke with patient for 20 minutes\u201d without differentiating the time spent on each, an auditor cannot confirm that the full 20 minutes was interactive. Best practice is to document each activity type separately with its own time entry.

Valid contact forms

CMS accepts any modality that supports real-time two-way clinical exchange. The following contact forms satisfy the interactive communication requirement when the content addresses the patient\u2019s physiologic data, symptoms, or care plan:

• Live telephone call with patient or authorized caregiver responding in real time
• Live video visit (including telehealth platforms compliant with applicable CMS rules)
• Secure messaging with two-way real-time exchange (patient portal chat with both parties active simultaneously)
• Face-to-face visit in the office or clinical setting (though this time is typically captured under the Evaluation and Management code for that encounter)

AI-powered telephone calls are an increasingly common modality in large-scale RPM programs. An AI call qualifies when it asks structured clinical questions, captures patient responses in real time, time-stamps the interaction, and escalates concerns to human clinical staff when warranted. The call must be genuinely two-way \u2014 the patient responds to questions rather than simply listening \u2014 and the content must address clinical status. Generic wellness check-ins that do not touch physiologic data, symptoms, medication, or care plan do not meet the clinical content standard.

What doesn\u2019t count alone

The following activities do not satisfy the CMS interactive communication requirement by themselves, regardless of how much clinical effort they represent:

• Voicemail left without a patient callback or real-time response during the same interaction
• One-way automated reminders or alerts (e.g., \u201cplease take your blood pressure medication\u201d or threshold-triggered device alerts pushed to the patient without response)
• Email without a real-time responsive reply from the patient during the same session
• General mass communications or bulk outreach not specific to the individual patient\u2019s clinical status
• Asynchronous data review by clinical staff, which is separately billable under CPT 99091 when applicable but does not count toward the 99457/99458 interactive communication threshold

It is worth emphasizing that these activities are not without value \u2014 many are essential parts of an RPM workflow. The key is accurate coding. Voicemail attempts and device alert reviews do not belong in the cumulative minute count for CPT 99457. Including them inflates the reported interaction time and creates over-billing risk. A clean documentation practice keeps interactive minutes separate from all other clinical activities in the RPM workflow.

The clinical content requirement

Real-time and two-way are necessary conditions for interactive communication under CMS\u2019s definition, but they are not sufficient on their own. The interaction must also be clinically meaningful: it must address the patient\u2019s physiologic data, current symptoms, medication adherence, or care plan. A 20-minute conversation between a patient and a nurse that covers only general topics \u2014 family updates, weather, appointment logistics \u2014 does not satisfy the interactive communication requirement, even if it is genuinely two-way and occurs in real time.

Best practice is to design every interaction around a structured clinical protocol that ensures the required content is covered. Protocols typically begin with a review of recent device data (blood pressure trends, weight changes, oxygen saturation), move to symptom assessment (any new or worsening symptoms since the last contact), check medication adherence, and close with care plan review or adjustment. This structure makes the clinical content of the interaction explicit and easy to document.

Documentation should capture the clinical content of each interaction in enough detail to demonstrate that the conversation addressed the required subject matter. A note that says \u201ccalled patient, no issues\u201d provides little audit protection. A note that says \u201creviewed blood pressure readings from the past 7 days with patient; patient reports no headaches or dizziness; medication adherence confirmed; no care plan changes at this time\u201d clearly satisfies the content requirement. Escalations or care plan changes identified during the interaction should always be documented inline.

How AI-powered calls satisfy the requirement

AI-powered wellness calls satisfy the CMS interactive communication requirement when they are built around a structured clinical protocol. The call asks targeted questions about medication adherence, current symptoms, device readings such as blood pressure, weight, glucose, or oxygen saturation, and functional wellness indicators. The patient\u2019s responses are captured and time-stamped in real time. When a response indicates a clinical concern \u2014 a symptom threshold crossed, a missed medication, or a patient-reported problem \u2014 the system escalates to human clinical staff immediately rather than queuing the alert for later review.

CMS defines the interactive communication requirement by content and structure, not by who conducts the call. An AI call that captures clinical content in a real-time two-way exchange meets the same standard as a call conducted by a nurse or medical assistant. For a detailed explanation of the billing codes the interactive communication requirement underpins, see the CPT 99457 billing guide. For an overview of how Positive Check structures AI-powered calls within a complete Remote Patient Monitoring program, see the RPM solution overview.

The documentation advantage of AI calls is significant at scale. Every AI-powered interaction produces a consistent structured record: date, start and end time, cumulative duration, clinical content summary, patient responses, and any escalations triggered. This output maps directly to the documentation fields required for CPT 99457 and 99458 billing without relying on staff to produce contemporaneous notes of uniform quality. Providers who have deployed AI-driven RPM engagement consistently report that documentation consistency and audit readiness improve substantially compared to staff-managed call programs at equivalent patient volumes. See the scaling patient engagement case study for a deployment example.

Documentation standards

Every interactive communication must be documented in a way that allows an auditor to confirm that the billable requirements were met. CMS auditors reviewing CPT 99457 and 99458 claims look for specific elements. Missing any one of them \u2014 most commonly the staff or system identifier or a clear record of cumulative minutes \u2014 can result in claim denial or post-payment recoupment. The required documentation elements for each interactive communication are:

• Date and time of the interaction
• Method (telephone, video, portal chat, in-person)
• Duration of the interaction, with cumulative running total for the calendar month supporting the 99457 and 99458 thresholds
• Content summary: medication discussion, symptom assessment, device data reviewed, care plan changes or confirmations
• Staff member name or AI system identifier that performed the interaction
• Any escalations, follow-up actions, or care plan adjustments made as a result of the interaction

The cumulative minute total is the single most important operational metric in an RPM program because it directly determines which billing codes are billable in any given month. A per-patient time log that accumulates across every interaction in the calendar month \u2014 updated after each contact \u2014 is the foundation of compliant RPM billing. Programs that rely on staff to manually reconstruct cumulative totals at month-end frequently encounter errors in both directions: over-billing for patients who fell short of the threshold, and under-billing for patients who exceeded one or two add-on thresholds without anyone noticing.

Handling unreachable patients

When a patient does not answer calls or respond to messages, the interactive communication requirement cannot be satisfied for that month, and CPT 99457 is not billable. Programs that bill 99457 for months with only unanswered outreach attempts are a common audit finding. The correct response to an unreachable patient is documentation, not billing.

Documentation of every outreach attempt is important for two reasons. First, it demonstrates that the program made good-faith efforts to reach the patient, which is relevant context if the program is later audited across multiple months. Second, it creates a record that may support re-enrollment or care coordination decisions \u2014 a patient who has been unreachable for multiple months may need a higher-level intervention. Document each attempt with the date, time, method used (telephone, portal message), and outcome (no answer, voicemail left, message sent with no reply). Multiple attempts across different modalities within the month are recommended practice.

CMS permits authorized caregiver contact as an alternative when the patient is unable to respond directly \u2014 for example, a patient with cognitive impairment whose family member manages their care. When caregiver contact is used, the caregiver\u2019s relationship to the patient must be documented, and the interaction content must still address the patient\u2019s clinical status in a clinically meaningful way. See the RPM FAQ for more on caregiver contacts and other common RPM compliance questions.

Common questions