A small cohort for healthcare PMs, clinicians, and builders who want a working system — not another course library. The exact playbook I used to ship HealthClaw, AINPI, and 25+ other projects with Claude Code + FHIR.
Everything below was built solo, on nights and weekends, using the same system you'll learn. Most would normally take a team months.
PHI redaction, step-up auth, MCP tool validation, Curatr data-quality eval. Running on Railway with full test coverage.
An audit of the CMS National Provider Directory with five data-quality findings. Pre-registered methodology, published findings.
Patient access app with SMART on FHIR auth. Built end-to-end in weeks, not quarters.
Breast cancer screening, ADHD med monitoring, LDL compliance. Live CQL measures running against a real FHIR server.
Sigma dashboards built on FHIR-derived data. The pattern that powers my day-job platform.
What's the one healthcare problem you can't get out of your head? That's what you'll build in this cohort.
You see the gaps clearly. You're tired of waiting two quarters for engineering capacity to validate an idea.
You know the workflow. You know what's broken. You don't want to learn a CS degree before you can prototype.
You can code. FHIR has a learning curve. We compress it from months to weeks.
You're shipping a healthcare product and AI-assisted dev is your unfair advantage. Use it well.
If you want to watch videos and feel productive, this isn't it. Every week ends with you having shipped something, or you've been honest with yourself about why you didn't.
You can stop at any stage. The intro call alone is worth your time — you'll leave with the methodology whether you join or not.
I'm a senior PM at a national pharmacy data platform by day, and the founder of FHIR IQ by night. Over the past 18 months I've shipped 25+ healthcare AI projects solo using Claude Code, FHIR, and a system I refined the hard way.
Before that: Director of FHIR Data Analytics at a health tech startup. Before that: building the data layer at b.well Connected Health, powering Samsung Health, Google Fitbit, and major health systems. Roughly 15 years in this industry.
I'm not selling a secret. I'm selling time — the months I've already spent figuring out what works, so you don't have to. I've taught this in 1:1s. I'm formalizing it into a cohort because the demand is there and the timing is right.
Speaking at HL7 DevDays Minneapolis, June 2026. Host of Out of the FHIR podcast. Author of the FHIR IQ Playbook on Substack.
Tell me a little about you and what you want to build. I'll reach out within 48 hours to schedule.
This is a small group on purpose. I want to know everyone's project well enough to actually help unstick them.
If the cohort isn't a fit after the intro call, no pressure. You'll still leave with the methodology and a clear next step on your project.
2–3 hours per week. One group call, one builder session you can attend live or watch on replay. Anything more is up to you — most people ship faster the more they put in.
No. The whole point of the system is that you don't need to be a full-time engineer to ship real software. If you can read a paragraph and follow instructions, you can do this. Engineers benefit too — the FHIR-specific patterns alone are worth it.
No. There are free tutorials all over YouTube. This is the playbook for shipping real healthcare projects — how to scope, prompt, validate, deploy, and not get stuck. Claude Code is the tool. The system is the value.
We cover safe development practices, PHI redaction patterns, and architecture for compliant builds. None of the exercises require you to use real PHI — we use synthetic FHIR data throughout.
Cancel anytime. The intro call is free. The first-month $29 is non-refundable but you keep all the resources. Months 2+ at $99 are month-to-month, cancel whenever.
If you want a passive course you watch at 11pm and feel good about, this isn't it. We ship things. If you're not willing to actually start a project, your money is better spent elsewhere.
Even better. This cohort is structured so you'll show up to DevDays with something built — and people will want to talk to you about it.