APCM’s 13 Service Elements: What “Availability” Actually Means for Each One

CMS wrote APCM’s billing requirement around a specific word, and most practices skim past it: a patient needs access to all 13 service elements, not delivery of all 13 every month. That distinction sounds like a technicality until you’re the one deciding what documentation actually proves a practice made 24/7 access available to a patient who never called after hours. This page unpacks each element individually, the way Mindbowser’s own APCM pillar doesn’t have room to, because the pillar covers the whole program and this page covers just this one requirement in the depth it deserves.

Epic-Approved Vendor · HIPAA and SOC 2 controls built into every build · 50+ healthcare solutions shipped.

Consent and the Initiating Visit

Consent has to be obtained, written or verbal, and documented before APCM billing begins, and it needs to cover the specific elements of the program, not a generic care-management consent a practice may already have on file for CCM. The initiating visit establishes the care plan and the patient relationship that everything else builds on. A practice reusing an old CCM consent form without updating it to reference APCM specifically is the most common documentation gap at this stage.

24/7 Access and Continuity of Care

These two elements get satisfied by default more often than they get documented. A practice with an after-hours answering service or on-call provider is almost certainly meeting the 24/7 access requirement already. The gap is rarely the service; it’s the record showing the service exists, how a patient reaches it, and that it was available during the billed month, not just generally in place.

Continuity of care means the same care team, or a designated substitute, manages the patient’s ongoing care rather than routing them to whichever provider has an open slot. Documentation here is less about a single event and more about a pattern: the chart should show a consistent care team across visits, not a different provider every time with no continuity note explaining why.

Practices running APCM across a large panel with several providers hit a version of this that a single-physician practice never sees: continuity has to hold across the team, not just per patient. If a patient sees Provider A for three visits and then Provider B for the fourth with no designated-substitute note explaining the switch, that’s a continuity gap even if Provider B is a perfectly reasonable clinical choice for that visit.

The requirement isn’t that one specific person handles every visit forever; it’s that the switch, when it happens, is intentional and documented rather than an artifact of whoever had an open slot that day. A scheduling system built purely to fill the next available appointment, without a continuity check against who’s already managing that patient’s APCM enrollment, will generate exactly this gap at scale without anyone deciding to create it.

Alternative Care Delivery and Comprehensive Care Management

Alternative care delivery methods, telehealth, e-visits, asynchronous messaging need to be available as an option, even for patients who never use them. Comprehensive care management is the broadest element on this list and the one most likely to get treated as a catch-all rather than something specifically documented.

“Comprehensive” isn’t a vague quality standard; CMS defines it as these four specific components tied into one plan.

The Care Plan and Care Transitions Coordination

APCM’s care-plan requirement overlaps substantially with CCM’s existing care-plan documentation, which is useful for practices already running CCM: the same underlying care-plan infrastructure largely satisfies this element for APCM too, with updates to reflect APCM-specific language. Care transitions coordination covers what happens when a patient moves between care settings, such as a hospital discharge, a specialist referral, or a skilled nursing admission, and whether the primary care team’s plan accounts for that transition rather than treating it as outside their scope.

The distinction that matters operationally: a care plan is a static document until something changes, and care transitions coordination is the part of the requirement that forces it to update in response to a real-world event. A patient’s care plan written at enrollment and never touched again satisfies the letter of the care-plan element but fails care transitions coordination the first time that patient is hospitalized and the plan doesn’t reflect it. This is where APCM’s requirement is stricter than it might first appear: CMS isn’t just asking for a document to exist, it’s asking for the document to stay current against events the practice doesn’t always control the timing of.

A patient can be discharged from an unrelated hospital system on a Friday afternoon with no ADT feed reaching the primary care practice until the following week, and the care-transitions clock doesn’t wait for that delay to resolve itself. Practices that treat this element as “we have a care plan” rather than “we have a care plan that updates when the patient’s situation changes” are the ones most likely to have a technically-present-but-functionally-stale document if a reviewer pulls the chart mid-episode.

Ongoing and Enhanced Communication: The Two Elements Most Often Confused

These read as near-synonyms in CMS’s own list, which is exactly why practices under-document the distinction between them.

Population Data Analysis and Risk Stratification

These two elements are where EHR connectivity genuinely matters, not as a generic claim but because analyzing a population and stratifying risk requires current data pulled from across a practice’s patient panel, not a manual review of individual charts. ConnectHealth is the layer that makes this data available live, pulling condition and risk data from Epic, Cerner, Athenahealth, or whatever EHR a practice runs, so population analysis reflects current panel data rather than a stale export someone ran at the start of the quarter.

Performance Measurement: The Element Tied to MIPS Value Pathway Reporting

This is the element with the most concrete external requirement attached to it. For MIPS-eligible clinicians, performance measurement is satisfied through the Value in Primary Care MIPS Value Pathway, with CMS able to withhold APCM payment for incomplete reporting. For the full mechanics of this requirement, including the MIPS penalty exposure and the FQHC/RHC exemption, see the performance-measurement section of Mindbowser’s APCM guide, which covers this element in depth rather than repeating it here.

Building Documentation That Proves Availability, Not Just Claims It

Software that tracks which tier each element falls into, and flags gaps by tier rather than treating all 13 as one undifferentiated checklist, is what turns “we believe we’re compliant” into a record that survives a review.

The tiering matters because a gap in a structural element and a gap in a recurring element have different fixes and different urgency. A missing standing-capability record, no documented after-hours access policy, for instance, is a one-time fix that closes the gap for every enrolled patient at once. A missing recurring-element record, a month where care-plan updates weren’t logged for a specific patient, is a per-patient, per-month problem that compounds silently if nothing flags it.

Treating both as equally urgent either wastes effort chasing a structural fix that’s already solved, or under-reacts to a recurring gap that’s quietly accumulating across the panel. A practice auditing its own APCM documentation for the first time usually finds the structural elements in reasonable shape and the recurring elements far patchier, simply because structural documentation gets set up once and recurring documentation depends on it happening correctly every single month without fail.