Dudoxx grew from clinical experience in UKE Hamburg's dermatology department — and a determination to solve the documentation problem at its source.
Every screen in Dudoxx was shaped by physicians in daily practice — a single view that surfaces patients, reviews, and tasks without the clutter of legacy EHRs.
Lab results received for T. Weber
2 min agoPrescription renewed for A. Becker
15 min agoNew message from M. Schmidt
1 hour agoRevenue
€12,450
Patients
142
Appointments
87
Weekly Revenue
Beyond the consultation room, Dudoxx gives practice teams a single source of truth — scheduling, billing, analytics, and clinical records that talk to each other. Three things make that possible: the AI is built into the platform rather than bolted on beside it, every clinical record is stored directly in HL7 FHIR R4 instead of a proprietary schema, and the whole platform runs either on our managed EU cloud or inside your own infrastructure. The same physician-led design carries through every module.
Dr. Frenz Ohm spent 3–4 hours every clinical day on documentation — SOAP notes, referral letters, billing codes, prescription renewals. Not because the system was neglected, but because it was designed for administrators, not clinicians. Every tool that promised to help added more complexity. So we built TUCAN: not a chatbot, but an autonomous clinical orchestrator that handles the entire administrative layer of medicine — so physicians can be fully present in the room. TUCAN was never a separate product bolted onto an records system. It lives inside the platform and shares the same services, roles, permissions and audit trail as every screen a clinician touches — which is why a new capability becomes available to the AI the moment it ships, with no separate integration project.
A world where every physician enters a consultation knowing their patient's complete context, exits having already completed the documentation, and never wonders whether the referral was sent or the billing was coded — because TUCAN handled all of it. We think three things have to be true at once for that world to arrive, and almost no system today gets all three: the AI has to be native to the platform, the clinical record has to live in an open international standard, and the clinic has to be free to choose where the software runs. That combination is what we are building.
Three co-founders uniting clinical practice, healthcare operations, and enterprise technology
CEO & Co-Founder
Clinical Leadership & Digital Health
Dermatologist at UKE Hamburg and the registered managing director of Dudoxx UG. Frenz brings frontline clinical experience and digital-health leadership to a platform shaped around how physicians actually work.
View Dr. Frenz Henning Ohm's profile
COO & Co-Founder
Dermatology, Research & Clinical Operations
Former researcher and Senior Physician at UKE Hamburg, now leading the Derm4hair specialist practice she founded. Nesrine connects clinical validation, research, and real-world operations at Dudoxx.
View Dr. Nesrine Ben Anaya's profile
CTO & Co-Founder
AI Architecture & Enterprise Systems
Technology leader with 30 years of experience across AI, banking, enterprise platforms, and healthcare systems. Walid architects Dudoxx's FHIR-native, privacy-first platform and its TUCAN AI orchestration layer.
View Walid Boudabbous's profileThree convictions shape every decision — from architecture to clinical policy.
Dudoxx Omni Intelligence is our own AI layer — language models, embeddings, speech-to-text, voice and document reading — running self-hosted by default on Dudoxx-operated infrastructure, so no patient data, transcript or document is handed to a third-party cloud AI vendor. The platform itself deploys on our managed EU cloud or on your own servers, your choice. We built it this way not as a compliance checkbox, but because it is the only architecture that truly respects the patient's right to privacy.
TUCAN handles the administrative layer so physicians can own the clinical layer completely. Human judgment always has the final word — the AI prepares, suggests, and executes on instruction.
Built on HL7 FHIR R4 from day one — clinical data is stored directly in the standard, not translated into a proprietary schema behind it, so what goes in and what comes out are the same shape. Your patient data belongs to you and travels freely — to any specialist, any system, any country. We will never trap you in a proprietary format.
Three co-founders uniting clinical practice, healthcare operations, and enterprise technology
