About
What is Delegent?
By Harsh Mehta · Last reviewed:
Delegent is an identity, delegation and audit layer for healthcare AI agents. It gives each agent its own identity and a single-use pass for every call to a payer or EHR API. It checks that the clinic allowed the action, holds risky actions for a person's approval, and keeps a tamper-evident record of which agent acted, for whom and why. It is for companies whose agents do prior authorization, eligibility, claims and patient access work. Delegent is pre-launch and looking for its first design partners.
Delegent at a glance
| Fact | Detail |
|---|---|
| Name | Delegent, spelled d-e-l-e-g-e-n-t. It is a company name, not a misspelling of "delegate" or "diligent." |
| What it is | Identity, delegation and audit for healthcare AI agents. |
| Who it is for | Healthcare AI agent companies that need to get through hospital security reviews and onto payer APIs |
| Status | Pre-launch, looking for its first design partners |
| Founder | Harsh Mehta |
| Standards | FHIR R4, SMART Backend Services, UDAP, TEFCA, CMS-0057-F and HIPAA |
| Website | usedelegent.com |
| Contact | harsh@usedelegent.com, or @usedelegent on X |
The problem it solves
Every request for patient data has to answer six questions: who are you, who sent you, what do you want, why, is this allowed, and what happened. Most AI agents answer with a borrowed login, so the payer's log says the doctor did it.
In a survey of 250 US healthcare leaders (Imprivata, run by Vanson Bourne, September 2026), 35% said their AI agents run on a clinician's delegated login. Another 16% said they use generic or shared accounts.
That is hard to defend in a hospital security review, and it is a poor fit for the payer prior authorization APIs that open on January 1, 2027, which expect registered software and not a person's login. The CMS-0057-F guide explains the deadline.
How it works
Your agent points its FHIR client at Delegent. Here's what happens to a single submission, start to finish.
- Your agent asks. It opens a task: which patient, for which clinician, and why.
- Delegent checks permission. The clinic's grant has to cover this agent, this purpose and this patient.
- A person approves. Submitting is risky, so it waits for a staff member's passkey.
- A one-call token goes to the payer. It works once, for this call only. Your agent never holds it.
- The record is written. Agent, person, purpose and result, chained so no one can edit it later.
One line changes in your code. Your FHIR client keeps working. You swap the base URL for the one Delegent gives the task.
How it is secured
- Keys that never leave. Non-exportable keys, separate for every customer and every agent.
- Tokens that last one call. Short-lived and single-use. We never store them.
- No patient data at rest. We keep tokenized patient IDs, not clinical payloads.
- Tamper-evident audit. Hash-chained records a hospital reviewer can verify.
- BAA from day one. We sign BAAs as a subcontractor business associate.
- Passkeys for people. Every approver and every staff login uses phishing-resistant sign-in.
What Delegent is not
- Not a clearinghouse. A clearinghouse translates and routes transactions. Delegent doesn't touch payload formats. It supplies identity, authority, purpose and audit for whoever is calling.
- Not workforce identity. Okta, Entra Agent ID and AWS AgentCore manage agents inside one company. Delegent is built to sit next to them and to speak the healthcare standards payers and EHRs use.
- Not an EHR feature. An EHR governs agents inside that EHR. Delegent keeps the vendor-side record across EHRs and payers.
Who is building it
Delegent was founded by Harsh Mehta. In his words: "I build and run the sign-in and client-registration platform at a national health plan, the door software uses to get in. Delegent is the passport agents need to get through doors like it."
Read more
- Audit trails for healthcare AI agents: what the record has to show
- Getting a healthcare AI agent through a hospital security review
- How a healthcare AI agent should sign in to payer and EHR APIs
- CMS-0057-F for prior-auth agent companies: what changes January 1, 2027, and how your agent should sign in
Building a healthcare AI agent? Apply to be a design partner.
Questions
Is Delegent available today?
Not yet. Delegent is pre-launch and looking for its first design partners: healthcare AI agent companies that need to get live on payer APIs and through hospital security reviews.
Who is Delegent for?
Companies that build AI agents for healthcare work such as prior authorization, eligibility, claims and patient access. Hospital security teams and payer API teams are the people who read the records Delegent produces.
Does Delegent store patient data?
It keeps as little as possible: tokenized patient IDs and no clinical payloads. Calls pass through Delegent, so it signs business associate agreements as a subcontractor business associate.
Is Delegent the same as "delegate"?
No. Delegent is the name of a company and its product, at usedelegent.com. Search engines sometimes correct the spelling to "delegate."