No IT project. No changes to your Kipu® configuration. No new software for staff to learn — it's Claude, connected to the system of record. Here's the whole path, start to finish.
Someone with admin access to your Kipu instance, to generate API V3 credentials. If API access isn't enabled yet, your Kipu account manager can turn it on.
We recommend Claude Enterprise with a BAA signed between your organization and Anthropic — EMR answers appear in staff conversations, so that agreement matters.
That's the realistic end-to-end once the BAA is signed and your credentials are in hand: provision, paste into Claude, first question answered.
Your Kipu administrator generates API V3 credentials from your own instance: Settings → API management. You'll get three values — access_id, secret_key, and app_id.
The credentials stay under your control. They're issued from your instance, they're read-scoped by how we use them, and you can revoke them from Kipu at any time — every request is signed with your credentials, so revoking them severs the connection.
We sign a BAA, then validate your credentials live against Kipu — a real API call, not a form submission — so a typo surfaces in seconds, not on day three. Then we stand up your organization's private connector on its own subdomain:
A workspace admin adds the connector once in Claude's settings — Settings → Connectors → Add — and it's available org-wide. Each staff member signs in individually with their own work account, so access and audit stay per-person. Then someone asks the first question, and the census answer comes back before the meeting ends.
Your Kipu® user directory stays the access list. New hires appear after the next directory sync; departed staff lose access the same way — the sync runs nightly, and there's no separate user list to maintain.
Change someone's role or location assignments in Kipu and the connector follows. There is no second permission system to drift out of date.
There's no software installed at your facilities and no agent on staff machines. Staff use Claude; the connector lives on our infrastructure.
Each tool call is logged — who, which tool, when — with patient arguments and results deliberately excluded. Want the log? Ask and we'll export it for you.
Join the pilot cohort — from credentials in hand, you're about 15 minutes from your first answer.
Book a demo