Security Architecture Overview

1. Security Architecture & Governance

PatientCore is engineered from the ground up for high-trust outpatient clinical environments. Our technical safeguards are architected to satisfy Republic Act No. 10173 (Philippine Data Privacy Act), PhilHealth PECWS 3.0 clearinghouse encryption mandates, and international clinical data exchange standards (HL7 FHIR).

This technical summary outlines our cryptographic mechanisms, tenant perimeter isolation, and operational controls for institutional hospital due diligence and third-party API platform verification.

2. Multi-Tenant Architectural Isolation

PatientCore implements strict multi-tenant boundary isolation to prevent unauthorized data access across healthcare provider accounts:

3. Cryptographic Controls & Data Protection

• Transport Layer Security: All endpoints enforce TLS 1.3 across external connections. Insecure HTTP requests are automatically upgraded or rejected with HSTS (HTTP Strict Transport Security).
• Volume & Field Encryption: Databases at rest utilize AES-256 volume encryption. Sensitive secrets, clinician PINs, and national identifiers (PhilHealth PIN, SSS, Tax ID) are protected with salted one-way hashes or encrypted with envelope keys.
• PhilHealth Claims Cryptographic Architecture (Roadmap): Prepared for direct clearinghouse submission with AES-256-CBC envelope encryption and SHA-256 digital signature hashing under PhilHealth PECWS 3.0 standards.

4. Role-Based Access Control (RBAC) & Break-Glass Protocols

Healthcare workflows demand strict separation of duty between administrative and clinical personnel:

• Administrative vs. Clinical Segregation: Front-desk receptionists, billing officers, and triage staff cannot view doctor SOAP consultation notes, diagnostic findings, or clinical assessments.
• Break-Glass Clinical Emergency Protocol: In emergency scenarios where a physician requires urgent access to records from another specialty department, access requires an explicit typed clinical justification logged to an append-only compliance ledger.
• Workstation Session Protection: Clinical terminals lock automatically after configurable periods of inactivity. Clinicians unlock their workstation rapidly using rate-limited 4-digit PINs.

5. Immutable Audit Trails

Every read, write, modification, e-prescription generation, diagnostic order, and billing settlement generates an append-only, tamper-evident audit record containing:

• Authoritative UTC and regional local timestamps.
• Operator identity, authenticated role, and workstation IP.
• Encounter token and targeted record classification.
• Cryptographic checksums to prevent log tampering or retrospective alteration.

6. Offline-First Resilience & Local Synchronization

Philippine clinics frequently experience unstable telecommunications and intermittent internet connectivity. PatientCore implements an offline continuity layer:

• Browser IndexedDB Local Encrypted Cache: Consultations continue without interruption when internet drops. Clinicians can draft SOAP notes and write prescriptions locally with zero data loss.
• Deterministic Sync Conflict Resolution: Upon connection restoration, an idempotent transaction queue reconciles local drafts against the cloud database using deterministic vector timestamps.

7. Security Inquiries & Vulnerability Reporting

We welcome security audits and responsible vulnerability disclosures from institutional hospital IT teams and independent security researchers: