OpenMed 3.0 is out: Apache-2.0 clinical AI that runs fully local and never falls back to the cloud. 422 open issues if you want in on 3.1
Hey r/LocalLLaMA! Maintainer here.
Some of you might remember OpenMed from our 1.8 post a few months back. Quick recap: it's an open-source (Apache-2.0) medical AI toolkit with one rule we never break: patient data stays on your machine. No API keys, no cloud calls, works offline. There are 2,200+ open models on Hugging Face, and they run with Transformers, ONNX, GGUF through your own llama.cpp, in the browser with WebGPU/WASM, or on a phone.
We just shipped 3.0, and it's a big one.
What's new
Most of OpenMed so far worked one document at a time: find the diagnoses in this note, strip the names out of that PDF. But a real patient is spread across clinic notes, hospital FHIR feeds, HL7 messages from another clinic, lab CSVs and imaging reports, and those sources disagree all the time. 3.0 adds Patient Journey, which stitches all of that into one timeline per patient, right on your own hardware.
The part I'm proudest of: it refuses to guess.
- A 99% identity match? Still not merged, a person reviews it. A wrong merge puts one patient's allergies in someone else's chart.
- Two sources disagree on a diagnosis? Both stay, flagged for review.
- A lab gets corrected from 6.8 to 4.4? Both are kept, and you can still read the record exactly as it was before the fix.
- A note only says "January"? It won't make up January 1st just to fill an OMOP column.
- Ask for a summary with a local model you haven't downloaded? It refuses. It never quietly calls a cloud API instead.
That last one is the whole philosophy. With clinical data, a silent fallback to a hosted model is a privacy decision nobody made.
Want to try it? The demo runs fully offline: five messy synthetic sources become one journey in about 0.07s.
pip install "openmed==3.0.0"
git clone --depth 1 --branch v3.0.0 maziyarpanahi/openmed
python openmed/examples/v3_golden_journey.py
Being honest about where it stands: the demo patient is synthetic, the summarization pipeline is synthetic-only in 3.0 (not ready for real patients yet), and this release doesn't ship new clinical model checkpoints. Think of it as the plumbing your local models plug into.
Now the ask: we need you!
148 PRs from 10 people went into 3.0, 46 of them from the community, and 3 folks made their very first contribution. 3.1 is being built in the open right now, with 422 open issues and 30 good first issues waiting. Some fun ones to start with:
- Add date and ID trap tests for low-resource languages (#3894)
- Teach the multimodal preflight to spot GIF, WebP and BMP files (#3833)
- Write an offline walkthrough of a federated round (#3882)
- Add runnable synthetic examples for the clinical workflow contracts (#3794)
If local AI for healthcare is your thing, come be part of it: pick an issue, say hi, and your name goes in the next release notes. Stars, bug reports and "this broke on my machine" reports help a ton too.
Repo: maziyarpanahi/openmed
Release notes: github.com/maziyarpanahi/openmed/releases/tag/v3.…
Good first issues: github.com/maziyarpanahi/openmed/issues
I'll be hanging out in the comments, ask me anything!
(English isn't my first language, so an LLM helped me write this post. The code, the release and every number in it are ours. 🤗)
158 points · 27 comments
Mentions
OpenMed 3.2 is out. Four new open disease models, one analyze_text call: GLiFormer Base and Large, GLiNER2.5 Base and Spanish. Apache-2.0, on CPU. Also new: Nepali IDs and UK postcodes in de-identification, and synthetic FHIR, OMOP, HL7 and C-CDA data. github.com/maziyarpanahi/openmed/releases/tag/v3.… t.co
@cgcorporation Pleasure! Please check out the github repo for OpenMed: maziyarpanahi/openmed
Good first issues: github.com/maziyarpanahi/openmed/contribute Repo, a star helps other developers find it: maziyarpanahi/openmed Every PR and its author is in the release notes: github.com/maziyarpanahi/openmed/releases/tag/v3.…
How the review packet works: github.com/maziyarpanahi/openmed/blob/master/docs… The code, Apache 2.0 (a star helps others find it): maziyarpanahi/openmed Synthetic bundles, no real FHIR server. Existing writers need the 3.0 to 3.1 migration guide to get these checks.
Terminology resolution in openmed 3.0.0: github.com/maziyarpanahi/openmed/blob/master/docs… Synthetic 3-concept ICD-10-CM subset. OpenMed bundles no vocabularies; you bring your own. Apache 2.0.
OpenMed 3.0 is out: Apache-2.0 clinical AI that runs fully local and never falls back to the cloud. 422 open issues if you want in on 3.1 Hey r/LocalLLaMA! Maintainer here. Some of you might remember OpenMed from our 1.8 post a few months back. Quick recap: it's an open-source (Apache-2.0) medical AI toolkit with one rule we never break: patient data stays on your machine. No API keys, no cloud calls, works offline. There are 2,200+ open models on Hugging Face, and they run with Transformers, ONNX, GGUF through your own llama.cpp, in the browser with WebGPU/WASM, or on a phone. We just shipped 3.0, and it's a big one. What's new Most of OpenMed so far worked one document at a time: find the diagnoses in this note, strip the names out of that PDF. But a real patient is spread across clinic notes, hospital FHIR feeds, HL7 messages from another clinic, lab CSVs and imaging reports, and those sources disagree all the time. 3.0 adds Patient Journey, which stitches all of that into one timeline per patient, right on your own hardware. The part I'm proudest of: it refuses to guess. - A 99% identity match? Still not merged, a person reviews it. A wrong merge puts one patient's allergies in someone else's chart. - Two sources disagree on a diagnosis? Both stay, flagged for review. - A lab gets corrected from 6.8 to 4.4? Both are kept, and you can still read the record exactly as it was before the fix. - A note only says "January"? It won't make up January 1st just to fill an OMOP column. - Ask for a summary with a local model you haven't downloaded? It refuses. It never quietly calls a cloud API instead. That last one is the whole philosophy. With clinical data, a silent fallback to a hosted model is a privacy decision nobody made. Want to try it? The demo runs fully offline: five messy synthetic sources become one journey in about 0.07s. pip install "openmed==3.0.0" git clone --depth 1 --branch v3.0.0 maziyarpanahi/openmed python openmed/examples/v3_golden_journey.py Being honest about where it stands: the demo patient is synthetic, the summarization pipeline is synthetic-only in 3.0 (not ready for real patients yet), and this release doesn't ship new clinical model checkpoints. Think of it as the plumbing your local models plug into. Now the ask: we need you! 148 PRs from 10 people went into 3.0, 46 of them from the community, and 3 folks made their very first contribution. 3.1 is being built in the open right now, with 422 open issues and 30 good first issues waiting. Some fun ones to start with: - Add date and ID trap tests for low-resource languages (#3894) - Teach the multimodal preflight to spot GIF, WebP and BMP files (#3833) - Write an offline walkthrough of a federated round (#3882) - Add runnable synthetic examples for the clinical workflow contracts (#3794) If local AI for healthcare is your thing, come be part of it: pick an issue, say hi, and your name goes in the next release notes. Stars, bug reports and "this broke on my machine" reports help a ton too. Repo: maziyarpanahi/openmed Release notes: github.com/maziyarpanahi/openmed/releases/tag/v3.… Good first issues: github.com/maziyarpanahi/openmed/issues I'll be hanging out in the comments, ask me anything! (English isn't my first language, so an LLM helped me write this post. The code, the release and every number in it are ours. 🤗)