Skip to main content

Cody BlevinsHealthcare Integration ArchitectI build healthcare data integrations and the tools to test and support them.

HL7v2, FHIR, X12 EDI, and APIs across provider and payer systems, from the first data contract through ongoing operations. I've held manager-level integration roles at athenahealth and Devoted Health, about three years in all, and I stay hands-on in the code. I also run the platform I build on: MCP tooling for coding agents, a merge operator that gates their work, and self-hosted inference on AMD GPUs.

Cody Blevins
Marion, Virginia · Remote, U.S.
Selected work

Integration tools and the platform behind them

Independent projects for healthcare data exchange, file validation, and cluster operations. Try the browser tools or read the source; the full list is on the selected-work page.

  1. 01

    fi-fhir

    Parses HL7v2, X12 EDI, and CSV into semantic events such as patient_admit and lab_result, then routes them through configurable workflows with FHIR R4 output. The playground runs the real kernel in your browser as WebAssembly.

    Go · Healthcare · HL7v2 · FHIR

  2. 02

    edilint

    One static binary that gates outbound X12, HL7v2, EDIFACT, delimited, and fixed-width files in CI, with every X12 rule cross-referenced to the TA1 or 999 code a trading partner would return.

    Go · Healthcare · X12 · HL7v2

  3. 03

    FlexInfer

    Kubernetes-native GPU scheduling and model serving across vLLM, Ollama, and llama.cpp. It runs the inference behind this site.

    Go · Kubernetes · LLM · gRPC

  4. 04

    Loom Core

    A Go daemon that manages MCP servers and agent memory, plus Mills, the gated pipeline that plans, implements, tests, and merges work on the projects above.

    Go · MCP · Kubernetes · GitLab

Professional focus

Healthcare integrations, built and operated

I work across implementation, partner coordination, and ongoing support, and I've led that work in manager-level roles.

  1. 01

    Healthcare data exchange

    HL7v2, FHIR, X12 EDI, and API integrations across provider and payer systems.

    Interface support, API engineering, and architecture, plus about three years in manager-level integration roles

  2. 02

    Integration tooling

    fi-fhir parses healthcare data into structured events; edilint checks EDI and flat files before delivery.

    Independent Go projects with source, tests, and documentation

  3. 03

    Platform engineering

    K3s on Harvester, Flux GitOps, Prometheus/Grafana/Loki, self-hosted GitLab CI, and GPU inference.

    The homelab behind my independent projects and this site

Delivery pipeline

Shipped by the factory

The tools above are maintained with Mills, an agent delivery pipeline I built and operate: its gates refuse work that fails a check, and escalations are counted, not hidden.

30 days to Oct 30, 2026, across every repository Mills works in: 417 of 913 runs merged, 96% of gate evaluations passed, and 290 escalated.

Live systems

The systems behind the work, read now

The factory that maintains these tools, the GPUs that serve this site, the cluster underneath, and the MCP servers my agents can reach. Each row reads the same sanitized public API as the page it links to and says whether its figure is live or a saved snapshot.

  1. Factory

    The Mills delivery pipeline: every run's stages, gates, retries, and cost over the last 30 days.

    417merged of 913 runs
    Snapshot
  2. Inference plane

    Open models on self-hosted GPUs behind an OpenAI-compatible gateway, with the engine and hardware of each one that is warm.

    —models warm
    Unavailable
  3. Cluster

    The K3s cluster that serves this site: node readiness, GPUs, and the health score FlexDeck computes from them.

    —nodes ready
    Unavailable
  4. MCP fleet

    The Go MCP servers Loom Core exposes to coding agents, mapped by category with the tools each one lets an agent call without asking.

    57servers in 86 categories
    Snapshot
Writing

Interoperability, reliability, and delivery

Practical notes from healthcare integrations, platform reliability work, and cross-functional delivery, starting with the interoperability notes.

  1. revised Nov 11, 2026

    Professional · 7 min read

    A Production Playbook for Healthcare API Integrations

    A practical operating model for healthcare integrations: explicit contracts, safe delivery, observable decisions, and support loops that improve the product.

    healthcare · apis · reliability · support-engineering

Next step

Evaluating my work?

I'm looking for my next full-time role, leading or building healthcare integration teams or in platform engineering. The selected-work page links to source, the resume covers the history, and the contact page is the fastest way to reach me.