Skip to content
Main Site News Console

OpenMed 3.0 Released: A fully local, zero-cloud Apache-2.0 clinical AI—422 open issues ready for v3.1 contributors.

· Reddit · r/LocalLLaMA Translated
Reddit

Hey r/LocalLLaMA! I’m the project maintainer.

Some of you might remember our post for the 1.8 release a few months back. Quick recap: OpenMed is an open-source (Apache-2.0 licensed) medical AI toolkit built around one non-negotiable rule: patient data never leaves your local machine. No API keys, no cloud calls, runs fully offline. We currently have over 2,200 open-source models on Hugging Face, running via Transformers, ONNX, GGUF through local llama.cpp, in-browser via WebGPU/WASM, and even directly on mobile phones.

We just released version 3.0, and it’s a major milestone.

What’s New

Until now, most of OpenMed operated on one document at a time: extract diagnoses from this chart, redact patient names from that PDF, etc. But real-world patient data is scattered across clinic notes, hospital FHIR feeds, HL7 messages from other practices, lab CSVs, and imaging reports—often conflicting with one another. Version 3.0 introduces the Patient Journey feature, stitching all these fragmented data sources into a single, unified patient timeline right on your local hardware.

What I’m most proud of: it never guesses.

  • A 99% identity match? Still won’t merge automatically—it flags for human review. A single false merge could cross-contaminate one patient’s allergy history into another’s chart.
  • Conflicting diagnoses across two sources? It keeps both and flags them for review.
  • A lab result was corrected from 6.8 to 4.4? Both are preserved; you can always inspect the original pre-correction record.
  • A record only says “January”? It will never invent “January 1st” just to satisfy an OMOP field.
  • Requested a summary from a local model you haven’t downloaded yet? It simply refuses; it will never secretly fall back to a cloud API behind your back.

That last point reflects the philosophy of our entire project: when handling clinical data, silently falling back to a cloud-hosted model is effectively making unauthorized privacy decisions on the user’s behalf.

Want to give it a spin? The demo runs completely offline: stitching 5 messy synthetic sources into a patient journey takes about 0.07 seconds.

Terminal window
pip install "openmed==3.0.0"
git clone --depth 1 --branch v3.0.0 https://github.com/maziyarpanahi/openmed
python openmed/examples/v3_golden_journey.py

To be completely transparent about where things stand: the demo patients are synthetic, the summarization pipeline in 3.0 is currently only validated on synthetic data (not ready for production patient care), and this release doesn’t introduce new clinical model checkpoints. Think of it as the underlying plumbing for plugging in your local models.

Community Call: We Need You!

Version 3.0 is the result of 148 PRs from 10 contributors, including 46 from the community and 3 first-time open-source contributors. Version 3.1 is currently being developed out in the open, with 422 open issues and 30 “good first issue” tickets ready to go. Here are a few interesting entry points:

  • Add date and ID trap tests for low-resource languages (#3894)
  • Add GIF, WebP, and BMP support to multimodal preflight (#3833)
  • Write an offline field guide for federated learning rounds (#3882)
  • Add runnable synthetic examples for clinical workflow contracts (#3794)

If you’re interested in local AI for healthcare, come join us: grab an issue, say hi, and get your name in the next release notes. Dropping a star, filing bug reports, or even just letting us know “this broke on my machine” helps a ton.

I’ll be hanging around in the comments—feel free to ask anything!

(English is not my first language, so this post was polished with the help of an LLM. But the code, the release, and every piece of data are 100% our own hard work. 🤗)

Top Discussions

kian_no (⬆13): Is this useful on a personal level? I could just point a profile to a folder containing all my data and have a local model generate a report; in that scenario, what makes this tool different or more useful?
dark-night-rises (OP) (⬆5): You can use local models with any coding agent to handle tasks privately, but those are still general-purpose models. There are clinical tasks generative models just can’t do well, such as medical and clinical entity extraction with span detection. This is similar to the System 1 models people have been discussing recently—they are essentially classifiers equipped with broader general knowledge. OpenMed comes with over 2,000 clinical models that you can deploy in different setups, and the models will…
sleight42 (⬆5): OP, you should crosspost this to /r/coolgithubprojects too.
dark-night-rises (OP) (⬆2): Much love! 🤗
dark-night-rises (OP) (⬆7): That’s a great question. We’ve been focused on building the tools and models developers need to call. We tested two models: on workstations, we used Qwen3.8 27B, which performs exceptionally well at agent tool calling, invoking the right OpenMed models and clinical tools as needed; on resource-constrained devices like mobile phones, LFM2.5 2.6B handled tool calling surprisingly well, accurately triggering the appropriate models and tools on both iPhone and Android.
Leary_2844 (⬆8): “Fully local with no cloud fallback”? Are we doing cheap buzzword gimmicks in post titles now?
silenceimpaired (⬆7): Not sure how anyone outside healthcare would use this… What models does it use? Does the model have a knowledge base to reference besides the patient data?
dark-night-rises (OP) (⬆9): It’s definitely not meant for people outside healthcare! It’s built specifically for healthcare practitioners and developers. If you’ve worked on even a single healthcare project, 90% of what looks alien here will make total sense. Our hope is that when people tackle medical AI projects in the future, they know it can be done 100% locally without ever relying on remote models.