Implementing AI in healthcare products
Healthcare is where AI has to be right, private and explainable. I have designed and built AI into health products end-to-end — from a model that helps doctors make treatment decisions to AI meal analysis from a photo — with the reliability and data-handling this domain demands.
Clinical decision support that clinicians trust
On Ealthiness I architected a custom AI model on top of Ollama with a Weaviate vector database to help doctors make treatment decisions, alongside an LLM trainer chat (Gemini/OpenAI with fallback) and AI meal analysis from photos. Self-hosting the core model keeps sensitive data under control, and fallbacks keep the assistant available when a single provider fails.
Built for privacy and scale
Health platforms carry real regulatory and reliability weight. I have paired NestJS backends with MinIO storage, Redis and BullMQ queues, and self-hosted inference so patient data stays where it should. Earlier I built mDoc.one for one of Germany’s leading digital-health companies and a US post-surgery patient-tracking platform — so I know how these systems fail and how to keep them up.
From mobile app to admin to model
A health product is more than a model: it is a patient app, a clinician/admin surface and the AI in between. I design all three together — Expo/React Native apps, React admin panels and the AI services behind them — so the experience is coherent and the data flows cleanly from capture to insight.
- Clinical decision support on a self-hosted model + vector DB keeps sensitive data controlled.
- Provider fallbacks and queues keep health AI available and reliable.
- Whole-product thinking: patient app, clinician admin and the AI between them.