Approved EHR connector
Vendor-specific authentication, authorized reads, subscriptions or webhooks, and explicitly supported writes.
Pro KPO integrations
Keep the systems that already run your organization.
Add an intelligent staffing layer through approved, customer-authorized connections. Pro KPO's business logic is designed to remain independent of any one EHR vendor.
Per-agency authorization
Event-driven where supported
Rules before write-back
Continuous reconciliation
Connector architecture
Translate each EHR into one controlled staffing model.
The connector handles vendor differences. The Pro KPO engine handles customer policy, staffing workflow, autonomy, and auditability.
Normalized staffing model
A common model for workers, clients or residents, locations, units, shifts, availability, credentials, and external IDs.
Pro KPO policy engine
Deterministic eligibility, customer authority settings, call-out workflow, outreach, awards, and exception routing.
Controlled write-back
Idempotent commands, retries, conflict handling, reconciliation, and a traceable external result.
Connector status
Status means evidence - not engineering intention.
A connector moves to Available only after the required vendor access, implementation, testing, customer authorization, and operational approval are complete.
Pro KPO Connect
WellSky Personal Care
API Connect is the relevant WellSky product for real-time bidirectional use. Multi-client and Marketplace requirements remain under discussion.
Pro KPO Connect
AxisCare
Target home-care environment. Connector access, supported operations, commercial terms, and testing have not been established.
Pro KPO Connect
CareSmartz360
Target home-care environment. Connector access, supported operations, commercial terms, and testing have not been established.
Pro KPO Connect
Homecare Homebase (HCHB)
Target home-care environment. Connector access, supported operations, commercial terms, and testing have not been established.
Pro KPO LTC
PointClickCare
Target LTC environment. No live connector or official partnership is being claimed.
Pro KPO LTC
MatrixCare
Target LTC environment. No live connector or official partnership is being claimed.
Third-party names and marks belong to their respective owners. Their appearance here identifies target environments only and does not imply endorsement, certification, Marketplace status, or an active commercial relationship.
WellSky discovery checklist
The first pilot depends on the shift operations behind the public API surface.
The published Connect API supports client-credential authentication and real-time object operations, but the exact closed-loop staffing methods still need technical confirmation.
One application serving multiple authorized customer agencies
Sandbox or test tenant and production enablement process
Create, reassign, unassign, cancel, and status-update shift operations
Shift or appointment change notifications and webhook delivery
Caregiver availability, qualifications, credentials, and active status
Per-agency licensing, partner terms, Marketplace steps, and support model
Rate limits, pagination, backfill, retry, and reconciliation requirements
Permission to use the WellSky name or logo during pilot and launch
01
Read-only discovery
Validate identities, field mappings, pagination, timestamps, time zones, and permitted history before workflow decisions depend on the data.
02
Shadow and approval modes
Compare Pro KPO recommendations with current operations, then require an authorized person to approve proposed external changes.
03
Controlled routine write-back
Enable only documented, tested, idempotent commands with conflict detection, reconciliation, and exception routing.
Integration discovery
Tell us which system must remain the source of record.
Share your EHR, agency or facility structure, desired workflow, current API access, and the operations that need read or write capability.