Skip to content

For church-based and community sponsor networks

You sponsor navigator programs across many sites and report to funders on faith. Kept Count gives you adoption and outcomes by site as funder-grade aggregates.

A sponsor network stands up navigator programs in congregations and community sites, connects each to a billing practice, and answers to funders for the whole. The sites are reach sites, not billing sites: they find and hold the people a practice cannot. Kept Count sponsors each site as its own organization, shows the network which sites are live, staffed, supervised, and delivering, and produces the aggregate report a funder will accept, with no member record crossing a site.

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.

The sponsor is not the biller. Each site's navigators furnish work under a billing practice's supervision, and the practice bills these codes. What the sponsor gains is a program that funders can see and practices want to keep.

  • 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.

  • Reach sites

    Sites find and hold; practices bill

    Per your fee schedule

    A congregation or community site reaches people a practice cannot. The practice provides the initiating visit and the supervision. The site's work becomes countable under the practice's month.

  • Funder reporting

    Aggregates a program officer can use

    Per your fee schedule

    Sites live, navigators active, members reached, months supported, and handoffs completed, by site and in total, with small cells suppressed. The report is produced from the same records the practices review, not from a separate survey.

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.

  1. 01

    Sponsor each site as its own organization

    Every site is onboarded as a separate tenant under the network's sponsorship, with its practice partner, its navigators, and its supervisor assignments. The readiness view shows which sites are set up and which are waiting on a step.

    Synthetic data
  2. 02

    Navigators work their assigned members

    Each site's navigators see only their assigned members. Time entries are server-timestamped and carry the supervising practitioner in force on that date.

    Synthetic data
  3. 03

    The network watches adoption

    Sites live, navigators active in the last thirty days, members reached, and months in progress, by site. A stalled site is visible in the second week, not at the quarterly meeting.

    Synthetic data
  4. 04

    Practices review and close their months

    Each practice partner reviews the member-months its sites produced and closes the month with a hashed packet for its own billing department. The sponsor sees the closed counts, not the members.

    Synthetic data
  5. 05

    Report to funders from the same records

    The funder report is an aggregate of what the practices reviewed: reached, supported, handed off, by site and in total, with small cells suppressed. It is produced in minutes and it reconciles because there is only one source.

    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.

  • 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.

  • Append-only audit trail

    Consent, assignment, role, and approval events are recorded with who acted and when. The log rejects edits and deletions, including by the table owner.

  • 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.

  • 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.

Read the full proof center, including what it does not prove

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.

  • Kept Count never turns a site into a billing site

    Sites reach and hold people. Practices provide the initiating visit, the supervision, and the claim. Kept Count keeps those roles distinct in the data, because blurring them is how a program loses its standing.

  • Kept Count never lets member data cross sites or reach the sponsor

    The sponsor's view is aggregates with small-cell suppression. A site sees its own program. A practice sees the members it authorized. Sponsorship buys visibility into adoption, not into people.

  • Kept Count never takes a percentage of anything a practice bills

    Sponsorship is per organization, owed whether or not a claim pays. The sponsor's incentive and the practice's stay their own.

Questions this buyer asks

Answered directly.

Our sites are congregations with volunteer navigators.

That is the model Kept Count is built for. Each site is its own organization, its navigators see only their assigned members, and supervision comes from the practice partner, not from the site. Volunteer or paid is a contract question between the practice and the site.

What does a site need in order to go live?

A practice partner that has authorized the program, at least one navigator, and a supervision assignment on record. The readiness view shows the sponsor exactly which of those each site still lacks.

Can the sponsor see outcomes, or only activity?

Both, as aggregates: members reached, months supported by the practice, handoffs completed, and holds by reason. What the sponsor cannot see is a member, and that is what makes the report safe to send to a funder.

We report to several funders with different templates.

The aggregate export is by site, by practice partner, and by period, and it is produced from one set of records. Reshaping it for a template is minutes of work, and the numbers reconcile across every version because there is one source.

What agreements does a sponsor deployment require?

Kept Count is designed for covered operation, with a business associate agreement executed per customer. Each practice partner is a covered entity for its members. The sponsor's aggregate view is configured under the sponsorship agreement and contains no protected health information.

Next step

Bring your site list and the practices you have. We will show you adoption by site the way a funder wants to see it.

A workflow session runs a sample network of sites through onboarding, supervision, and the aggregate report on synthetic data. No member information, no agreement, no cost.