Cody Blevins
I help teams make integrations predictable: clear contracts, readable operations, and delivery paths that stay calm when the system gets messy.
Healthcare integrations, AI platform boundaries, and reliability programs for teams that need crisp execution.
Healthcare API, HL7v2, and FHIR workflows
Production support and reliability ownership
Incident and escalation telemetry improvements
Cody site map at a glance
If you want the quickest tour, these are the cleanest paths through the site.
Services
See engagement shapes, timelines, and where I add leverage.
Products
See where each product surface fits and why it matters.
Playground
Run hands-on validation and workflow tooling.
Writing
Read implementation notes and case studies.
About
See professional background and operating principles.
Resume
Use the concise version for scope, systems, and delivery history.
Contact
Talk about an engagement, collaboration, or a thorny system.
Consulting Fit
Start with the services page for engagement shapes, diagnostic work, and the problems I am best suited to help untangle.
Execution Proof
Read case studies and writing to see architecture, delivery, and incident thinking.
Background
Use the about page and resume when you want the shorter version of scope, leadership style, and operating range.
Integration Leadership with Operator Instincts
I bridge architecture, implementation, and operations so teams can ship integrations that stay reliable in production.
Healthcare Integrations
Designed and operated healthcare API integrations across HL7v2 and FHIR workflows.
Reliability & Operations
Owned API incident loops, escalation handling, and reliability telemetry improvements.
Technical Program Delivery
Led complex migration and upgrade programs with clear risk and dependency management.
Projects & Labs
A representative slice of the systems, tools, and experiments I keep running in public.
Interoperability, Reliability, and Delivery
Practical notes from healthcare integrations, platform reliability work, and cross-functional delivery.
April 20, 2026
The First 90 Days: Introducing AI-Assisted Dev to a New Team
How I would roll out AI-assisted development on a team that has not standardized: what to do in week one, what to earn the right to argue about later, and what almost always goes wrong.
April 20, 2026
A One-Page AI Usage Policy That Actually Works
A short, adoptable AI usage policy for engineering teams: what to put on the page, what to leave off, and why the policy matters less than the habits it makes explicit.
Let's Solve the Hard Integration Work
If your team needs stronger integration architecture, better operational signal, and faster incident recovery, I'd love to help.