Skip to content

Platform · Integrations

Open by design, built on an open standard

Works with the systems you have.

The patient record in Dudoxx AI HMS is built on FHIR R4, an open standard. IT leads and partners work with a data shape the industry already knows, and accounting exports for tax advisers.

Where the record meets other systems

  • FHIR R4 record

    Dudoxx AI HMS builds its patient record on FHIR R4, an open standard for structuring health data.

  • Working with the record

    Integration starts from a record built on FHIR R4 and is planned with your IT lead and partners.

  • Lab and accounting

    The record holds lab results alongside the notes and letters, so a value is read in context.

  • Your practice system

    Many clinics keep their practice system; how the two work side by side is planned with your clinic.

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)

Talk to us about your systems

Book a demo and we look at the systems your clinic already runs.