KanTime API
No B2B API. The only public document is a Cures Act patient-access API PDF using Basic Auth and CCDA XML. Business integration runs per agency through a partner-mediated Interoperability Hub speaking HL7, FHIR, and CCDA, with no developer portal or public webhooks.
Frequently asked questions
KanTime scores F on the API Report Card. No B2B API. The only public document is a Cures Act patient-access API PDF using Basic Auth and CCDA XML. Business integration runs per agency through a partner-mediated Interoperability Hub speaking HL7, FHIR, and CCDA, with no developer portal or public webhooks.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
KanTime is an enterprise EMR and agency-management platform for post-acute care, Medicare-certified home health, hospice, palliative, pediatric, private duty, and consumer-directed services: intake, scheduling, OASIS-E point-of-care documentation, EVV, billing/claims, payroll inputs.
Healthcare / Post-Acute, mid-to-large multi-branch, multi-service-line agencies.
700 agencies with 1,200+ branches, ~900,000 patients, 210,000 users, $12.9B claims processed, 70M annual visits (2022 figures; likely larger today).
Demographics/census, OASIS-E assessments, clinical notes, visit schedules, all-state EVV records, claims/EDI, authorizations, invoicing, payroll inputs.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.