Population Identification
Roster ingestion, diagnosis and risk filtering, payer segmentation, exclusion logic and provider attribution.
Best for:Groups that need a reliable, prioritized enrollment pool.
Select individual modules or deploy an end-to-end service spanning patient identification, enrollment, devices, monitoring, documentation and revenue-cycle support.
InstaMD can support technology-only, shared-services or fully managed delivery. Clinical and billing responsibilities are assigned in the implementation plan.
Roster ingestion, diagnosis and risk filtering, payer segmentation, exclusion logic and provider attribution.
Best for:Groups that need a reliable, prioritized enrollment pool.
Coverage verification, patient outreach, program education, consent capture and ordering workflow.
Best for:Practices seeking consistent patient qualification and conversion.
Device selection, cellular activation, shipping, setup, replacement, troubleshooting and inventory management.
Best for:RPM programs requiring scalable national logistics.
Reading review, threshold queues, adherence outreach, interactive communication, escalation and closure documentation.
Best for:Organizations needing clinical capacity and standardized response workflows.
Device-day counts, cumulative time, communication records, care-plan linkage and exception reporting.
Best for:Billing teams that need auditable, code-specific evidence.
Charge preparation, claim submission support, denial workflow, reconciliation and performance reporting.
Best for:Programs seeking visibility from service delivery through payment.
Effective January 1, 2026, the RPM family includes lower data-day and lower treatment-management time pathways. Code selection must reflect the actual service furnished during the billing period.
99490 · 99439 · 99487 · 99489
Generally two or more chronic conditions expected to last at least 12 months or until death that place the patient at significant risk of death, acute exacerbation, functional decline or decompensation.
Eligible billing practitioner with a comprehensive care plan, consent, continuity, access and care-coordination processes.
InstaMD’s supported CCM workflow emphasizes clinical-staff and complex-care pathways shown above; final code selection remains the billing practitioner’s responsibility.
99424 · 99425 · 99426 · 99427
One serious, high-risk chronic condition expected to last at least three months and requiring development, monitoring or revision of a disease-specific care plan.
Practitioner responsible for the condition, supported where permitted by clinical staff and a condition-focused care process.
98975 · 98976–98978 · 98980 · 98981
Patient needs monitoring of therapeutic response, adherence or function using the applicable device and data category.
Qualified practitioner whose scope and treatment relationship support the monitored therapy and required management services.
99495 · 99496
Eligible discharge from a qualifying setting to a community setting with need for timely communication, medication reconciliation and medical decision-making.
Practitioner assuming transition responsibility and able to complete required contact, face-to-face visit and complexity elements.
Concurrent billing may be possible, but it is never automatic. Each service must independently satisfy medical necessity, code instructions and payer policy.
Maintain separate objectives, activities and time records. Device data review and RPM interactive management cannot be reused as CCM or PCM time.
Do not operate or bill RPM and RTM concurrently for the same patient during the same monitoring period. Select the single pathway that matches the data being monitored and the clinical purpose, document the transition when changing programs, and verify current payer rules.
Evaluate bundling and same-period restrictions. Do not duplicate transition work, communication or medical decision-making.
Define ordering, treatment, supervision and billing ownership. Prevent duplicate claims for overlapping services and periods.