A Production-Ready, 241-Class Multimodal Clinical Intelligence Engine with Real-Time AI Telehealth
MedIQ (formerly DermLIP Server) is a highly optimized, fully localized inference and training engine. It leverages a streamlined architecture (SigLIP2, EVA-CLIP, and OpenAI-CLIP) to classify 241 long-tail dermatology conditions and is scalable to audio and text diagnostic inputs. It completely eliminates Language Model hallucination through a hard-coded Clinical Knowledge Base and a deterministic rule engine.
NEW: Voice Calling Microservice - Real-time WebRTC telehealth consultations with AI-powered transcription, clinical reasoning, and bidirectional voice (patients can speak to AND listen to the AI doctor). 100% local execution with zero external API calls.
Everything is containerized via Docker for safe, isolated execution and connects through a unified FastAPI Gateway.
We maintain an exhaustive suite of documentation for every script, algorithm, and hyperparameter in this project. If you have a question, it is answered in the docs/ folder.
finetune.py.(For detailed breakdowns of dataset.py, dashboard.py, run_all_training.bat, etc., browse the docs/ directory).
MedIQ uses Supabase for persistent conversation history and image storage.
supabase/migrations/001_core_hms_schema.sql and 002_hms_rls_and_triggers.sql within your Supabase project's SQL Editor (Run as postgres admin).config/.env with your project credentials:
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SERVICE_KEY=your-service-role-key
mediq-images in the Supabase Storage dashboard.This core visual system utilizes three foundational architectures, each uniquely fine-tuned or engineered to conquer the severe domain gap of clinical skin photos:
acne_vulgaris), which fetches human-verified facts from the clinical_kb.json.acreate_client) with a tuned HTTP connection pool. This enables the system to handle thousands of concurrent guest sessions and medical reports without event-loop blocking.MedIQ is engineered for production-grade resilience and horizontal scalability:
docker-compose.yml with healthchecks, restart policies, and service_healthy readiness gates.The API is fully isolated into Docker Microservices (one container per AI model to eliminate transformers dependency contamination).
# Bring up the Gateway and the active ensemble
docker compose up --build -d
# OR use the deployment script (includes Voice Service)
./deploy_multimodal.bat
The gateway exposes a unified orchestrator port (8003 by default) covering:
POST /predict (Submit image. Executes Stage 1 & Stage 2 OOD Gates, then routes to single model or ?model=ensemble)POST /<model>/chat (Retrieve context-aware medical followups)POST /call/initiate (Start WebRTC telehealth consultation with AI)WS /ws/call/{call_id} (Real-time transcription + AI insights during call)/<model>/predict bypassing gates)MedIQ now supports real-time AI telehealth consultations with bidirectional voice:
All AI models run locally with zero external API calls:
# 1. Run database migration (manual)
supabase db push
# 2. Deploy voice service
./deploy_multimodal.bat
# 3. Test health
curl http://localhost:8010/health
# 4. Initiate call
curl -X POST http://localhost:8003/call/initiate \
-H "Authorization: Bearer <token>" \
-d "appointment_id=<uuid>"
π Complete Voice Calling Documentation
Because deep-learning vision models are highly sensitive to their input distribution, following these photographic guidelines is strictly required to pass the OOD (Out-of-Distribution) Gates and achieve maximum diagnostic accuracy:
The root workspace includes a master batch file designed to sequentially tune all three foundation models, applying optimal Epochs, MixUp, Focal Loss, and EMA regularization.
# Completely hands-free batch runner for all 5 foundation models
.\run_training.bat
Monitor live training progress, model health, and generalization gaps via the central hub:
venv\Scripts\streamlit run dashboard.py
36 commits
TypeScript
56.0%
Python
37.2%
PLpgSQL
2.1%
JavaScript
2.0%
HTML
1.0%
A Production-Ready, 241-Class Multimodal Clinical Intelligence Engine with Real-Time AI Telehealth
MedIQ (formerly DermLIP Server) is a highly optimized, fully localized inference and training engine. It leverages a streamlined architecture (SigLIP2, EVA-CLIP, and OpenAI-CLIP) to classify 241 long-tail dermatology conditions and is scalable to audio and text diagnostic inputs. It completely eliminates Language Model hallucination through a hard-coded Clinical Knowledge Base and a deterministic rule engine.
NEW: Voice Calling Microservice - Real-time WebRTC telehealth consultations with AI-powered transcription, clinical reasoning, and bidirectional voice (patients can speak to AND listen to the AI doctor). 100% local execution with zero external API calls.
Everything is containerized via Docker for safe, isolated execution and connects through a unified FastAPI Gateway.
We maintain an exhaustive suite of documentation for every script, algorithm, and hyperparameter in this project. If you have a question, it is answered in the docs/ folder.
finetune.py.(For detailed breakdowns of dataset.py, dashboard.py, run_all_training.bat, etc., browse the docs/ directory).
MedIQ uses Supabase for persistent conversation history and image storage.
supabase/migrations/001_core_hms_schema.sql and 002_hms_rls_and_triggers.sql within your Supabase project's SQL Editor (Run as postgres admin).config/.env with your project credentials:
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SERVICE_KEY=your-service-role-key
mediq-images in the Supabase Storage dashboard.This core visual system utilizes three foundational architectures, each uniquely fine-tuned or engineered to conquer the severe domain gap of clinical skin photos:
acne_vulgaris), which fetches human-verified facts from the clinical_kb.json.acreate_client) with a tuned HTTP connection pool. This enables the system to handle thousands of concurrent guest sessions and medical reports without event-loop blocking.MedIQ is engineered for production-grade resilience and horizontal scalability:
docker-compose.yml with healthchecks, restart policies, and service_healthy readiness gates.The API is fully isolated into Docker Microservices (one container per AI model to eliminate transformers dependency contamination).
# Bring up the Gateway and the active ensemble
docker compose up --build -d
# OR use the deployment script (includes Voice Service)
./deploy_multimodal.bat
The gateway exposes a unified orchestrator port (8003 by default) covering:
POST /predict (Submit image. Executes Stage 1 & Stage 2 OOD Gates, then routes to single model or ?model=ensemble)POST /<model>/chat (Retrieve context-aware medical followups)POST /call/initiate (Start WebRTC telehealth consultation with AI)WS /ws/call/{call_id} (Real-time transcription + AI insights during call)/<model>/predict bypassing gates)MedIQ now supports real-time AI telehealth consultations with bidirectional voice:
All AI models run locally with zero external API calls:
# 1. Run database migration (manual)
supabase db push
# 2. Deploy voice service
./deploy_multimodal.bat
# 3. Test health
curl http://localhost:8010/health
# 4. Initiate call
curl -X POST http://localhost:8003/call/initiate \
-H "Authorization: Bearer <token>" \
-d "appointment_id=<uuid>"
π Complete Voice Calling Documentation
Because deep-learning vision models are highly sensitive to their input distribution, following these photographic guidelines is strictly required to pass the OOD (Out-of-Distribution) Gates and achieve maximum diagnostic accuracy:
The root workspace includes a master batch file designed to sequentially tune all three foundation models, applying optimal Epochs, MixUp, Focal Loss, and EMA regularization.
# Completely hands-free batch runner for all 5 foundation models
.\run_training.bat
Monitor live training progress, model health, and generalization gaps via the central hub:
venv\Scripts\streamlit run dashboard.py
36 commits
TypeScript
56.0%
Python
37.2%
PLpgSQL
2.1%
JavaScript
2.0%
HTML
1.0%