Enterprise-Grade Architecture
for Healthcare AI
Built for the hardest compliance environments on earth. ASEAN hospitals demand zero downtime, zero PHI leakage, and multi-jurisdiction data residency.
4-Tier Multi-Tenant Architecture
Every tier has an independent admin panel, isolated Row-Level Security policies, and configurable modules. A config change at Tier 2 (Group) propagates down — a config at Tier 4 (Department) stays scoped to that department.
Country
Malaysia · Canada · Singapore
- Separate data residency per jurisdiction
- Country-level compliance configuration
- Local payment rail integration (FPX, Interac, NETS)
- Independent admin panel per country
Healthcare Group
KPJ · Raffles · Columbia Asia
- Group-level analytics and consolidated billing
- Cross-hospital reporting dashboard
- Group admin with hospital management
- Isolated RLS policies per group
Hospital
KPJ Damansara · KPJ Ampang · KPJ Ipoh
- Patient check-in flows and kiosk configuration
- HIS integration (KCIS, NEHR, MyHealth)
- Staff dashboard and queue management
- Configurable modules per facility
Department
A&E · Cardiology · Orthopaedics · OB/GYN
- Queue management and specialist routing
- Acuity threshold configuration per department
- Department-level analytics
- Independent module activation
Each tier is a separate RLS boundary. Zero cross-tenant data access is architecturally enforced — not just policy.
86-Table PostgreSQL Schema
Row-Level Security enforced at every table. Tenant isolation is a database guarantee, not an application assumption. Zero cross-tenant data leakage is possible by design.
Schema Coverage
Audit Event Architecture
Every read and write is captured with: actor, timestamp, IP address, action type, affected record ID, and before/after JSON diff.
7-year log retention — healthcare compliance requirement across MY, CA, and SG.
HIPAA-Aligned Design
- Audit table captures every PHI access event
- Minimum necessary access enforced via RLS
- AES-256 encryption for PII at rest
- TLS 1.3 for all data in transit
- Automated breach detection triggers
On-Premise MOVO-X AI — Zero PHI Egress
The only HIPAA and PDPA-compliant LLM clinical triage solution deployed in ASEAN. No patient data leaves the hospital network.
Deployed inside hospital private network with hospital-enforced network policy. API calls routed through hospital's internal gateway — never via public internet path. Zero patient data leaves the hospital.
System prompt: clinical context (department, acuity thresholds, active language). User turn: anonymised symptom description — no direct patient identifiers sent to model. Prompt construction happens inside hospital network boundary.
Structured output extraction: SOAP clinical note format. Acuity score 1–5 assigned from symptom keywords, duration, and risk factors. Delivered to doctor's dashboard before patient enters the consultation room.
Performance
Resilience & Audit
- Fallback: if AI unavailable, kiosk switches to structured symptom checklist — no patient blocked
- Every triage session logged: prompt, response, SOAP output, acuity score
- Timestamp, kiosk ID, and patient encounter ID on every audit record
- Session replay available for clinical governance review
- Anomaly detection on acuity score distribution per department
Triple-Layer Security
Each layer is independently verifiable. Security is not a policy — it is an architectural constraint enforced at network, application, and database level simultaneously.
Network Layer
- Hospital private network deployment — kiosk never on public internet
- Firewall rules with zero inbound ports exposed on kiosk hardware
- VPN for remote administration and support access
- Network segmentation between kiosk LAN and hospital HIS LAN
- All external API calls outbound-only, proxied through hospital gateway
Application Layer
- JWT authentication with 15-minute access token expiry
- Refresh token rotation with single-use enforcement
- Rate limiting on all API endpoints — per IP, per tenant, per user
- OWASP Top 10 compliance — safe DOM APIs enforced across entire codebase
- Content Security Policy headers on every response
- Input validation with Zod schemas at every API boundary
Database Layer
- Row-Level Security policies enforced on every table — no exceptions
- Supabase service role key never exposed to client or browser
- All queries use prepared statements via Prisma — no raw SQL from user input
- Column-level encryption for PII fields (IC number, NRIC, passport)
- Automated daily backups with Point-in-Time Recovery (PITR)
- Zero cross-tenant query paths possible by architectural design
18-Month Compliance Head Start
Each jurisdiction's compliance stack was architected from day zero — not retrofitted. Competitors entering ASEAN healthcare cannot replicate this in under two years.
Malaysia
- PDPA 2010 — consent management, data minimisation, breach notification
- PHFSA 1998 — Private Healthcare Facilities and Services Act compliance
- MOH certification pathway and Circular 5/2019 digital health records mandate
- Supabase ap-southeast-1 (Singapore) with envelope encryption
- KMS in ap-southeast-5 (Jakarta) for MY-adjacent residency
- MY-resident Data Protection Officer appointed
Canada
- PIPEDA (federal) — Privacy Act digital health alignment
- Law 25 (Quebec) — world's strictest provincial privacy law
- PHIPA (Ontario) — Personal Health Information Protection Act
- OHIP Health Card verification integration
- Data residency in Supabase ca-central-1 (Montreal)
- Consent audit trail captured per encounter, 7-year retention
Singapore
- PDPA (SG) — Personal Data Protection Act compliance
- HBRA — Healthcare Bill of Rights Act alignment
- NEHR integration — National Electronic Health Record API
- HealthHub API for patient-facing data portability
- MAS TRM guidelines for financial data and payment handling
- MOH Singapore licensing pathway for private hospital operators
Production Infrastructure
Every infrastructure choice is production-verified — not planned. 62 end-to-end tests pass on every pull request. OWASP ZAP security scan runs on every CI build.
Technical Diligence Welcome
Our CTO is available for architecture deep-dives, security reviews, and code walkthroughs. OWASP ZAP scan results, E2E test suite output, and schema documentation are available in the investor data room.