Zero-Retention Security Whitepaper
Why storing zero bytes of patient data on server disks is the gold standard for clinical confidentiality and data breach immunity.
Executive Summary
Most healthcare software architectures rely on centralized relational databases (PostgreSQL, MySQL, MongoDB) to store patient charts, pure-tone audiograms, and clinical narratives. This persistent data repository creates a high-value target for ransomware attacks, unauthorized access, and subpoena liabilities.
phiReports.health is architected around Zero Data Retention. Patient data exists exclusively in the clinician’s browser volatile RAM during active editing. When an official PDF export is requested, the payload is transmitted over TLS 1.3 to an isolated ephemeral Chromium container that renders the vector document directly into an in-memory buffer, streams the bytes back to the client, and terminates the container lifecycle. Zero records, zero disk files, and zero database entries remain.
The Ephemeral RAM Lifecycle
Clinician inputs patient name, audiogram (AD/AS), and ISBAR notes. All state remains strictly in local client memory.
Encrypted POST request sent with strict Cache-Control: no-store, no-cache headers.
Headless Chromium instance compiles the high-resolution vector PDF buffer in memory without writing to disk.
PDF binary bytes stream to clinician's download folder. Container context and memory are immediately garbage-collected.
HIPAA Security Rule Alignment (45 CFR § 164.312)
§ 164.312(e)(1) Transmission Security
All data in transit is protected using modern Transport Layer Security (TLS 1.3) with perfect forward secrecy and 256-bit AES encryption.
§ 164.312(a)(2)(iv) Data at Rest
Because phiReports.health stores zero bytes of PHI at rest, the risk of physical disk breach, unencrypted backup leakage, or server theft is mathematically zero.
§ 164.312(d) Authentication & Access
Clinic Passkeys authenticate prepaid document credit balances without associating credentials with patient medical charts.
Decoupled Billing & Payment Separation
Stripe payment processing operates on an isolated domain and possesses zero visibility into clinician inputs or clinical documentation.