Skip to content

Platform · Security and privacy

Each desk sees its part, each clinic its own data

Patient data, protected.

Security in Dudoxx AI HMS is built from plain layers: sign-in, roles, clinic isolation, encryption and an audit log. Reception, doctors and accounting each see the part of the record their work needs.

The layers, one at a time

  • Roles

    Each desk opens its own role-based portal, ten on one platform.

  • Clinic isolation

    Each clinic's data is isolated: records, documents, schedules and invoices stay inside its boundary.

  • Encryption

    Patient data is encrypted in transit and at rest.

  • Audit log

    An audit log sits behind the record, for questions such as who looked at a result.

In daily work

  1. Layers

    Security comes in plain layers, starting at sign-in: each person uses their own account.

  2. GDPR

    Dudoxx AI HMS is GDPR-aligned by design.

How it fits into the platform

Dudoxx AI HMS architecture: one gateway, one clinical core, one patient record Clients (web portals on Next.js, desktop app on Electron, mobile app on Flutter) enter through a secure gateway into the clinical core built on NestJS (EHR, scheduling, documents, billing, messaging). Seven AI assistants work inside the core and use self-hosted language models. The core calls four processing engines (FastAPI, LiveKit) and stores clinical data in the FHIR R4 patient record, one partition per clinic, plus clinic data (PostgreSQL), files (MinIO) and a knowledge index (Qdrant). Data services run in containers. The platform runs as SaaS, on-premises or hybrid. AI ASSISTANTS · INSIDE THE PLATFORM Toucan first orchestrator Condor plans · asks · acts Falcon voice Parrot messages IBIS clinical guidance Phoenix help Sentinel paper to data plan · ask · act on the record PROCESSING ENGINES Private AI models self-hosted language models no outside AI provider Document reading scans to structured data FastAPI Document generation branded PDF output FastAPI Voice speech-to-text · text-to-speech Video visits consultations · meetings LiveKit PLATFORM · FROM THE SCREEN TO THE RECORD Clients web portals · desktop app Next.js Electron Secure gateway sign-in · roles clinic isolation Clinical core EHR · scheduling · documents billing · messaging NestJS Patient record FHIR R4 · one partition per clinic the single clinical source of truth Clinic data, files, index accounts · per-clinic storage search vectors PostgreSQL MinIO Qdrant YOUR INFRASTRUCTURE SaaS On-premises Hybrid FHIR R4 RESOURCES IN THE RECORD Patient Encounter Appointment Observation Condition CarePlan MedicationRequest AllergyIntolerance Immunization DiagnosticReport DocumentReference live updates · to every screen patient record and EHR trust boundary data store request
Dudoxx AI HMS architecture: one gateway, one clinical core, one patient record Clients (web portals on Next.js, desktop app on Electron, mobile app on Flutter) enter through a secure gateway into the clinical core built on NestJS (EHR, scheduling, documents, billing, messaging). Seven AI assistants work inside the core and use self-hosted language models. The core calls four processing engines (FastAPI, LiveKit) and stores clinical data in the FHIR R4 patient record, one partition per clinic, plus clinic data (PostgreSQL), files (MinIO) and a knowledge index (Qdrant). Data services run in containers. The platform runs as SaaS, on-premises or hybrid. AI ASSISTANTS · INSIDE THE PLATFORM Toucan first orchestrator Condor plans · asks · acts Falcon voice Parrot messages IBIS clinical guidance Phoenix help Sentinel paper to data plan · ask · act on the record PROCESSING ENGINES Private AI models self-hosted language models no outside AI provider Document reading scans to structured data FastAPI Document generation branded PDF output FastAPI Voice speech-to-text · text-to-speech Video visits consultations · meetings LiveKit PLATFORM · FROM THE SCREEN TO THE RECORD Clients web portals · desktop app Next.js Electron Secure gateway sign-in · roles clinic isolation Clinical core EHR · scheduling · documents billing · messaging NestJS Patient record FHIR R4 · one partition per clinic the single clinical source of truth Clinic data, files, index accounts · per-clinic storage search vectors PostgreSQL MinIO Qdrant YOUR INFRASTRUCTURE SaaS On-premises Hybrid FHIR R4 RESOURCES IN THE RECORD Patient Encounter Appointment Observation Condition CarePlan MedicationRequest AllergyIntolerance Immunization DiagnosticReport DocumentReference live updates · to every screen patient record and EHR trust boundary data store request
Dudoxx AI HMS architecture: one gateway, one clinical core, one patient record Clients (web portals on Next.js, desktop app on Electron, mobile app on Flutter) enter through a secure gateway into the clinical core built on NestJS (EHR, scheduling, documents, billing, messaging). Seven AI assistants work inside the core and use self-hosted language models. The core calls four processing engines (FastAPI, LiveKit) and stores clinical data in the FHIR R4 patient record, one partition per clinic, plus clinic data (PostgreSQL), files (MinIO) and a knowledge index (Qdrant). Data services run in containers. The platform runs as SaaS, on-premises or hybrid. AI ASSISTANTS · INSIDE THE PLATFORM Toucan first orchestrator Condor plans · asks · acts Falcon voice Parrot messages IBIS clinical guidance Phoenix help Sentinel paper to data plan · ask · act on the record PROCESSING ENGINES Private AI models self-hosted language models no outside AI provider Document reading scans to structured data FastAPI Document generation branded PDF output FastAPI Voice speech-to-text · text-to-speech Video visits consultations · meetings LiveKit PLATFORM · FROM THE SCREEN TO THE RECORD Clients web portals · desktop app Next.js Electron Secure gateway sign-in · roles clinic isolation Clinical core EHR · scheduling · documents billing · messaging NestJS Patient record FHIR R4 · one partition per clinic the single clinical source of truth Clinic data, files, index accounts · per-clinic storage search vectors PostgreSQL MinIO Qdrant YOUR INFRASTRUCTURE SaaS On-premises Hybrid FHIR R4 RESOURCES IN THE RECORD Patient Encounter Appointment Observation Condition CarePlan MedicationRequest AllergyIntolerance Immunization DiagnosticReport DocumentReference live updates · to every screen patient record and EHR trust boundary data store request
Dudoxx AI HMS architecture: one gateway, one clinical core, one patient record Clients (web portals on Next.js, desktop app on Electron, mobile app on Flutter) enter through a secure gateway into the clinical core built on NestJS (EHR, scheduling, documents, billing, messaging). Seven AI assistants work inside the core and use self-hosted language models. The core calls four processing engines (FastAPI, LiveKit) and stores clinical data in the FHIR R4 patient record, one partition per clinic, plus clinic data (PostgreSQL), files (MinIO) and a knowledge index (Qdrant). Data services run in containers. The platform runs as SaaS, on-premises or hybrid. AI ASSISTANTS · INSIDE THE PLATFORM Toucan first orchestrator Condor plans · asks · acts Falcon voice Parrot messages IBIS clinical guidance Phoenix help Sentinel paper to data plan · ask · act on the record PROCESSING ENGINES Private AI models self-hosted language models no outside AI provider Document reading scans to structured data FastAPI Document generation branded PDF output FastAPI Voice speech-to-text · text-to-speech Video visits consultations · meetings LiveKit PLATFORM · FROM THE SCREEN TO THE RECORD Clients web portals · desktop app Next.js Electron Secure gateway sign-in · roles clinic isolation Clinical core EHR · scheduling · documents billing · messaging NestJS Patient record FHIR R4 · one partition per clinic the single clinical source of truth Clinic data, files, index accounts · per-clinic storage search vectors PostgreSQL MinIO Qdrant YOUR INFRASTRUCTURE SaaS On-premises Hybrid FHIR R4 RESOURCES IN THE RECORD Patient Encounter Appointment Observation Condition CarePlan MedicationRequest AllergyIntolerance Immunization DiagnosticReport DocumentReference live updates · to every screen patient record and EHR trust boundary data store request

The same architecture with the technology behind each layer and the resource types of the patient record.

Open the full diagram (opens in a new tab)

Questions about security and privacy

Walk through the layers with us

Book a demo and bring your data protection questions; we answer them with the platform open.