PLATFORM · ARCHITECTURE

Shared infrastructure.
Isolated environments.

ApneDoctors serves many hospitals from one platform without any hospital inheriting another's setup — or seeing a row of their data. This page explains how that is arranged, without turning into engineering documentation.

Talk to us Security overview

APNEDOCTORS HQ
The control plane. Provisioning, configuration, platform health, audit.
APNEDOCTORS PLATFORM
Tenancy, role-based access, module configuration, the AI and workflow layer.
HOSPITAL TENANTS
One isolated environment per hospital, with its own identity, users and data.
ROLE SURFACES
ApneDoctors OS, ApneDoc, ApneMeds and the patient app, scoped by role inside a tenant.

PLATFORM · MULTI-TENANT

One platform.
Many hospitals. No mixing.

Every hospital runs as its own tenant with its own identity, users, modules, workflows and data. The infrastructure underneath is shared; the environment on top is not. A hospital configures what it needs and never inherits somebody else’s setup — or sees a row of their data.

TENANCY MODEL

SHARED INFRASTRUCTURE · ISOLATED ENVIRONMENTS

APNEDOCTORS HQ

APNEDOCTORS PLATFORM

Provisioning · Role-based access · Tenant isolation · Configurable modules · Audit

Hospital A

Isolated

HOSP-RJK-04421

ENABLED MODULES

ReceptionDoctorsApneMedsBillingAnalytics

6 roles · 214 users

Hospital B

Isolated

HOSP-AMD-01188

ENABLED MODULES

ReceptionDoctorsBillingTheatreWardsAnalytics

8 roles · 486 users

Hospital C

Isolated

HOSP-SUR-07734

ENABLED MODULES

ReceptionDoctorsApneMeds

4 roles · 39 users

OWNERADMINRECEPTIONDOCTORPHARMACYBILLING

ROLES ARE GRANTED PER TENANT · NEVER ACROSS THEM

The architecture How a hospital goes live

GUARANTEES

What the model
commits to.

Tenant isolation: A hospital's operational data is scoped to that hospital. Access is granted inside a tenant and does not reach across one.
Role-based access: Owner, admin, reception, doctor, pharmacy and billing. A role exists within a tenant and carries no meaning outside it.
Configurable modules: Two hospitals on the same platform can run entirely different environments, because the modules are chosen per tenant.
Patient-held identity: Health identity belongs to the patient, not to a tenant. A hospital receives what a visit requires when the patient scans in.
Auditability: Administrative and clinical actions are recorded with actor and timestamp, inside the tenant they happened in.
One record per visit: Check-in, brief, consultation, prescription, dispensing and billing attach to the same visit rather than to six systems.

PROCUREMENT ASKS THESE

Straight answers,
before you ask twice.

Q
Is our data shared with other hospitals?
No. Operational data is scoped to your tenant. Nothing about your hospital is visible from another hospital's environment.
Q
Do we get the same setup as everyone else?
No. Modules, roles and workflows are configured per hospital. The platform underneath is shared; the environment on top is not.
Q
Who can see a patient's history?
The hospital the patient has shared with, through the visit they opened by scanning. Sharing is per hospital, by the patient's action.
Q
Can we keep our existing systems?
That is part of the onboarding conversation. We map what you already run before deciding what ApneDoctors should replace or sit alongside.

Nothing on this page is a compliance attestation. If a certification matters to your procurement, ask us directly and we will tell you exactly where we stand.

ENTERPRISE

Bring your architecture
team to the call.

We would rather answer the hard questions early than discover them during implementation.

Talk to ApneDoctors Security

Shared infrastructure.Isolated environments.

One platform.Many hospitals. No mixing.

What the modelcommits to.

Straight answers,before you ask twice.

Bring your architectureteam to the call.

Shared infrastructure.Isolated environments.

One platform.Many hospitals. No mixing.

What the modelcommits to.

Straight answers,before you ask twice.

Bring your architectureteam to the call.

Shared infrastructure.
Isolated environments.

One platform.
Many hospitals. No mixing.

What the model
commits to.

Straight answers,
before you ask twice.

Bring your architecture
team to the call.

Shared infrastructure.
Isolated environments.

One platform.
Many hospitals. No mixing.

What the model
commits to.

Straight answers,
before you ask twice.

Bring your architecture
team to the call.