CoolFace
Modelpublic

AmareshHebbar/medical-ai-model-suite

sourceHugging Faceapache-2.0updated 3mo agoView on Hugging Face
0likes
Model Card

Medical AI Fine-tuned Model Suite

A collection of 16 Qwen2.5 models fine-tuned with QLoRA, one per medical/healthcare task — ICD-10 coding, billing, clinical documentation, India's PM-JAY scheme, and more. Built by Amaresh Hebbar.

Collection page: [link to your HF collection here]

Every model uses the same approach: a real public data source (CMS, NHA India, peer-reviewed biomedical corpora — no synthetic or LLM-generated training data), QLoRA fine-tuning on Qwen2.5, and a narrow, well-defined task with a strict system prompt. The goal is a set of small, deployable specialists rather than one large general-purpose medical model.

Why specialist models instead of one big model

A single general medical LLM has to be evaluated, monitored, and trusted across every task it might be asked to do. These models are scoped to one job each — ICD-10 coding, PM-JAY classification, radiology report coding — so each one is small enough to self-host cheaply, easy to evaluate against a clear ground truth, and safe to swap out independently if a better version ships later.

The 16 models

ModelTaskBaseRows
icd10-coder-qwen25-7bICD-10-CM medical codingQwen2.5-7B74,719
snomed-mapper-qwen25-7bClinical terminology mappingQwen2.5-7B74,719
clinical-summarizer-qwen25-7bSOAP note summarizationQwen2.5-7B30,000
symptom-diagnoser-qwen25-7bSymptom → differential diagnosisQwen2.5-7B119,467
discharge-qa-qwen25-3bDischarge summary Q&AQwen2.5-3B30,000
radiology-coder-qwen25-3bRadiology report codingQwen2.5-3B25,090
medical-ner-qwen25-3bClinical named entity recognitionQwen2.5-3B16,671
hindi-medical-qwen25-3bHindi medical reasoningQwen2.5-3B19,704
cpt-coder-qwen25-3bCPT/HCPCS procedure codingQwen2.5-3B17,029
medical-billing-qwen25-3bMedical billing assistantQwen2.5-3B17,029
pmjay-classifier-qwen25-3bIndia PM-JAY package classificationQwen2.5-3B11,140
pharmacy-ner-qwen25-1bDrug entity extractionQwen2.5-1.5B3,500
ayurveda-icd-qwen25-1bAyurveda to ICD-10 bridgeQwen2.5-1.5B3,002
insurance-classifier-qwen25-1bStark Law DHS complianceQwen2.5-1.5B1,601
icd10-to-drg-qwen25-1bICD-10 → MS-DRG reimbursementQwen2.5-1.5B5,385
loinc-coder-qwen25-1bLab test CPT codingQwen2.5-1.5B2,179

Training method

All 16 models share the same recipe:

Fine-tuning methodQLoRA, 4-bit NF4 quantization, rank 16, alpha 32
Training frameworkUnsloth + TRL SFTTrainer
Target modulesqproj, kproj, vproj, oproj, gateproj, upproj, down_proj
HardwareSingle NVIDIA A40 (48GB)
Optimizerpagedadamw8bit, cosine LR schedule
Experiment trackingWeights & Biases

Model size is matched to dataset size — large datasets (>50k rows) get Qwen2.5-7B, mid-size (10k–50k) get Qwen2.5-3B, and smaller specialist datasets (<10k) get Qwen2.5-1.5B. This keeps inference cost proportional to task complexity instead of running every task through the same large model.

Data sources

Every dataset behind these models is built from real authoritative public data — CMS (ICD-10-CM, MS-DRG, Physician Fee Schedule, HCPCS), NHA India (PM-JAY HBP 2022, PM RAHAT), and peer-reviewed biomedical corpora (chat_doctor, augmented-clinical-notes, drugprot). No synthetic or LLM-generated training data. Full extraction pipelines and column-level provenance are documented on each dataset card.

How to use any model in this suite

Each model is a LoRA adapter on top of its base Qwen2.5 model. Load with PEFT:

python
from transformers import AutoModelForCausalLM, AutoTokenizer
from peft import PeftModel
import torch

base_model = "unsloth/Qwen2.5-7B-Instruct"  # match the base size for the model you're using
adapter    = "AmareshHebbar/icd10-coder-qwen25-7b"

tokenizer = AutoTokenizer.from_pretrained(base_model)
model = AutoModelForCausalLM.from_pretrained(base_model, torch_dtype=torch.bfloat16, device_map="auto")
model = PeftModel.from_pretrained(model, adapter)

See each model's individual card for its exact system prompt, example input/output, and recommended serving setup (Transformers, Unsloth, or vLLM).

Limitations

These are narrow specialist models, not general medical assistants. Each model only performs the single task it was trained on — using it outside that task will produce unreliable output. None of these models are a substitute for a licensed medical or billing professional; all output should be reviewed by a qualified person before being used in a clinical, billing, or compliance decision.

Citation

bibtex
@misc{medicalai2026,
  author    = {Hebbar, Amaresh},
  title     = {Medical AI Fine-tuning Suite},
  year      = {2026},
  publisher = {HuggingFace},
  url       = {https://huggingface.co/AmareshHebbar}
}

Contact