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.
Stated plainly
What is not built yet.
A security or integration reviewer will find these anyway, so here they are, itemized, for your team to plan around.
- No live connection to any named electronic health record.
- No SMART on FHIR authorization flow — no app registration, no OAuth client, no scope negotiation with a vendor's authorization server.
- No FHIR Bulk Data ($export) client.
- No write-back to the electronic health record. Your EHR remains the clinical record.
- No HL7 v2 interface.
- No claims submission. Kept Count prepares 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.