Flat file, spreadsheet panel export
In production use
A CSV or XLSX roster export normalizes into Kept Count's intake contract. This is how every current panel gets in.
Integrations
Your EHR stays the system of record.
Kept Count runs your monthly program beside it, not inside it. Roster and panel data load today through a spreadsheet export. A FHIR R4 Bundle normalizer exists in software; connecting a live EHR is later scoped work, not the founding path.
What exists today
Two sources, one normalized intake.
Both sources produce the same normalized record. Everything downstream — eligibility classification, program tiering, the enrollment queue, the care board, the billing packet — is indifferent to which one produced it.
FHIR R4 Bundle normalizer
Built and unit-tested; the live connection is scoped with you
A Patient/Condition/Coverage FHIR R4 Bundle normalizes into the same intake shape as a spreadsheet upload. The transform is built and unit-tested today. Connecting it to your EHR's live endpoint is scoped work we do together as your first design partner.
Set up together
Scoped with your IT team.
Every connection is set up with your team, against your EHR’s own interfaces, before any patient data moves.
- Your EHR's live connection: we connect to its standard FHIR R4 interface with your IT team, under your vendor's authorization process.
- Patient lists at any size: start with a panel file export from any EHR, and move to a scheduled feed when your team is ready.
- Your EHR stays the clinical record. Kept Count reads what it needs and keeps the work between visits beside it.
- Interface formats your environment already uses, such as HL7 v2 feeds, are scoped during setup.
- Claims stay with your biller. Kept Count hands over review-ready evidence; your organization or its revenue-cycle partner submits.
Eligibility verification
Spreadsheet in. Live eligibility feeds later, if you pay for them.
Founding scope is a CSV or XLSX roster your team already exports. Kept Count does not submit claims and does not operate a clearinghouse. If a later phase needs a named eligibility feed, we scope that as paid adapter work against the vendor you already use — not as a go-live requirement.
Tell us your EHR and your export format.
We will tell you directly whether today's roster or FHIR intake fits your workflow, and exactly what we would build together if it doesn't.