Selected Work

Format-agnostic pipeline that parses legacy healthcare formats (HL7v2, X12 EDI, CSV) into semantic events like patient_admit and lab_result, then routes them through configurable workflows. Integration logic reads in workflow terms instead of PID.3.1.

Includes staged parsing with Source Profiles, FHIR R4 output, a GET /metadata CapabilityStatement checked against implemented mappings, and CI coverage gates. The Mapping Studio and remaining 1.0 release work are documented in the case study.

The playground runs the real fi-fhir parsing and FHIR mapping kernel, compiled to WebAssembly, in your browser: paste an HL7v2 message and get its segments, semantic events, diagnostics, and FHIR transaction Bundle. It ships synthetic samples only, and nothing you paste leaves the page.

Live demo: the fi-fhir IDE with a preview-only identity — paste synthetic HL7v2, no data is stored.

Single static binary that gates outbound files in CI or a send script: X12 envelope integrity with control-number and segment-count recounts, invisible and lookalike character detection, terminator consistency, declared-versus-actual trailer counts, and fixed-width layout drift.

48 rules across X12, HL7v2, EDIFACT, delimited, and fixed-width files, with every X12 rule cross-referenced to the TA1 or 999 code a trading partner would return for it. v0.3.0 added fmt, fix, diff, and stats subcommands, plus an MCP server so a coding agent can lint the files it generates. Zero dependencies, JSON and SARIF output, CI-friendly exit codes, tested on a three-OS matrix. Built with agentic engineering under adversarial review, and the review is in the commit history.

Automatic hardware discovery and labeling, benchmark-driven scheduling via CRDs and a scheduler extender, multi-backend model serving (vLLM, Ollama, llama.cpp), and dynamic LoRA adapters. Runs in production on my own cluster.

A Go daemon plus VS Code and Zed extensions that manage Model Context Protocol server lifecycles, sync configuration across supported AI coding tools, and provide persistent agent memory across sessions. This is the tooling I use to build everything else on this page.

Mills sits on top: a Kubernetes operator that plans backlog in a council, implements in sandboxed pods, runs gates (scope, protected paths, secret scan, tests pinned to the pushed commit), opens the merge request, watches CI, and merges under a policy held in GitOps with a kill switch and per-repo budgets. Every run leaves stage records with cost, gate verdicts, and the commit that was actually tested. fi-fhir and edilint are now maintained through it.

Self-hosted system of record for vendor-integration work: projects and vendors, artifact capture with SHA-256 evidence hashing and data-classification levels, decisions, risks, milestones, Gantt/Kanban/status views, hybrid FTS5 plus semantic search, an MCP server surface for AI agents, Prometheus metrics, and a formal threat model gating what data may enter. I use it daily to run real multi-vendor integration programs.

Roughly 300 routes handling multi-source ingestion (Gmail classification pipeline, feeds, calendars), five storage tiers (Postgres, Neo4j graph, Qdrant vectors, Redis, MinIO), LangGraph agent workflows for document composition, and ARQ background jobs. About 140K lines.