DOMAIN / REVENUE CYCLE FOCUS / AI ENABLEMENT + EVALUATION

Revenue cycle intelligence for healthcare AI.

I help turn real-world RCM judgment into AI systems that can actually do the work.

RCM BRAIN FIRST. AGENT SECOND.

PHOTO / TBD professional photo
goes here
ROLE RCM + AI
MODE IN THE WEEDS

The model isn't
the hard part.

Knowing what right looks like is.

Healthcare AI doesn't operate in a vacuum. Revenue cycle work depends on context, evidence, payer behavior, sequencing, judgment, and knowing when the available information isn't enough.

That's where I work.

Domain expertise, translated.

01

RCM Intelligence

Real-world revenue cycle expertise that defines what competent work should actually look like.

DOMAIN KNOWLEDGE
02

AI Evaluation

Testing outputs, finding failure modes, challenging assumptions, and separating plausible answers from defensible ones.

TEST + VALIDATE
03

Workflow + QA

Translating specialist judgment into processes humans and agents can execute, evaluate, and improve consistently.

SYSTEM DESIGN

Okay, but what are we actually talking about here?

AI can execute a workflow. RCM expertise determines whether it's the right workflow.

My work sits between revenue cycle operations and the systems being built to perform, evaluate, or support that work.

Explore RCM + AI

RCM Brain First.
Agent Second.

Automation should inherit domain expertise, not replace the need for it.

See the full approach →
01 Investigate
02 Define
03 Translate
04 Pressure Test
05 Validate
06 Learn

Notes from inside the work.

All lab notes →
LAB NOTE / 001 AI QA / RCM

Why AI QA in RCM Can't Be Reduced to “Did the Agent Complete the Task?”

A completed workflow isn't necessarily a correct one.

Read note →
LAB NOTE / 002 DOMAIN EVALUATION

The Difference Between a Plausible RCM Answer and a Defensible One

Sounding right and being supportable are not the same thing.

Read note →
LAB NOTE / 003 FAILURE MODES

Five Ways an RCM Agent Can Be Technically Correct and Operationally Wrong

Because execution is only one part of the outcome.

Read note →
SECONDARY PHOTO / TBD

I spent years doing the work before I started teaching AI how to do it.

My background is in healthcare revenue cycle operations. Today, I work at the intersection of RCM domain expertise, AI enablement, agent evaluation, QA, and workflow design.

I care less about whether an AI system can produce an answer than whether that answer survives contact with the real operational problem.

More about me →

Building AI for healthcare revenue cycle?

I'm interested in the systems trying to make complex healthcare operations more intelligent, reliable, and scalable.