RCM Intelligence
Real-world revenue cycle expertise that defines what competent work should actually look like.
DOMAIN KNOWLEDGEI help turn real-world RCM judgment into AI systems that can actually do the work.
RCM BRAIN FIRST. AGENT SECOND.
THE THESIS
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.
WHAT I BRING
Real-world revenue cycle expertise that defines what competent work should actually look like.
DOMAIN KNOWLEDGETesting outputs, finding failure modes, challenging assumptions, and separating plausible answers from defensible ones.
TEST + VALIDATETranslating specialist judgment into processes humans and agents can execute, evaluate, and improve consistently.
SYSTEM DESIGNRCM + AI
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 + AISELECTED WORK
METHOD / RCM BRAIN FIRST
Automation should inherit domain expertise, not replace the need for it.
See the full approach →FROM THE LAB
A completed workflow isn't necessarily a correct one.
Read note →Sounding right and being supportable are not the same thing.
Read note →Because execution is only one part of the outcome.
Read note →ABOUT ANNIE
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 →LET'S TALK
I'm interested in the systems trying to make complex healthcare operations more intelligent, reliable, and scalable.