maziyarpanahi/openmed

Local-first healthcare AI: clinical NER & HIPAA PII de-identification that runs 100% on-device. 2,200+ medical models, 21 languages, Apple MLX + Python, no...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 37 seconds ago
Added to GitGenius on September 12th, 2026
Created on October 4th, 2025
Open Issues & Pull Requests: 475 (+0)
GitHub issues: Enabled
Number of forks: 667
Total Stargazers: 5,308 (+0)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.0 days
Mean response time: 16.0 days
90th percentile: 39.0 days
Tracked items: 1,238

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 2% of open issues come from outside the core team — the tracker reads mainly as internal planning. Almost all tracked open issues have seen activity in the last three months. Only 8% of issues opened in the past year have been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 394
New in 7 days: 67
Closed in 7 days: 83
Avg open age: 33 days
Stale 30+ days: 24
Stale 90+ days: 9

Recent activity

Opened in 7 days: 67
Closed in 7 days: 83
Comments in 7 days: 0
Events in 7 days: 69

Top labels

  • feature (1,294)
  • roadmap-v2 (1,161)
  • P1 (646)
  • P2 (446)
  • roadmap-v3 (395)
  • P0 (387)
  • help wanted (273)
  • good first issue (253)

Detailed Description

OpenMed is a local-first healthcare AI platform that performs clinical named entity recognition and HIPAA-compliant PII de-identification entirely on-device.

The tool addresses the need to extract structured clinical insights from medical text while ensuring patient data never leaves the user's network. It works by running inference locally on the user's hardware after model artifacts are downloaded, keeping all processing on-premise. The platform supports multiple deployment targets including Apple Silicon via MLX, Android via ONNX Runtime Mobile, and browsers via Transformers.js, with a Python SDK as its core interface.

Organizations handling sensitive patient information should consider this tool if they operate under strict data residency requirements or cannot route clinical data through cloud services. It suits healthcare providers, research institutions, and compliance-sensitive deployments that need to maintain full control over where computation occurs. The project provides a large catalog of pre-built models covering clinical NER and de-identification across multiple languages, reducing the need to train custom models from scratch. The README does not make direct comparisons to alternative solutions.

The project maintains active development across multiple platforms and languages, with dedicated implementations for iOS via OpenMedKit and Android export pathways. Documentation covers both consumer and agent-based usage patterns, including MCP server integration and a command-line interface. The tool registry and skills catalog indicate ongoing expansion of callable interfaces and pre-built workflows for common healthcare NLP tasks.