KanTime API
KanTime is an enterprise EMR and agency-management platform for post-acute care, supporting home health, hospice, pediatrics, private home care, palliative care, and self-directed care from a single system. This page is an independent design exercise that asks what a well-designed KanTime API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed KanTime API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing KanTime product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is KanTime?
KanTime is an enterprise EMR and agency-management platform for post-acute care, supporting home health, hospice, pediatrics, private home care, palliative care, and self-directed care from a single system. The platform spans intelligent scheduling, longitudinal clinical management, point-of-care documentation, electronic visit verification integrated with state aggregators, and end-to-end e-billing, serving mid-to-large multi-branch, multi-service-line agencies.
Core product areas include:
- Service lines (Home Health, Hospice, Pediatrics, Private Home Care, Palliative Care, Self-Directed Care)
- Intelligent Scheduling and CareTracker (staffing coordination and CareOps)
- Comprehensive Clinical Management (longitudinal records and point-of-care documentation)
- End-to-End E-Billing and Payroll as a Service (invoicing, claims tracking, timesheets)
- KanTime+ and EVV (business intelligence plus visit verification integrated with state aggregators like Sandata, HHA eXchange, and CareBridge)
An API for a platform like this would naturally organize around its core data entities:
- Patients, Census, Referrals, Authorizations
- Visit schedules, EVV records, Clinician assignments
- OASIS-E assessments, Clinical notes, Physician orders
- Claims/EDI, Invoices, Payroll inputs
The KanTime Integration Challenge
Multi-branch post-acute agencies run scheduling, clinical documentation, EVV, and billing on KanTime every day, but programmatic access to that data is heavily gated:
- No public B2B API: there is no developer portal and no self-serve signup; the only publicly documented API is a Cures Act patient-access "Patient API" PDF (Basic Auth with patient portal credentials, returning CCDA XML), built for individual patients, not agency operations
- Partner-mediated interoperability: B2B integration runs through KanTime's Interoperability Hub (HL7, FHIR, CCDA) with 125+ hand-connected partners and per-agency enablement projects coordinated by KanTime's team
- No developer surface: no SDKs, no public webhooks, no sandbox, and no published pricing or technical documentation for agency data
- Customer-reported integration limits: reviewers cite integration capabilities as the platform's main limitation, including gaps connecting to external billing programs
- Multi-service-line complexity: home health, hospice, pediatric, and private duty lines each carry their own document types, payer rules, and EVV state-aggregator requirements
- PHI and compliance constraints: OASIS-E assessments, EVV records, and Medicare/Medicaid claims demand HIPAA-aligned access controls and audit trails
What a KanTime API Could Look Like
If KanTime exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like KanTime: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate to a KanTime agency account and obtain a session token for downstream calls.
Patient Operations
/patientsWould list patients and census records with filters for service line, branch, status, and payer.
Visits
/visitsWould retrieve completed and upcoming visits with clinician, EVV status, and date-range filters.
Scheduling
/schedulesWould pull visit schedules and clinician assignments across branches and service lines.
Clinical
/oasis_assessmentsWould retrieve OASIS-E assessments, clinical notes, and physician orders tied to patient episodes.
Billing
/claimsWould pull claims, invoices, and authorization status by payer, episode, and date range.
Use Cases
Sync census and visit data into your systems
- Pull patients, referrals, and authorizations from KanTime into a central warehouse - Stream visit completions and EVV records to downstream analytics and payroll tools - Keep census in sync across home health, hospice, pediatric, and private duty lines
Automate scheduling and EVV compliance
- Pull visit schedules and clinician assignments across branches in near real time - Flag unverified or missed visits before they hit state aggregator deadlines - Feed schedule data to staffing and capacity planning workflows
Reconcile billing, claims, and payroll
- Pull claims, invoices, and EDI status for financial reporting - Match visit activity against expected reimbursement to surface leakage - Sync timesheet and payroll inputs to external billing and payroll programs KanTime doesn't natively connect to
Power clinical quality and compliance reporting
- Extract OASIS-E assessments and point-of-care documentation for QA review - Track orders and documentation completeness across service lines - Surface documentation gaps to clinical leadership dashboards automatically
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require agency credentials and MFA handled in a managed, encrypted session
Connectivity
Would build on authenticated KanTime web workflows surfaced as a normalized API across service lines
Response format
Normalized JSON across patient, visit, schedule, OASIS-E, and claim objects
Rate limits
Adaptive throttling tuned to your agency environment to avoid platform-side limits
Session management
Would need automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for census, visits, and claims with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, HIPAA-aligned controls, and audit logging
Webhooks
Event-style callbacks for new referrals, visit completions, EVV events, and claim status changes
Latency
Design target: sub-second reads on cached entities; multi-second writes when posting through scheduling and billing workflows
Throughput
Design target: horizontally scaled workers sized to multi-branch, multi-service-line agency volume
Reliability
Retry, backoff, and idempotency keys for intake, scheduling, and claim operations
Versioning
Clear versioning and change management would matter as KanTime evolves
Frequently asked questions
Yes. PHI flows through an encrypted credential vault with scoped tokens, HIPAA-aligned access controls, and full audit logging so clinical and billing data stays protected.
Home health, hospice, pediatrics, private duty, palliative, and self-directed care lines are supported from one API surface, covering patients and census, visit schedules, EVV records, OASIS-E assessments, clinical notes, claims, and invoices, with write operations where your configuration permits them.
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual KanTime product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.