Stop Chasing Minutes.
Start Building Stable Revenue.

1. If we turn on APCM, how much new revenue are we realistically talking about?

It depends on two levers: the size of your Medicare panel and how many patients land in each APCM tier (G0556, G0557, G0558). In most primary-care groups, 40–70% of the Medicare panel can be enrolled once workflows are in place. G0556 patients (one or no chronic conditions) generate a smaller monthly amount; G0557/G0558 patients (multiple chronic conditions, with or without QMB status) generate more per month.

As a rough pattern, practices that already have basic care-management processes in place see APCM reach meaningful scale in 3–6 months. Early months are lower as you build consent, care plans, and risk tiers; once your panel is fully enrolled, APCM becomes a predictable, non–time-based revenue line tied to your primary-care relationships rather than to how many RPM minutes you can log.

To get out of “hand-waving mode,” we recommend running your actual numbers through the APCM revenue calculator using your Medicare panel size and a conservative estimate of how many patients will qualify for each tier.

2. What would actually change for my staff day-to-day if we add APCM?

APCM doesn’t require your team to become a call center. It formalizes work that already happens between visits and expects you to do it more consistently and document it more clearly. The main day-to-day changes are:

• Structured outreach and follow-up: scheduled check-ins, especially around discharges and high-risk patients, instead of ad hoc calls.
• Care-plan hygiene: keeping a “living” care plan current in the EHR and sharing updates with patients/caregivers.
• Use of non-visit communication: making intentional use of portal messages/phone calls and documenting them as part of APCM rather than “miscellaneous admin.”
• Panel and risk visibility: thinking in terms of “which APCM patients are high-risk and need attention this week,” not just whoever is on the schedule.

With FairPath in place, most of this shows up as a single work queue (who needs outreach, what’s missing for this month’s APCM claim) rather than a collection of spreadsheets and sticky notes. Without a platform, you’re asking staff to track APCM work manually, which is where programs usually stall.

3. We already bill CCM and use an RPM vendor. Do we have to turn those off to start APCM?

No, but you do need to be deliberate about which patients are on which program each month. CMS created APCM to bundle and simplify advanced primary care, not to outlaw CCM or RPM. In practice, most groups do something like:

• Use APCM as the default for Medicare primary-care patients where your clinic is the main “medical home.”
• Reserve CCM/PCM for edge cases where APCM doesn’t quite fit (e.g., specialty-led principal care, legacy arrangements).
• Layer RPM/RTM selectively on top of APCM for specific diagnoses and payers where monitoring is clinically needed and coverage is clear.

What you shouldn’t do is double-bill overlapping care-management work with APCM and CCM/PCM/TCM for the same patient/month. FairPath encodes stacking rules and payer policies so your exports don’t include combinations that are likely to be denied or questioned in an audit; if you’re running everything manually, your billing team has to keep that rulebook in their heads.

4. Do we need more staff to run an APCM program, or can we use the team we have?

Most practices start APCM with their existing team and reframe part of their current nursing/MA workload instead of hiring a new department. The levers are:

• Panel size: a few dozen APCM patients can be handled opportunistically; a few hundred starts to need structured workflows; 500–1,000+ benefits from a dedicated care-management FTE or two.
• How much is automated: if staff are mining the EHR manually and documenting in free text, you’ll feel understaffed quickly. If APCM tasks show up in a queue with templates and checklists, one nurse or MA can handle a surprisingly large APCM panel.
• Mix with existing programs: if you already run CCM and RPM, APCM will replace some bespoke tasks and consolidate others.

FairPath is built so that a small, cross-trained team can manage APCM, RPM, RTM, and CCM together without quadrupling effort: the same workflows and dashboards drive all of them, and the platform keeps track of which work “belongs” to which code.

5. How much EHR or IT work is involved in getting APCM off the ground?

You do not need to rip and replace your EHR. APCM expects you to use certified EHR technology (CEHRT) for quality reporting, but the mechanics can be phased in:

• Phase 1 – Stand up the program: export a patient panel, define consent scripts, and begin documenting APCM work using existing note types/templates.
• Phase 2 – Structure the data: add or refine discrete fields for consent, care-plan status, risk tier, transitions, and after-hours encounters.
• Phase 3 – Align with MVP/ACO reporting: connect APCM patients to your Value in Primary Care MVP or ACO measure set so quality reporting and billing line up.

FairPath sits on top of your EHR as the APCM/RPM command center. You can start by uploading a simple CSV, and over time more of the data will be exchanged through structured interfaces; the goal is to keep your EHR as the clinical source of truth while FairPath orchestrates eligibility, workflows, and billing.

6. Are patients going to be surprised or upset by APCM charges?

APCM is a Part B service, so for most patients standard 20% coinsurance applies after the deductible. Qualified Medicare Beneficiaries (QMBs) and similar high social-risk patients have their cost-sharing covered by other payers and should not be billed directly.

The main drivers of patient satisfaction are:

• How you frame APCM: patients should understand that this is an ongoing primary-care program they are actively enrolled in, not a random line item.
• Whether they feel the benefit: if they experience easier access, more coordinated care, and timely follow-up, they are far less likely to question modest monthly cost-sharing.
• QMB handling: QMBs should never receive “surprise bills.” Your front office and billing team need clear flags and rules so these patients are excluded from balance-collect attempts.

FairPath helps by clearly flagging APCM enrollees and QMBs, generating consent scripts that include cost-sharing language, and giving you a record of what was explained and when--so if questions come up, you’re not relying on memory.

7. What are the biggest APCM compliance risks we should be worried about?

The CMS rule text is long, but the main failure modes are straightforward:

• Weak or missing consent: no clear record that the patient agreed to APCM, understands only one provider can bill it per month, and knows they can opt out.
• No evidence behind the code: billing APCM without documentation of service elements--no recent care plan, no documented transitions follow-up, no sign of 24/7 access being available.
• Code stacking / duplication: billing APCM alongside CCM/PCM/TCM in ways that look duplicative to auditors, or pairing APCM with RPM in ways that double-count the same work.
• Quality reporting gaps: billing APCM but not fulfilling the associated MVP/ACO performance-measure expectations where you are subject to them.

FairPath’s job is to convert these into software rules instead of memory tests: no APCM claim is generated unless consent is on file, a minimum evidence set is present, and the code combination passes your configured stacking rules. If you prefer to run APCM manually, you’ll want a written policy and internal audit plan that checks these same points before claims go out.

8. What does a realistic 90-day APCM rollout look like?

In most practices, a 90-day rollout breaks into three phases:

• Days 1–30: Design and mapping.
  Confirm your understanding of APCM, pick a clinical champion, export your Medicare panel, and segment patients into provisional G0556/57/58 tiers. Draft consent language, identify current gaps (e.g., care-plan coverage, transitions workflows), and decide whether to start with a pilot subset or go panel-wide.
• Days 31–60: Pilot and workflow hardening.
  Enroll an initial cohort, run APCM through your existing staff, and see where workflows break down--especially around documentation of care plans, after-hours access, and transitions. Tighten templates and processes, and begin using your APCM evidence pack to validate charts before claims.
• Days 61–90: Scale and standardize.
  Expand enrollment, monitor staff workload, and make final adjustments to roles and queues. Connect APCM patients to your MVP/ACO quality reporting plan, and lock in your monthly billing and internal-audit cycle.

With FairPath, much of this is baked into the implementation path: panel import, APCM tiering, workflow templates, and billing rules are configured up front, so your 90 days are spent validating and tuning rather than inventing everything from scratch.