Clinical systems governed in-country, with the evidence to show it.

Hospitals, insurers, CROs and digital-health teams run clinical and patient-facing systems across cloud and on-prem — with patient data pinned in-country and every change on an audit trail.

A doctor showing a patient a scan on a tablet

Built for

  • Hospitals
  • CROs
  • Pharma
  • Health Insurance
  • Digital Health
In-region
Patient data pinned to Mumbai or Frankfurt
Air-gapped
Option for isolated clinical networks
SCIM
Access follows the hospital directory
P0–P4
Change control with SLAs and audit trail

Regulatory reality

The regimes, and the control that answers each

  • DPDP Act 2023 / GDPR

    What it demands

    Patient data localised, processing purpose-limited and evidenced

    The control that answers it

    Residency pinned to Mumbai or Frankfurt; access and processing written to the audit trail

  • Clinical change control

    What it demands

    Every production change approved, tracked and reviewable

    The control that answers it

    ITSM change records with P0–P4 SLAs and a full audit trail

  • Workforce access hygiene

    What it demands

    Clinicians, researchers and contractors get exactly the access their role needs, revoked on exit

    The control that answers it

    IdP federation with SCIM provisioning; roles scoped by department and system

  • Availability of clinical systems

    What it demands

    Degradation detected and escalated before it reaches the ward

    The control that answers it

    Observe SLOs with burn-rate alerts; incidents opened automatically in ITSM

Use cases

Four workflows, mapped to the modules that run them

  • 01

    Patient data residency & in-region storage

    Pin workloads, inventory and audit records to an in-country region — Mumbai for DPDP, Frankfurt for GDPR — with air-gapped deployment available for networks behind strict firewalls.

  • 02

    Federated access for clinical & research staff

    Federate your IdP with SCIM provisioning so a new hire is granted the right role on first login and offboarded automatically on the next directory sync.

  • 03

    Change control with audit evidence

    Every production change is tracked through ITSM with P0–P4 SLAs and breach detection, with a full record retained for auditors.

  • 04

    Bundled observability for clinical systems

    Observe gives logs, metrics, traces and SLOs in one place, raising incidents automatically when a critical system degrades.

Reference architecture

The estates, the control plane, and what comes out

01Clinical estate (in-region)
On-prem clinical systems (Edge)
Mumbai · Frankfurt regions (DPDP · GDPR)
Entra ID · AD
02Compliant control plane · api-gateway
Security scanning (CIS · DPDP · GDPR)
Whale IAM + PAM
ITSM change control (CAB)
Inventory & Discovery
Landing Zone
03Resident data tier
Postgres RLS (in-country)
Tamper-evident audit chain
Backup & DR
04Compliance outcomes
100% data residency
DPDP / GDPR evidence
CAB-gated changes
Data-resident clinical cloud: workloads and audit stay in-region, security is scoped to DPDP and GDPR, and every production change is CAB-gated through ITSM + PAM.

Questions

Procurement, hosting and integration questions

01Can research data and clinical data be governed separately?

Yes. Workloads are grouped by system, roles are scoped per workload, and residency and access policies apply per group — so research collaborators never inherit clinical access.

02Do you support hospital networks that cannot connect outbound?

Yes — the air-gapped deployment class runs with no outbound connectivity and receives signed offline update bundles; the Edge Agent inventories the estate inside the network.

03Which certifications does the platform hold?

ISO/IEC 27001, 27017, 27018 (PII in the cloud), 27701 (privacy) and ISO 22301, independently audited, plus a GDPR compliance assessment — certificates are in the Trust Center.

Next step

Bring your Healthcare estate to a working session.

We connect one of your accounts read-only during the session, walk the Healthcare workflows above on your real resources, and leave you with the control mapping for your regimes.