For New York Health Home lead entities
You attest for every downstream agency's months. Kept Count shows each agency's capture and downgrade exposure as aggregates, with no PHI crossing organizations.
The lead entity carries the network's attestation risk and sees the network through claims that have already paid. Kept Count gives each care-management agency the same month, the same minimums, and the same close, and gives the lead the roll-up: members enrolled, months met, months at risk of downgrade, and plan-of-care deadlines, by agency, as aggregate buckets with small-cell suppression. No drill-through. No member record crosses an organization.
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 tiers your agencies bill, and the downgrade the network absorbs when an HH+ month misses its minimum. The lead sees these as counts by agency, never as members.
Rate code 1853
HH+ care management
$925.28 downstate, $867.45 upstate
Per member per month. Requires 4 core services in the month, 2 of them face-to-face.
Rate code 1876
HH+ assisted outpatient treatment
$1,115.19 downstate, $1,046.64 upstate
Per member per month. Requires 4 core services, all 4 face-to-face.
Rate code 1874
High Risk / High Need care management
$386.83 downstate, $363.60 upstate
Per member per month. Requires at least 1 core service. This is also where an HH+ month lands when it misses its minimum.
The downgrade
HH+ month that misses its minimum
$538.45 lost downstate, $503.85 upstate
The month does not fail. It quietly pays the High Risk rate for a documentation reason, and nothing in the remittance says why.
Published New York State Department of Health Health Home rates, rate cycle 2511, effective April 1, 2025. A later rate column is posted pending federal approval and is deliberately not shown. Verify against the current fee schedule before relying on any figure. Children's Health Home tiers are counted but never 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
Onboard each agency as its own tenant
Every care-management agency runs its own month in its own tenant, with the state minimums configured once by the network. Readiness by agency shows who is set up and who is not.
Synthetic data - 02
Agencies capture the month against the minimum
Core services, face-to-face contacts, and the plan-of-care clock are counted in each agency as they happen. Care managers and their supervisors see the shortfall with days left.
Synthetic data - 03
The lead sees the roll-up
Members enrolled, months met, months at risk, and downgrade exposure by agency as aggregate buckets. Small cells are suppressed. There is no member view and no path to one.
Synthetic data - 04
Each agency closes and exports its own month
The agency reviews its month, closes it at the tier it actually cleared, and exports CSV or XLSX. The lead's view updates from the closed counts.
Synthetic data - 05
Attest from evidence, not from trust
At period end the lead has, by agency, how many months met their tier, how many downgraded, and how many plans of care were on time. The network conversation moves from the remittance to the month.
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.
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.
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.
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.
Kept Count never lets PHI cross organizations
The lead's view is built from aggregates the database produces under each agency's row-level security. Small cells are suppressed. There is no drill-through, and the network agreement contains no member data.
Kept Count never takes a percentage
The network fee is fixed, owed whether or not a month pays. A vendor paid on the upgrade has a reason to count generously. Kept Count does not.
Kept Count never submits on an agency's behalf
Every closed month leaves the agency as a file it reviews and uploads. The lead's oversight is of counts, never of claims.
Questions this buyer asks
Answered directly.
Our agencies use different care-management systems.
Each agency keeps its system of record and runs the counting month in Kept Count. Members arrive by file. The network gets one standard and one roll-up regardless of what sits underneath.
Can the lead see a specific member's months?
No, and that is the point. The lead sees buckets by agency with small cells suppressed. If a bucket needs investigation, the conversation happens with the agency, under the network's existing process.
What does an agency have to change to participate?
Care managers record core services and face-to-face contacts in Kept Count as they happen, and the agency closes its month there. The readiness view shows the lead which agencies have done the setup.
How is the network fee structured?
As a fixed fee for the network, never a percentage of anything the agencies bill. Pricing is discussed in the workflow session, against your network's size and structure.
What agreements are required?
Kept Count is designed for covered operation, with a business associate agreement executed per customer. Each agency is its own tenant under its own agreement. The lead's aggregate view is configured under the network agreement.
Next step
Bring your agency list and one quarter of remittances. We will show you the downgrade exposure you are attesting to.
A workflow session runs a sample network through the agency month and the lead roll-up on synthetic data. No member information, no agreement, no cost.