For independent practice associations and accountable care organizations
Attributed lives, practice by practice, with no view of what is being captured. Kept Count shows program health across the network without opening a single practice's records.
Your practices bill the care-management codes, or do not, in their own systems and on their own terms. The network carries attribution, quality, and shared savings on the result and sees only the claims that eventually clear. Kept Count gives every practice the same month, the same rules, and the same packet, and gives the network the aggregate: enrolled, supported, held, and closed by practice, with the authority boundary keeping each practice's records its own.
Public evaluation uses synthetic data. Kept Count is designed for covered operation, and business associate agreements are executed per customer before live patient use.
What pays you
The codes and tiers behind the month.
Each participating practice bills these codes for its own attributed members. The network's return is the aggregate: consistent capture, supported months, and the attribution that APCM months help carry.
G0556
APCM level 1, one or fewer chronic conditions
$16.37
Per member per month. No minute threshold. Consent, the initiating visit, and the practice-level capabilities carry the claim.
G0557
APCM level 2, two or more chronic conditions
$53.78
Per member per month. The tier most enrolled members land in. Held when the condition count is not documented.
G0558
APCM level 3, two or more conditions and QMB
$117.24
Per member per month. QMB status is verified before the tier is assigned, and a QMB member is never billed cost-sharing.
99490
CCM non-complex, first 20 minutes
$66.13
Per member per month. Time-based, so every minute is server-timestamped, and the same member cannot carry CCM and APCM in one month.
G0019 and G0022
Community health integration
Per your fee schedule
Monthly, time-based, furnished by auxiliary personnel under general supervision after an initiating visit by the billing practitioner. Rate per your fee schedule.
G0023 and G0024
Principal illness navigation
Per your fee schedule
Monthly, time-based, for a serious high-risk condition after an initiating visit. Rate per your fee schedule.
Attribution
APCM and Shared Savings Program assignment
Per your fee schedule
CMS lists APCM among the primary care services used for Shared Savings Program beneficiary assignment. A captured APCM month is evidence of the primary-care relationship attribution rests on.
CY2026 Medicare Physician Fee Schedule national non-facility rates, verified September 7, 2026. Confirm against your MAC locality fee schedule before relying on any figure. Codes shown without a rate are paid on your fee schedule and are not priced on this site.
How the month runs in Kept Count
One month, start to packet.
Each step is shown on synthetic data. Your roles, your rules, and your month close run the same way in the workflow session.
- 01
Each practice scans its own attributed panel
Every practice classifies its members by program fit, condition count, QMB status, and payer type against the same rules. Medicare Advantage members are held until a payer-specific rate is verified.
Synthetic data - 02
One month, one set of rules, in every practice
Consent, time evidence, exclusion rules, and supervisor review run identically in each practice. The rules are data the network configures once, maintained with a certified coding professional.
Synthetic data - 03
Each practice closes its own month
A practice supervisor reviews supported, held, and unknown member-months and closes the month. The hashed packet goes to that practice's billing department, not to the network.
Synthetic data - 04
The network sees the roll-up
Enrolled, supported, held, and closed by practice, with hold reasons as aggregate buckets. Small cells are suppressed. There is no drill-through to a member and no cross-practice record access.
Synthetic data - 05
Readiness by practice before expansion
The network sees which practices have consent scripts, supervision, and intake in place and which do not, and expands the program on evidence rather than on a rollout date.
Synthetic data
Proof that applies to you
Tested in the open, on synthetic data, before any customer.
Every claim below is checked in the codebase and documented on the proof page. None of it is a customer result, and none of it is a promise of payment.
10,000 synthetic members, 29,100 patient-months
A certified synthetic run of the full platform: 24 navigator panels capped at 250, every expected code and hold reason matched, zero patient rows visible across panels or organizations.
Row-level security on every table
Access is checked at the database, scoped to the organization that owns the row. No table relies on an open policy.
Exclusion rules enforced in the database
A same-month conflict between code families is rejected by a database trigger before the time entry exists. Application code cannot route around it.
Fresh-database replay in the release gate
Every migration replays in order against a brand-new disposable database in continuous integration, then runs the security tests, before a release is trusted.
What Kept Count will never do
The boundaries are the product.
Care-management software earns trust by making responsibility easy to inspect. These are the lines Kept Count holds for you, on purpose.
The network never sees a practice's records
Row-level security scopes every row to the organization that owns it. The network view is built from aggregates the database produces, not from access the network holds.
Kept Count never bills on a practice's behalf
Each practice's billing department codes and submits its own months from its own packet. The network gets counts, not claims.
Kept Count never takes a share of savings or collections
The fee is per enrolled member or per network, owed whether or not a claim pays. Nothing in the pricing bends toward a code or a savings number.
Questions this buyer asks
Answered directly.
Our practices use different EHRs. Does that matter?
No. Kept Count runs beside each chart rather than inside it. Members and eligibility arrive by file, the program month runs in Kept Count, and the packet goes back to each practice's billing department.
Can the network see why a practice's months are held?
As buckets, yes: no consent, missing element, payer held, exclusion conflict, and so on, with small cells suppressed. As members, no. The practice works its own holds.
Some practices already run a care-management vendor.
Those practices can keep their vendor for the work and use Kept Count for the packet and the network roll-up, or run the whole month in Kept Count. What the network needs is one standard and one aggregate, not one vendor.
How does this help attribution?
Attribution rests on primary-care services, and APCM is on that list. Every supported APCM month is a documented primary-care relationship for that member with that practice. The roll-up shows the network how many attributed members carry one.
What agreements does a network deployment require?
Kept Count is designed for covered operation, with a business associate agreement executed per customer. Each practice's data is its own tenant. The network's aggregate view is configured under the network agreement and contains no protected health information.
Next step
Bring three practices and one month. We will show the network view you do not have today.
A workflow session runs a sample network through the practice month and the roll-up on synthetic data. No patient information, no agreement, no cost.