WorkBy industry

Healthcare Operations. Agentic operations for the administrative weight of clinical care.

We ship to multi-site clinical groups and digital-health operators carrying an administrative load their clinicians cannot sustain. The agent reads inbound messages and lab results, drafts prior-auth documentation, generates the weekly operations report, and routes anything outside a tight refusal lane to a human within minutes. The agent never diagnoses, never doses, never sees PHI in the raw, and never sends without a clinician's signature. Operator-in-the-loop is the metric the practice publishes.

Begin a conversation Try the software

What we ship for this industryIndustry · Healthcare Operations

01
Refusal-lane-first design.
The clinical no-list — no diagnosis, no dosing, no decision language — is written before the first feature ships and audited against a held-out corpus.
02
PHI pseudonymized in ingest.
Patient identifiers are replaced with session-scoped tokens before reaching the agent's reasoning context. Every read is appended to an immutable audit log keyed to your HIPAA security officer.
03
Drafted, never sent.
Prior-auth letters, refill triage notes, and weekly reports are drafted by the agent and queued for the on-shift clinician to accept, edit, or decline with one click.
04
Reporting as a side effect.
The weekly operations report is generated continuously from the same audit log that gates the agent's reads — not a Friday afternoon FTE rebuild.

The software, as artifactAtlas · Clinical operations

Atlas. Click through it.

The console below is a composed view of the Healthcare system we ship. Tab between views, click rows to inspect agent reasoning, accept or override the proposed action. Every state change is local to your browser — no real client data, no remote calls — so you can poke without consequence.

Selected engagement

The work, redacted to the bone.

Anonymized by sector and region only — no name, no jurisdiction tighter than region, no detail that could identify a client by elimination. Methodology in engineering language, outcomes as numerals.

Agentic AI2026

A multi-clinic primary care group, US Southeast

An always-on clinical-operations agent that runs intake triage, prior-auth drafting, and weekly reporting — without ever practicing medicine.

Clinician-hours returned: 23 hrs/wk
Median prior-auth turnaround: 94 min
Refusal-lane integrity (audited): 100%

The group had grown to fifteen clinicians across four sites, and the administrative weight had begun to consume the nurses. Inbound patient messages waited hours for triage; prior authorizations sat for days before someone could draft them; the weekly operations report was a Friday afternoon that ate two FTEs. The engagement was a single autonomous operator that reads, drafts, and routes the administrative surface of the practice — bound by a refusal lane wider than its work surface, and forbidden from any output that constitutes clinical judgment. The agent reads. The agent drafts. The clinician decides.

Methodology

01
Refusal lanes before features
Wrote the no-list before the yes-list: no clinical decision-making, no medication advice, no diagnostic language, no PHI in raw form inside the reasoning context. The refusal lane is audited weekly against a held-out corpus.
02
PHI-aware ingest
Inbound messages and lab results are pseudonymized before reaching the agent — every patient identifier is replaced with a session-scoped token, every read is appended to an immutable audit log keyed to the practice's HIPAA security officer.
03
Drafted, never sent
Every prior-auth letter, refill triage note, and weekly report is drafted by the agent and queued for the on-shift clinician to accept, edit, or decline with one click. The agent learns from edits; it does not learn from acceptances.
04
Reporting as a side effect
The weekly operations report is not a separate task — it is generated continuously from the same audit log that gates the agent's reads. Friday afternoon becomes a five-minute review, not a two-FTE rebuild.

The agent reads, drafts, and routes. The clinician decides.

Source notes redacted · Client identification withheld by agreement

Build discipline

Hardened scaffold. Yours to shape.

The fundamentals of every system we ship are fixed by discipline. Everything above them is built around your business — your roles, your refusal lanes, your integrations, your shape.

The spine

Always there

Six engineering fundamentals that ship on every engagement, regardless of industry.

01
Refusal lanes before features.
We write the no-list before the yes-list. The boundary the system will never cross is documented and audited before the first feature ships.
02
Operator in the loop on every decision.
The agent reads, drafts, and routes. A senior human takes every high-stakes action. The integrity of that posture is the metric we publish.
03
Replayable event sourcing.
Every draft, every flag, every state transition is reconstructable from an audit-stamped event log. Bugs are diagnosable. Decisions are explainable.
04
Row-level security on every table.
Postgres + RLS, applied without exception. Anonymous access is gated, client access is scoped to client rows, operator access is audited.
05
Audit log streaming on day one.
Every read, write, and refusal is appended to an immutable log keyed to your senior operator — your security officer, your toolpusher, your managing partner.
06
Observable from day one.
Structured logging, error-tracking, telemetry, weekly digests. The system explains itself before someone has to investigate it.

Your shape

Built around you

Seven customization axes. Concrete, not cosmetic — every axis is a token, a policy, an integration, an audit.

01
Identity & branding.
Your logo, palette, microcopy, sender domain. Brand tokens — not theme pickers — so contrast and accessibility never break under your colors.
02
Role taxonomy.
Clinician, toolpusher, paralegal, dispatcher — your roles, not ours. The RLS scaffolding bends around the role names you actually use.
03
Refusal lanes.
Your no-list, signed off by your senior operator. Versioned. Auditable. Replayable against any past conversation.
04
Integration surface.
We plug into the systems you already run — EHR, rig event bus, DMS, TMS, payor portal — never the other way around. Inbound webhook, outbound idempotent on retry.
05
Workflow gates.
Approve, override, escalate. Gated by your roles, sequenced to your operations rhythm, never to ours.
06
Data shape.
Your schema, your types — not a generic JSONB blob trying to fit every customer. Migrations versioned, idempotent, single-transaction.
07
Audit policy.
Who sees what. How long it is retained. How it exports to your compliance officer when an auditor asks. SOC2, HIPAA, state-bar, IADC-aligned where the industry requires it.

Your shapeCustomization surface

v1 · per engagement

Multi-clinic primary care

Identitylogo · wordmark · token · sender

Logo
<your-logo.svg>
Wordmark
Atlas — Multi-Clinic
Accent
● locked to AA contrast· token-bound, never hardcoded
Sender domain
send.your-clinic.com

Rolesrole · access · refusal

Clinician
RW· refusal: no diagnosis
Nurse
RW· refusal: no dosing
Admin
RW· refusal: no PHI raw
Patient (portal)
R· system policy

Integrationsystem · adapter

EHR
Athena · v9 schema bound
Lab
Quest · HL7 ingest
Payor
Aetna PA · webhook v2

Auditpolicy · officer · export

Retention
7 years
Officer
security@your-clinic.com
Export
SOC2 CSV + JSON
Last review
2026-04-30

Same discipline. Different domain. Always your shape.

The capability behind it

Healthcare Operations is the room. Agentic AI is the capability we bring into it.

Read the Agentic AI discipline Every industry

Open the room

Bring healthcare operations to the practice. We’ll send back the brief.

A working session, a written scope, a clear success criterion. Then a portal URL, an intake, and the kickoff row.

Begin a conversation