φ(ai) PHI AI
Menu
Clinical workspace
Patients & charts PHI AI assistant Signature queue Ambient documentation Imaging worklist Summarization Inbox triage Patient instructions
Revenue & records
Claims & billing Prior auth & appeals Documentation gaps Release of information Sensitive categories
Population
Cohort builder No-show risk Scheduling optimization Trial pre-screening Quality measures Ingest & mapping QA Data Store
Integration
Source & target EMRs Source patient import Bulk import manager Streaming data Bulk export manager Streaming export
System
Control panel Model monitoring
Governance
Registry & preflight Fairness screen Ambient consent gate Source attributes EMR conformance Retention Audit
Documentation
System documentation Implementation & setup guide Feature documentation System architecture EMR connections Emulators & non-PHI setup Compliance & responsibility Attribution
Ryan GomezRole
Signed in — Ryan Gomez · System Administrator
You stay on this screen — each role sees it as their own permissions allow. The assistant thread and the patient in context start fresh.
Working archetypes — combinations people really hold
One role at a time — each role on its own
DocumentationDocs
System documentation Implementation & setup guide Feature documentation System architecture EMR connections Emulators & non-PHI setup Compliance & responsibility Attribution
Repository

Retention

Recorded, not enforced — the platform's honest posture, mirrored. A retention period is a documented disposition intention; nothing at the storage layer prevents an early delete or performs a late one, and the platform says so rather than implying otherwise. This screen reads the Data Store's actual time coverage against a demonstration ruleset.

1922-12-19
oldest encounter on record
2026-12-28
most recent encounter
476
deceased patients — retention clocks typically run from death

Demonstration ruleset

CategoryRecorded periodRecords in scopeBasis
Adult medical records10 years from last encounter 32,835Demonstration figure — state minimums genuinely vary (5–10+ years); the deploying organisation sets its own with counsel.
Deceased patients10 years from death 476Commonly longer than the adult minimum; jurisdiction-dependent.
Claims & billing records7 years 59,347Payer contract and false-claims lookback driven.
Psychotherapy notesper-category schedule, separate store 30Held apart; the platform records a distinct schedule for the separate store.
Audit trail6 years minimum 0HIPAA §164.316(b)(2)(i) documentation retention.
The deliberate gap, stated. The deployable platform applies no storage-level immutability on any cloud: retention is recorded as metadata and drives documented disposition; the tamper-evident audit chain makes deviation detectable rather than impossible. Retention figures are the deploying organisation's determination with their HIM manager and counsel — the platform applies a ruleset, it does not choose one.

The ruleset, evaluated against the live corpus

Not a policy on a shelf: every class below was counted on this page load (cached one hour). Nothing here deletes anything — the platform proposes a disposition set for human review, and its integrity posture is detective, not preventive.

Record classRetention period HeldPast periodDisposition
Adult medical records 10y from last encounter 32,835 0 all within period
Claims & billing 7y from service 59,347 1,145 eligible for HIM disposition review — proposed, never automatic
Imaging studies 7y from acquisition 1,756 537 eligible for HIM disposition review — proposed, never automatic
Psychotherapy notes 10y from authorship 30 0 all within period
Audit trail permanent (never disposed) 0 0 all within period
Legal holds win. 2 patient(s) currently carry an open release-of-information request — their records are excluded from any disposition proposal regardless of age, and the exclusion is itself recorded. Evaluated 2026-08-29 23:55:24.