medicinetalk
Adam Johnson
More in life sciences and medicine
- Seyed Yahya Shirazineuroscience, 2 Apr 2026
- Rob Patrogenomics, 15 Feb 2026
- José R. Penadésmicrobiology, 4 Mar 2025
What they did
Johnson presented to the OHDSI community how he uses Claude Code to develop transportable analytic code for prognostic modelling on OMOP data, constrained by a CLAUDE.md that enforces OHDSI conventions. The environment is a Docker template with the HADES stack and numbered workflow steps; concept IDs follow a three-tier lookup and are tagged "[vocab query]" or "[pretraining]". He also uses Claude Code as a "lab manager" to sync repositories, align studies with a shared template, validate setups, triage GitHub issues and edit Synthea modules.
In their words
"unconstrained LLMs actively undermine OHDSI standards."
"AI-generated IDs tagged [pretraining] with mandatory warning — never silently trusted"
"Instruction following is convention, not code"
Lessons they draw
- Make the guardrailed path the default: a template repo and environment encode best practice from day one (Johnson).
- Treat IDs the model produces from pretraining as untrusted; confirm against the live vocabulary and tag them (Johnson).
- Stated limitations: instruction following is convention not code, and there is no automated concept-ID cross-validation against the live vocabulary (Johnson).
- He asks whether instruction following is a sufficient enforcement mechanism for reproducible research (Johnson).
Limits of this account
Conference slides (some text from extracted PDF), no outcomes data; the speaker frames the approach as "a working answer" and unsure if it is "the right one".