Built for health systems, payers, and digital health companies

Clinical AI agents that protect PHI by design.

Health systems and payers are deploying agents across prior auth, revenue cycle, and care coordination. The HIPAA Security Rule NPRM (proposed January 2025) and CMS-0057-F (electronic PA operational requirements effective January 2026) are reshaping what compliant AI infrastructure looks like. Record is built to meet that bar.

0standing credentials held across EHR, pharmacy, or payer systems
Relevant regulations
HIPAA / HITECHCMS-0057-FFalse Claims ActJoint Commission21st Cures Act
Agent Use Cases

Agents you can deploy today.

Every agent ships with Cedar policies pre-configured for healthcare compliance requirements. Deploy in minutes, not quarters.

01

Prior Authorization Agent

Submits and manages prior auth requests across payer portals, meeting CMS-0057-F's 72-hour expedited and 7-day standard response requirements. Queries EHR with JIT credentials scoped to the specific patient and auth type. Routes denials and peer-to-peer requests to clinicians via HITL — ensuring physician involvement before any adverse coverage determination.

02

Revenue Cycle Coding Agent

Reviews clinical notes, assigns ICD-10 and CPT codes, catches documentation gaps, and submits claims. Flags corrections for coder review before resubmission — never auto-correcting without human sign-off. Systematic AI coding errors that cause upcoding or undercoding create False Claims Act exposure; human review gates prevent that.

03

Clinical Documentation Agent

Transcribes ambient clinical conversations and structures SOAP notes. All PHI is processed through Gate 2 — the AI Gateway applies PHI sanitization before sending context to any LLM provider, addressing the core HIPAA prohibition on disclosing PHI to third parties without BAA coverage.

04

Care Coordination Agent

Identifies high-risk patients, coordinates specialist referrals, and manages care transitions across payers and providers. Routes all care plan modifications through clinician approval gates with full timestamped audit trails — consistent with both HIPAA minimum-necessary requirements and Joint Commission care coordination standards.

05

Medication Reconciliation Agent

Reconciles medication lists across admissions, discharges, and transfers by querying pharmacy systems, EHR, and PBM with separate JIT credentials per system — each expiring after the specific reconciliation task, never persisting between patient encounters.

The Challenge

Standard AI architectures violate HIPAA's minimum-necessary access principle at scale — agents query EHR systems with standing credentials that expose far more PHI than any single task requires. HHS's proposed HIPAA Security Rule NPRM (published January 2025, under review) would eliminate the required/addressable distinction and make role-based access controls, encryption, and immutable audit logs mandatory for every system touching PHI. CMS-0057-F imposes strict PA response time requirements starting January 2026 that are driving rapid agent adoption in utilization management. Record's JIT credential broker enforces minimum-necessary access per task — not per session, not per role.

How Record Helps

Governance built for healthcare.

01

Minimum-necessary PHI access, enforced per task

Cedar policies define exactly which PHI fields an agent may access for each workflow type. A prior auth agent working on Patient A can access the specific diagnosis and benefit codes required for that authorization — nothing more, nothing else. HIPAA's minimum-necessary standard enforced as a hard gate at the Kernel Sandbox, not as a policy guideline agents can reason around.

02

Gate 2 as your HIPAA-compliant AI proxy

All LLM interactions route through Record's AI Gateway with BAA coverage. PHI is sanitized before reaching any model provider — addressing the most common HIPAA compliance failure in healthcare AI: sending identifiable patient data to external APIs without the contractual safeguards HIPAA requires.

03

Physician-in-the-loop for clinical decisions

Multiple states have enacted or proposed legislation restricting AI as the sole basis for treatment or coverage decisions. Record's HITL gate structurally enforces physician or clinician review before any care plan modification, prior auth determination, or claim action — regardless of what the agent recommends.

04

Zero standing credentials in agent memory

Epic, Oracle Cerner, and Athenahealth credentials are minted per task and auto-revoked on completion. Agents never hold access tokens between tasks — eliminating the most common PHI breach vector in healthcare AI: long-lived API credentials persisting in agent memory, config files, or logs.

Three gates. Every action. Zero exceptions.

Every agent action passes through all three enforcement layers simultaneously — not just one. Here's what that means for healthcare.

Gate 1
Agent Harness

Cedar policy enforces patient-level PHI access scoping per workflow type — a prior auth agent working on one patient cannot access any other patient's record under any circumstance. HITL required for any action that modifies a care plan, order, or coverage determination, consistent with state legislative requirements for clinical AI oversight.

Gate 2
AI Gateway

PHI sanitization applied before every LLM call — identifiable patient data stripped before reaching any model provider, addressing HIPAA's prohibition on third-party PHI disclosure without BAA coverage. Record's AI Gateway acts as the HIPAA compliance boundary between your EHR data and external AI providers.

Gate 3
Kernel Sandbox

eBPF sandbox intercepts all file I/O and network connections — PHI cannot be written to disk, sent to unauthorized endpoints, or exfiltrated through any path outside Cedar policy scope. Provides the technical access controls and network monitoring that HHS's proposed HIPAA Security Rule NPRM would make mandatory.

Ready to govern agents in Healthcare?

See how Record works for your team in a 30-minute demo.