Guardrails First: Engineering Member-Facing Health AI

Official Schedule Context

Everywhere else in the company, an AI pilot can reach production in weeks. For our member-facing

clinical assistant, it can't, and that single constraint redesigned our entire architecture. This is

a field report on building conversational AI in a regulated digital health setting, where "move fast

and break things" isn't a culture choice. It's a liability. We'll get concrete about what changes

when every output has to be clinically safe, auditable, and compliant: PHI is protected by

architecture, not policy. Production and non-production are hard-isolated, dashboards are sanitized,

and engineers outside the US never touch protected health information. Must-not-fail behavior never

lives in a prompt. Emergency escalation and intent routing run as deterministic rules at the top of

every conversation turn, before the model is consulted. If you can't afford to get something wrong,

you don't leave it to a probabilistic system. Clinical safety is a continuous eval layer. ~30 LLM-

as-judge evaluators score clinical accuracy, clinical safety, escalation routing, and recommendation

relevance, continuously, not once. Every output is auditable. Each turn, tool call, and reasoning

step is traced so outputs can be reviewed and meet regulated reporting obligations. The throughline:

in regulated healthcare, compliance constraints aren't a tax you pay around the architecture. They

become the architecture. We'll talk about why guardrails-first is the only way to ship member-facing

health AI, and why "painfully slow" is sometimes exactly right. (This is non-diagnostic, member-

facing AI. The talk is about engineering discipline under regulation, not medical claims.) Key

takeaways - In regulated health AI, "move fast" is the wrong default. Design for deliberate, careful

launches. - Must-not-fail behaviors belong in deterministic rules at the top of every turn, never in

the prompt. - Protect PHI through architecture: isolate prod from non-prod, sanitize dashboards,

restrict access by role and geography. - Make every output auditable. Trace each turn, tool call,

and reasoning step so safety is reviewable, not assumed. - Treat clinical safety as a continuous

LLM-as-judge layer, not a one-time gate.

No official session recording transcript was found by exact title match on the AI Engineer YouTube channel during this run.

Pending transcript synthesis when an official recording or confirmed matching video is available.