1. System Topology & European Edge Infrastructure
Clarivius is deployed as a resilient, multi-region European cloud architecture with edge termination in Frankfurt and Prague. All clinical data storage, processing pipelines, and vector embeddings are physically and legally bound to European Union jurisdictions under GDPR Art. 44–49 restrictions.
2. The Dual-Track Architectural Invariant (Core Law #1)
Clarivius strictly isolates its two data pipelines: Clarivius Peer (Track A) and Clarivius Direct (Track B). Track A handles de-identified 4-parameter peer consultations with zero real-world identifiers or scans. Track B handles patient-initiated specialist reviews under explicit Art. 6 and Art. 9 consent.
3. Automated Zero-PII Compliance Engine
A deterministic client-side and edge validation gate parses free-text clinical descriptions in Track A to identify and block names, telephone numbers, national health IDs, dates of birth, and postal codes before transmission.
4. Continuous Asynchronous Textual Dialogue Protocol
Consultations on Clarivius are never cold, one-off automated documents. In Track B, patients and specialists communicate through a secure, encrypted asynchronous chat room to ask follow-up questions and clarify findings.
5. Medical Imaging & The 'DICOM Is Optional' Principle
While DICOM viewing is supported in Track B, medical imaging is strictly optional. Many diagnostic dilemmas are resolved through precise clinical chronology, histology review, and physical symptom mapping alone.
6. Standards, APIs & Machine-Readable Contracts
Clarivius publishes machine-readable contracts including JSON Schema for clinical intake, RFC 9116 security.txt, and llms.txt for AI indexing.