MULTI-TENANT ARCHITECTURE

One platform. Strict organisational boundaries.

The target architecture supports multiple hospitals, research institutions, life-sciences customers and public-sector organisations without mixing tenant data or permissions.

EDGE / WEBWebsite · app · API gateway · CDN
↓
IDENTITY & POLICYUsers · organisations · roles · SSO · MFA · consent
↓
APPLICATION SERVICESCases · capabilities · evidence · referrals · signals · billing
↓
DATA SERVICESTransactional DB · graph store · search index · object storage · audit log
↓
ASYNC / INTEGRATIONQueues · webhooks · FHIR/API connectors · email · reporting
↓
OBSERVABILITYLogs · metrics · traces · security events · cost
Production recommendation

Move the public the platform session demo to a proper transactional database, graph/search services, managed secrets, encrypted object storage, background queues and a separately controlled audit/event store before real health information is introduced.