System Architecture
A robust, scalable, and isolated architecture designed for high-availability clinical workloads.
Multi-Tenant Isolation
Curenium uses a "Logical Partitioning" model to ensure that different medical organizations never share clinical context or data accidental exposure.
Isolation Layers
- API Layer: Every request is scoped to an
organizationIdverified via JWT. - Database Layer: Every clinical document (Patients, Meds, Labs) contains a mandatory reference to its parent organization.
- Storage Layer: Physical files (Imaging, Lab PDFs) are stored in organization-specific buckets.
Service-Oriented Logic
The EHR is split into distinct logical services that handle specific clinical concerns:
- Registry Service: Manages patient identities and demographics.
- Clinical Service: Handles encounters, notes, and care plans.
- Diagnostic Service: Coordinates laboratory and imaging orders.
NEXT.JS / REDIS (Frontend & Edge)
NODE.JS / MICROSERVICES (Application)
MONGODB / S3 (Persistent Data)
High Availability
Distributed infrastructure with automatic failover to ensure the EHR is available 24/7.
Real-Time Sync
Websockets manage live updates across clinical dashboards for instant synchronization.
Our architecture allows us to isolate performance-heavy modules (like Imaging processing) to dedicated clusters, ensuring the core EHR remains responsive during peak loads.