Policy-compiler agent

Turns written rules into checks on every action.

Takes inPolicy text, protocols
The agentPolicy compiler
Hands backVersioned rules plus tests

Checked against clinicians

Clinician and compliance sign-off; rule tests against labelled cases.

Where a person decides

Policy owner approves every rule version.

Works on

Voice, RCM, payer, EHR agents.

On the roadmap. Tell us if you need it sooner. Reviewed .

The problem it solves

Rules live in PDFs: scope of practice, payer policy, state disclosure laws. Models don't reliably follow them, and nobody checks every action.

How it works

01

Read the policy

The agent turns written rules into precise, testable checks.

02

Review with your team

Compliance or clinical leads approve each check.

03

Run on every action

Checks run automatically on outputs and actions, deterministically.

An example, illustrative

Before

Policy PDF: 'Disclose AI use to the patient.'

With the agent

Check: every patient message includes the disclosure. 3 failures this week.

What it needs from you

The written policies and a named approver.

Its limits

A check is only as good as its reading of the policy, so a human approves each one.

Quick answers

What does the policy compiler do?

Compile written rules (scope of practice, payer policy, state disclosure, authority limits) into checkable gates.

How is the policy compiler checked against clinicians?

Clinician and compliance sign-off; rule tests against labelled cases.

Does this give legal advice?

No. It converts rules you provide into checks. Legal interpretation stays with your counsel.

Which rules work best?

Clear yes-or-no rules, such as required disclosures, code validity and scope limits.

What can the policy compiler not do?

Policy owner approves every rule version. No agent makes a clinical decision.

Get early access to the policy compiler