Debates, juries, blind panels, refinement rounds, or whatever deliberation shape you define, with several models arguing it out.

I built fhirHydrant so MCP-compatible AI clients could talk to a real FHIR server: SMART Backend Services auth, metadata-aware search and CRUD, compact responses, FHIRPath filtering. The proof of concept ran against Epic.

Two packages. @fhirstarter/backend handles SMART Backend Services auth for any FHIR client — JWT assertion, JWKS, automatic token refresh. @fhirstarter/ehr is a thin, dependency-free EHR-launch library with Vue and React components. A standalone-launch package might follow if I ever find a reason to write it.

Modern JavaScript for wiring a web app into Epic's Active Guidelines platform without the boilerplate.

A simple PHP client for SMART on FHIR — the standard API for integrating an application with any modern healthcare system. As far as I know it's the premiere FHIR library for PHP; there weren't many to choose from.

Strangely, this is probably my most-used thing. Forks and copied snippets of it are still floating around.

Cerner's MPages were originally static. They couldn't talk to the backend without a full reload.  So I hacked their code until I understood how the Cerner Command Language (CCL) layer worked, then built XMLCclRequest — an object modeled on the browser's XMLHttpRequest that allows an MPage to call CCL asynchronously.

I released it in 2009 as part of mPagesJS on SourceForge and presented it with David Stone at that year's MPages Development Conference. Then I gave the code to Cerner. They shipped it as-is, with my name on it, built into MPages 2.0 — you didn't need my file anymore, it was just there. Their own developers were still calling it a native framework function a decade later, and people are still writing wrappers around it.