Platform
How Pulse Platform connects to your EMR and operations stack.
Pulse Platform runs referral intake, authorizations, scheduling, and case management in front of your EMR, not instead of it. It integrates with HHAeXchange and AlayaCare. Here is what each connection does, and how every other connection is scoped.
Live today: HHAeXchange.
The HHAeXchange integration is live with customers. It is a one-way patient profile push: Pulse Platform sends the patient profile to HHAeXchange, and the patient ID that HHAeXchange returns is stored on the Pulse record, so both systems refer to the same patient. Americas Home Health runs this connection in production. Read the Americas Home Health case study.
Today the connection is one-way. The Americas Home Health rollout was built as a foundation that a later phase can extend.
Available: AlayaCare.
Pulse Platform also integrates with AlayaCare. The AlayaCare connector creates the client in AlayaCare and stores the AlayaCare ID on the Pulse record, so both systems refer to the same client. The connector runs one way, from Pulse Platform to AlayaCare. Syncing visits, EVV, caregiver availability, or status updates back from AlayaCare is on the roadmap.
Integration status by system.
Live means customers use the connection in production. Available means the connector ships in the product.
| System | Category | Status | What moves |
|---|---|---|---|
| HHAeXchange | Home care EMR and EVV | Live with customers | One-way patient profile push; patient ID returned to Pulse Platform |
| Apploi | Caregiver recruiting | Live at EOM Homecare | New applications arrive in the Pulse Platform recruiting workflow |
| AlayaCare | Home care EMR | Available | One-way client create in AlayaCare; AlayaCare ID stored on the Pulse record |
| CentralReach | ABA practice management | Scoped with each customer | Defined with each customer during scoping |
| Rethink | ABA practice management | Scoped with each customer | Defined with each customer during scoping |
| PointClickCare | Skilled nursing EHR | Scoped with each customer | Defined with each customer during scoping |
| Other EMR, EVV, billing, and payroll systems | Various | Scoped with each customer | Defined with each customer during scoping |
How other connections are scoped.
Every other connection is scoped with each customer before work starts: which system owns the patient record, scheduling, and EVV, which data moves, in which direction, and how often. The HHAeXchange and AlayaCare connectors are included in the Pulse license; other connections are priced as custom add-ons.
Behavioral health EHRs follow the same rule. Kipu and ZenCharts connections are not off-the-shelf Pulse Platform connectors: the Madison Ave team that builds Pulse Platform has delivered customer-specific integration work with both for treatment providers. See addiction treatment center work.
Recruiting and e-signature.
Recruiting integrations run on the same record. EOM Homecare connects Apploi to its Pulse Platform recruiting workflow and uses embedded e-signature inside each credentialing stage. Read the EOM Homecare case study.
AppExchange ecosystem.
Pulse Platform is built on Salesforce and distributed on the Salesforce AppExchange. AppExchange apps your organization licenses, such as document signing, BI, or credentialing tools, can typically be added to the same Salesforce org, subject to each app’s own terms.
Open APIs.
Because Pulse Platform records live in Salesforce, your integration team can work with them through the standard Salesforce REST and Bulk APIs, using patterns it already knows.
Keep exploring: Pricing, Home care, Behavioral health, Addiction treatment, ABA therapy, Skilled nursing, Multi-location enterprise, or contact our team.
Map your integrations.
Book a working session and bring the list of systems you run today.
Book a Demo