Skip to content
Illustrative photograph of neighborhood follow-through between visits, with a clinical bag in hand. Not Kept Count staff, customers, or patients.

Care between visits — for provider organizations, care networks, and approved community partners

Know what this month can support.

Care-management platforms help you reach patients and file claims. Kept Count keeps the work between visits in one month — so billing, compliance, or a funder can see what is ready, what is held, and what still needs a person. Your EHR stays the clinical record. Coding and claims stay with you.

Nothing auto-submits. The fee never moves with collections. A person still has to approve.

Kept Count · the month

Synthetic operating view

Kept Count My day: one synthetic person, the next action, and the month chain across the top
Today · one person, one next action. Synthetic demo · no patient data.

Recount

Prepare the contact. Draft what happened. Keep the person in charge.

Recount is Kept Count’s own AI for the care desk — not a rented clinical-assistant brand, not an ambient scribe. It rereads the record the worker can already see, prepares the next contact, and can draft Goal, Barrier, Action, and Result into the note form.

A person still accepts, edits, or dismisses. Recount does not rank the list, send a message, pick a code, write the ledger, or replace clinical judgment. Public evaluation stays synthetic until the covered environment and agreements are in place.

Read the Recount authority boundary

Choose your path

Who are you counting for?

Six kinds of organizations run care between visits. Each loses money in a different place, and each gets a different month in Kept Count.

Beside the EHR

No replacement project

Built for provider organizations

Health centers, medical groups, health systems and ACOs

Named workflows, not one stack

APCM, CHI, PIN, Health Home and related pathways stay separate

You still bill

Fixed fee; no automatic clinical or billing approval

Where we sit in the market

Reaching the patient is not the same as closing the month.

Engagement software helps you call, text, and enroll. Claims software helps you submit. Kept Count is the month those tools leave behind: what happened, what is still open, and what may reach review — without taking coding, claims, or clinical authority.

Illustrative photograph of neighborhood follow-through at a stoop between visits. Not Kept Count staff, customers, or patients.

Engagement platforms

Reach the patient. Capture the encounter.

They do not tell billing what this month can support.

Claims and automation

Move codes. File faster.

They do not hold unsupported work before a reviewer signs.

Kept Count

One month — ready, held, or unknown.

A person still approves. The fee never moves with collections.

How the month stays intact

One month. Still open. Already reviewable.

See what happened, what is still open, and who can move it — without rebuilding close from spreadsheets, inboxes, and separate reports.

  1. 01

    Today

    One ranked day, a week calendar, and CHW time that is not a claim. Every person has a next action — outreach, coordination, or follow-through.

  2. 02

    Patient

    Consent, program fit, missing facts, and assignment stay with the person. Recount prepares the contact from the chart before the visit counts as done.

  3. 03

    This month

    Gaps, holds, and named owners — while the month is still open and you can still fix them.

  4. 04

    Review

    Hand billing, compliance, or a funder what is supported, held, or unknown. Recount Review surfaces missing proof. Nothing auto-submits.

See the full month

Kept Count · the month

Synthetic operating view

Kept Count monthly evidence close with human-review gates before billing handoff
Review packet · synthetic demo · no patient data

Hand someone the month — not a folder of exports.

Share the picture, then open the work, holds, and reviewer history when the team needs more than a screenshot.

Human approval stays visible at the practice and Pre-Billing boundaries.

Supported, held, and unknown states remain separate.

This month in the product

The month those other tools leave behind.

Open to coverage gaps, safety follow-up, and monthly-care pressure that still need an owner. Every item has a next action. Clinical and billing authority stay with the responsible provider.

Kept Count · the month

Synthetic operating view

Kept Count My day: one synthetic person, the next action, and the month chain across the top
Today · one person, one next action. Synthetic demo · no patient data.

Repeatable product validation

Tested against the cases that should move—and the ones that should stop.

Kept Count matched every expected classification in a fixed synthetic answer manifest, including coverage, consent, missing-evidence, duplicate-month, and tier-change cases. No PHI, database, network, or persistent patient record was used.

Expected codes and decision flags matched
100%
Qualifying and reason-coded hold paths tested
7
Stateless reference scenarios repeated
PHI or persistent patient records
0
Review the validation evidenceMethod, limits, walkthrough, and downloadable brief included.

CMS and OIG audit-response readiness

Give your Billing Department a defensible Pre-Billing record.

Kept Count turns practice-approved care-management requirements into visible work, named exceptions, and dated human review. If CMS, a Medicare contractor, or HHS-OIG asks for support, the evidence path is organized instead of scattered across inboxes and spreadsheets.

Illustrative photograph of one reviewer with a medical chart packet before billing handoff. Not Kept Count staff, customers, or patients.

Map requirements before codes move

Configure practice-approved criteria for APCM and other supported programs, then surface missing consent, patient facts, service elements, or capability evidence for review.

Hold unsupported or overlapping work

Keep conflicts, duplicate-month risk, missing support, and unresolved exceptions out of the supported queue until an authorized reviewer decides.

Preserve who reviewed what

Keep owners, dates, source references, decisions, holds, and correction history together for monitoring and record-response preparation.

Review the audit-response controls and authority boundary

One shared operation

Same month. Different authority.

Illustrative photograph of one reviewer sorting medical charts into supported and held stacks. Not Kept Count staff, customers, or patients.

Kept Count connects the people responsible for access, monthly care, supervision, and billing review. Permissions stay scoped. The practice keeps the decisions that are theirs.

Provider operations

See the program without assembling it.

Who is active, what is due, where work is stuck, and who owns the next step — across sites and teams.

See the provider solution

Care teams and navigators

Start the day with who needs you.

Community desks lead with today’s people, a week calendar, and outreach time that does not pretend to be billable. Practice desks keep clinical and claims authority.

See the partner solution

Pre-Billing and compliance

Review the month without a black box.

Trace the work, supervision, exceptions, and human approvals behind every supported or withheld line. Recount Review lists missing proof — it does not pick a code.

See the billing handoff

Community partnerships

Outreach can enter a provider-owned program without taking the practice with it.

Approved community teams support connection and follow-through. The receiving organization keeps patient access, supervision, clinical decisions, coding, and claims.

Explore navigator programs
Illustrative photograph of community care coordination with visit notes and a blood-pressure cuff. Not Kept Count staff, customers, or patients.

Practice economics

Put the opportunity next to the work it takes.

Choose Original Medicare, Medicare Advantage, or Medicaid, then add organization-level enrollment inputs. Original Medicare uses a labeled planning baseline; payer-specific paths require your verified written rate before economics appear.

No patient information, sign-in, or spreadsheet upload is required.

Interactive planning tool

Practice opportunity calculator

Choose a payer path, then use organization-level inputs. Original Medicare uses a labeled CY 2026 planning baseline. Medicare Advantage and Medicaid stay blocked until you supply a named, written rate source.

Step 1

Choose the payer path

The product never substitutes Medicare rates for a plan, state, program, or MCO.

Original Medicare is modeled from the published CY 2026 national non-facility APCM baseline, with the QMB coinsurance write-off shown explicitly.

Original Medicare baseline

Illustrative incremental annual gross

$102,673

$8,556 per month

Modeled only for the increase from 4% current enrollment to 25% target enrollment.

Illustrative year-one figure, assuming enrollment ramps in over the first 12 months: $51,337, reaching $102,673 at steady state.

Low
$82,139
Base
$102,673
High
$123,208

Low / high are an illustrative +/-20% planning band around the base case, not a statistical forecast.

Already net of $4,578 a year in QMB coinsurance you cannot bill. Allowed amounts would total $107,251; this model uses the lower figure as its realizable planning estimate.

Modeled chronic-condition pool
670
Incremental patient gap
194

67% chronic-condition share

12.5% QMB share

Uses practice-level assumptions only. No patient information is requested or needed.

Your provider organization

4 inputs
%
%
%

Planning estimate only—not a reimbursement forecast. Eligibility, documentation, billability, and rates require patient-level review by the practice.

Implementation decision

Choose how the program runs.

Compare the operating model—not just the gross reimbursement estimate. Staffing can be planned before a rate is known; net economics stay blocked until the payer rate is ready.

Incremental gross annual
$102,673
Staffing expense (coordinator–RN)
$110,000–$200,000/ yr
Incremental contribution after modeled cost
−$7,327
Care-management capacity
2 modeled FTEs
Assumptions and exclusions

FTE need is a planning estimate and may be met with existing or new staff. Actual capacity varies with acuity, workflow, supervision, and program requirements.

This is not practice net income. It excludes implementation, supervision, RCM and denial effects, overhead, patient cost sharing, payer variation, and uncollected amounts.

Your provider organization retains clinical supervision, the EHR, coding, claims submission, and final compliance authority.

Turn this estimate into a pilot plan
Refine the modelStrategy, QMB share, realization, staffing, fee and code assumptions

Care model

APCM-first is the default because it organizes eligible care around monthly service requirements rather than a minutes-first workflow.

The model assigns G0556 to the non-chronic share, G0557 to the 2+ chronic non-QMB share, and G0558 to the QMB share, as planning assumptions. The practice must validate eligibility and tier selection.

%

Realization assumptions

%
%

Staffing assumptions

Refine the capacity and cost assumptions behind the practice-team model.

Detailed model output

Published rates and internal planning assumptions are shown separately. Billing authority and final coding remain with the practice.

Illustrative incremental contribution after staffing

−$7,327/ year

G0558 · APCM

QMB share · net of coinsurance write-off

Patients
16
Rate / mo
$93.79
Annual
$18,310

G0557 · APCM

2+ chronic, non-QMB

Patients
114
Rate / mo
$53.78
Annual
$72,023

G0556 · APCM

Base tier · 0–1 chronic conditions

Patients
64
Rate / mo
$16.37
Annual
$12,340
Incremental gross annual
$102,673
Care-team FTEs
2
Staffing / yr
$110,000

APCM inputs use CMS CY 2026 national non-facility rates: G0556 $16.37, G0557 $53.78 and G0558 $117.24 allowed. The QMB tier is modeled at $93.79 — QMBs cannot be billed Medicare cost sharing, so the 20% coinsurance is written off or crossed over to a state Medicaid program that many states pay at zero. Non-QMB coinsurance is further reduced by the modeled collection rate, and the enrolled base by modeled attrition. Medicare Advantage members are excluded from this fee-for- service math entirely. Actual payment, eligibility and cost sharing vary and must be validated. See the CMS Physician Fee Schedule — Advanced Primary Care Management. The optional CCM-first view uses an internal illustrative $78 planning blend—not a single CMS rate and not an assertion that services may be billed together. The model assumes 67% of the fee-for-service panel has 2+ chronic conditions (CMS chartbook estimate); the remainder is modeled at the G0556 base tier. The year-one ramp and low/base/high band are illustrative planning assumptions, not forecasts. QMB protections, service requirements, documentation and billing compatibility must be verified against current CMS and MAC guidance during Pre-Billing review.

Implementation

Start with one site, one cohort, and a plan you can actually run.

Kept Count is configured around the team, systems, policies, and partners you already have.

Build a readiness plan
  1. 01

    Map

    Document the panel, staffing, EHR and billing handoffs, supervision, consent, and current gaps.

  2. 02

    Configure

    Set roles, permissions, escalation paths, documentation rules, and review ownership around the way your organization works.

  3. 03

    Rehearse

    Run the complete workflow with synthetic records before any live patient operation is approved.

  4. 04

    Activate

    Begin with an approved site and cohort, then expand when your clinical, operational, and billing leaders are ready.

Operating boundaries

Useful software makes responsibility clearer, not blurrier.

Everything Kept Count will not do lives in one place, on purpose.

Review the trust center

Kept Count organizes

  • Panel and enrollment workflow
  • Assigned monthly care work
  • Exceptions and supervision
  • Evidence and review history

Your provider organization retains

  • The EHR and clinical record
  • Clinical supervision and judgment
  • Coding and claim submission
  • Final compliance and legal decisions

What Kept Count will never do

  • The evaluation environment runs on synthetic data only, so your team can test the full workflow before any real patient record touches the system.
  • The validation results on this page come from a repeatable rules-and-exception test suite. They show the system behaves consistently, not a production-capacity benchmark, a clinical-eligibility determination, a reimbursement guarantee, a compliance certification, or an audit guarantee.
  • Kept Count never certifies compliance, determines medical necessity, selects the final code, or submits a claim. It supports your compliance and audit-response workflow so your team makes those calls with the evidence in front of them.
  • The practice-economics calculator opens the planning conversation. Your provider organization confirms patient-level eligibility, locality and payer rates, service requirements, documentation, coding, and collections before anything is final.
  • Production activates only after named approvals from your organization. Kept Count never flips that switch on its own.
  • Kept Count organizes the operation. Your clinicians, billers, and compliance leaders keep the decisions that are theirs.

Common questions

What to know before a first cohort

The short answer: Kept Count runs the month. Your organization keeps the decisions. See operating boundaries above for exactly what that does and does not include.

Does Kept Count replace our EHR?

No. Your EHR remains the clinical system of record. Kept Count organizes the care-management operation beside it: panel review, enrollment, monthly work, supervision, exceptions, and the handoff to billing or program review.

Is Kept Count only for APCM?

No. APCM is one named workflow. CHI, PIN, Health Home, CCM, and related programs are different pathways, not one stacked product. Kept Count does not make a service automatically billable.

Can community navigators work in the same program?

Yes, when the receiving organization approves the relationship, scope, access, training, and escalation rules. Navigators see only the work assigned to them; provider leaders keep patient, clinical, coding, supervision, and billing authority.

Who decides what gets billed?

The practice and its Billing Department or designated RCM reviewer. Kept Count prepares a reviewable Pre-Billing record and keeps unsupported or conflicting work visible. It does not automatically code, submit, or guarantee payment for a claim.

What happens before live patient use?

The organization completes a readiness review, approves the operating and authority model, configures access and safeguards, and validates the workflow with synthetic data. A customer BAA is executed before any real patient data moves.

What is Recount?

Recount is Kept Count’s own AI for the care desk. It prepares the next contact and can draft what happened into Goal, Barrier, Action, and Result — cited to the record. A person still accepts, edits, or dismisses. Recount does not rank the worklist, send a message, pick a code, write the ledger, or replace clinical judgment. Public evaluation stays synthetic until the covered environment and agreements are in place.

Bring a named first cohort. We’ll map the first month.

Show us how people, staff, partners, supervisors, and billing move through the month today. We’ll name the gaps and the approvals required to start.