Sunwave Health
EHR and practice management
EMR, CRM and billing. Sunwave documents a CallTrackingMetrics integration for calls; a website form method is not published.
EHR and practice management
Kipu and your treatment center website
EMR plus an admissions CRM. Kipu says its CRM turns website form inquiries into tasks; API access is by key, for Kipu clients and developers working with one.
- Read against the vendor's own pages
- BAA published
- Checked October 15, 2026
What it is
Behavioral health software with an EMR, a CRM for admissions and outreach, billing and compliance tools, used by addiction and behavioral health treatment centers.
How it connects to a website
- Form posting
Kipu's CRM page says it converts prospective patient information collected from forms on your website into tasks. It does not publish the technical method.
- API on request
Kipu's API page says clients, and developers working with a client, need an API key. Kipu's help center says access is set up in the EMR's API Management screen and that API use is a paid service.
What KhanWork does with it
- Build the website inquiry form to land in Kipu CRM the way Kipu sets it up for your account, then test it end to end with a dummy inquiry before launch.
- Connect call tracking where Kipu supports it. Kipu's CRM page lists call tracking vendors among the third-party platforms it integrates with, and shows CallRail and CallTrackingMetrics logos.
- Send analytics a count that a form was submitted, never what was typed into it.
- Leave the Kipu side (users, pipelines, API keys) with your Kipu admin or Kipu's own team.
Setup, as the vendor documents it
Kipu does not publish website form setup steps. For the API, Kipu's help center describes the request inside the Kipu EMR: a Super Admin opens Settings, Integrations, API Management and adds in-house or vendor access. A new vendor signs Kipu's Vendor Agreement before Kipu activates the connection, and Kipu notes that API use is a paid service.
What to watch out for
Where patient details can slip out with Kipu, and what the vendor's own documents say to switch on, switch off or ask for.
Kipu's BAA covers Kipu, not the path to it
The form on your website, the plugin that sends it and any middleware in between sit outside Kipu's agreement. Every hop that carries an inquiry needs its own answer to the same question: does that vendor sign a BAA?
42 CFR Part 2 travels with the record
Kipu's BAA has a section on 42 CFR Part 2. It says Part 2 information cannot be shared with agents or subcontractors without the patient's specific written consent. Ask how that applies to anything that syncs out of Kipu, such as call tracking or CRM exports.
Use Kipu's own API access
Kipu's documented route is API Management inside the Kipu EMR, where a third-party vendor signs a Vendor Agreement before Kipu activates its access. If a connector is not set up that way, ask how it reaches your data before you hand it credentials.
A certified vendor does not certify your site
Kipu shows a HITRUST certified logo on its site. That speaks to Kipu's platform. Your website, its forms and its tags are assessed on their own.
Keep inquiry details out of analytics
Google says it does not offer a BAA for Google Analytics. The analytics event for a submitted Kipu inquiry should carry no names, phone numbers, emails or answers.
Frequently asked questions
Kipu's CRM page says it converts information collected from forms on your website into tasks. It does not publish how, so the method depends on what Kipu enables for your account. We build the form to match and test it with a dummy inquiry before launch.
Kipu publishes a Business Associate Agreement on its website, last updated March 26, 2024 when we checked, and it includes a section on 42 CFR Part 2. Your contract with Kipu decides which version applies to you.
Kipu has an API, but access is for Kipu clients and developers working with a client, by API key, and Kipu says API use is a paid service. The endpoint documentation is not published openly.
Sources
- Kipu Health, homepage (opens in a new tab) (checked )
- Kipu Health, Behavioral Health CRM (opens in a new tab) (checked )
- Kipu Health, API (opens in a new tab) (checked )
- Kipu help center, API Requests (opens in a new tab) (checked )
- Kipu Health, Business Associate Agreement (opens in a new tab) (checked )
- Google, HIPAA and Google Analytics (opens in a new tab) (checked )
Not legal advice. This page reports what the vendor publishes. Nothing here implies a partnership with Kipu Health. Confirm plans and the BAA in writing with the vendor, and let your compliance lead or counsel decide what counts as PHI in your workflows. For the terms, see BAA, PHI, HIPAA and 42 CFR Part 2 in the glossary.
