hegl for healthcare
Work through payer paperwork without adding headcount.
hegl is an AI agent platform for healthcare admin teams. It handles prior authorizations, denials, eligibility and credentialing paperwork on top of the systems you already use, and brings a person anything that needs clinical or billing judgment.
Onboard your agent
Claude Code
/plugin marketplace add Katch-AI/hegl-plugin /plugin install hegl
Codex
codex plugin marketplace add Katch-AI/hegl-plugin Then install hegl from /plugins. Codex asks you to authorize it in your browser on first use.
Quick start
Start with "list my Hegl organizations", then: /hegl:build [agent] Start building an agent, or pick up where the build stopped. /hegl:feedback [agent] See what people complained about and improve the agent on it. /hegl:fix-errors [agent] Find out why runs are failing and fix it. In Codex and OpenCode, ask in words, e.g. "fix the errors on my agent". Any other MCP client: add the MCP server https://app.hegl.ai/mcp
- Every read, decision and write logged
- Tested on work your team already closed before it goes live
- Escalates to a person when it is not sure

Use cases
What healthcare admin teams run through hegl
Most healthcare admin is reading one document against another. A payer’s criteria against a chart note. A denial against the claim. An application against a provider’s file. hegl does the reading and the assembling, and brings a person the calls that need judgment.
Prior authorization requests
Payer criteria checked against the clinical documentation before anything is sent.
hegl checks what each request needs, assembles the packet, and flags what is missing.
Denial triage and appeals
Each denial needs its reason read and a call made: appeal, correct or write off.
hegl sorts denials by reason, pulls the supporting records, and drafts the appeal for review.
Eligibility and benefits checks
Coverage confirmed before the visit, not after the claim comes back.
hegl reads the eligibility response against the schedule and flags what does not line up.
Credentialing and enrollment
Applications, licences and attestations gathered, filed and kept current.
hegl assembles each file, tracks every expiry date, and chases what is missing.
Referral and intake processing
Referrals arriving as PDFs and emails that have to become a clean record.
hegl reads them, fills the intake fields, and routes incomplete ones back.
Claim edits and holds
Claims stopped for missing or mismatched information.
hegl fixes what your rules cover and sends the rest to a coder with the reason.
Payment posting exceptions
Remittances that do not match what was expected.
hegl clears the routine ones and brings billing the rest, work attached.
Patient and payer correspondence
Letters and requests that need an accurate answer on time.
hegl drafts from the account record. A named person approves before it goes.
- Medical necessity checks
- Auth status follow-up
- Retro auth requests
- Denial reason codes
- Timely filing deadlines
- Coordination of benefits
- Secondary claims
- Medical records requests
- Re-attestations
- Licence expiry tracking
- Payer enrollment forms
- Underpayment flags
- Write-off review
- Appeal deadline tracking
Your systems
Nothing to rip out
hegl runs on top of what your team works in today: the billing system, the inbox, the document store. It reads and writes only through the access you approve.
No migration.
Records stay where they are. hegl works through the connections you approve.
No engineers.
A revenue-cycle or practice lead describes the work. We connect the systems with you on a call.
No tools replaced.
hegl works alongside the clearinghouse and software you already pay for.
The fit
Why this work fits
The rules are written down. Every payer writes them differently.
Payer policies, edits and appeal requirements are published, but they vary payer by payer and change through the year. hegl applies the version your team works to and flags the case that does not fit it.
The judgment lives with your best biller.
Which denials are worth appealing, what wording works, when to call instead of write. hegl learns it from your team’s corrections and keeps it when people move on.
You already have the answer key.
Every worked auth, appeal and posting is an example with a known outcome. hegl is tested against them before it goes live and after every change.
When it is unsure
What happens when it is wrong
It asks.
When an item does not match what it has seen, it stops and asks the person who owns it. It does not guess.
It remembers.
Every answer becomes a permanent test. Accuracy goes up with use, not down.
It shows its work.
Every decision carries its inputs, its reasoning, and who overrode what. The audit trail is built in.
Getting started
How you start
Describe the work.
Someone who does the work talks it through. hegl writes the spec.
Test on your history.
hegl runs against work your team already finished. You see where it agrees.
Go live on your call.
It runs alongside your team, escalating when unsure. You widen it when ready.
FAQ
Frequently Asked Questions
hegl is an AI agent platform that runs healthcare administrative work, such as prior authorizations, denial follow-up, eligibility checks and credentialing paperwork, on top of the systems a team already uses. It reads, checks and drafts, and escalates anything that needs clinical or billing judgment to a person.
It stays in your systems. hegl reads and writes only through the connections you approve, and every read, decision and write is logged. Ask us for our current security documentation.
No. It checks documentation against the criteria and rules you give it and prepares the work. Clinical judgment, coding decisions and anything sent on a patient’s behalf stay with your staff.
It prepares the request and the packet. Where the submission route can be connected, hegl sends it once a person approves; where it cannot, the finished packet is queued for your team.
Before go-live, hegl runs on work your team already completed and you see where it agrees. After, every correction becomes a permanent test. We report a monitored error rate, not a promise of zero.
Email, document storage and the systems your team works in, through connections you approve. Anything with an API can be connected directly. Nothing has to be migrated.
Security & compliance
Secure by design
- SOC 2Type IIIn progress
- HIPAACompliant
- CASAApproved
- GDPRCompliant
Other teams
The same loop, other work
- Claims intake and triage
- Coverage verification
- Submission review and appetite matching
- Invoice processing and exception handling
- Expense report review
- Payment reconciliation
- KYC and alert reviews
- Contract review against playbooks
- License and filing deadlines
