Epic Systems Data Archival — Queryable, Compliant, Multi-Decade

Epic Systems data archival is the process of moving historical Epic data — typically downstream finance, HCM and SCM records, and in some cases legacy clinical data from systems being retired ahead of an Epic consolidation — into a long-term queryable archive instead of keeping it in the active Epic environment. Important framing: this is not about retiring Epic. Epic Chronicles stays as the active clinical system of record. Archival is about taking the multi-decade history (5–30+ years depending on state retention rules) and freeing it from expensive operational storage while keeping it queryable for audit, finance and patient-record retrieval. Syntra ETL's archive lives on Parquet + object storage with HIPAA-grade chain of custody preserved.

Three drivers. First, state retention rules in healthcare run long — adult medical records 5–10 years post last encounter in most states, pediatric records age-of-majority + 5–10 years (often 25–30 years total), HIPAA itself requires 6 years for accounting-of-disclosures, billing records typically 7 years for IRS, fraud-and-abuse cases run 6 years for FCA. Second, Epic Clarity storage cost climbs with multi-hospital consolidations as decades accumulate. Third, legacy systems being retired during an Epic Systems to Oracle Fusion migration (Lawson HR, McKesson finance, legacy practice management) need an archive home so their retention obligations don't block decommissioning. Archival is the disciplined answer to all three.

A Clarity backup is a point-in-time disk dump — restorable but not queryable, and still tied to the source schema with its operational complexity. An Epic Systems data archival creates a queryable, schema-stable, audit-grade archive: data is extracted via the Clarity-certified extractor, transformed into Parquet (columnar, vendor-neutral), partitioned by service area + fiscal period, indexed by patient MRN / encounter ID / account number for lookup, and stored on tiered object storage. A retiree, auditor or finance analyst can query the archive directly via SQL (Athena/Trino/BigQuery), not just restore-and-rummage. HIPAA accounting-of-disclosures is preserved through the read-access log built into the archive layer.

Both, with a strong default toward downstream business records. The standard Epic Systems data archival scope is downstream — Resolute AR posting history, GL journal history, worker master snapshots, supplier master snapshots, materials transaction history. Clinical record archival from Epic is a less common but supported scenario, typically for retiring a clinical system that was being consolidated INTO Epic (e.g., a small community hospital's legacy EHR being retired after Epic go-live). In that case we extract clinical records via HL7 v2 / CCDA / FHIR R4 export and archive in HL7-native or FHIR-native format with full clinical document fidelity preserved. State medical record retention rules apply — typically 7–30+ years.

Same HIPAA model as the live system, applied to the archive. The archive layer enforces role-based access: provider/clinical users see clinical records, billing users see financial records, retiree-self-service users see their own records only, auditors see read-only with full access logging. Every read access is logged (actor, timestamp, record retrieved, justification) and the log itself is retained per HIPAA accounting-of-disclosures rule §164.528. Break-glass access for emergencies is supported with mandatory after-the-fact review. The archive is encrypted at rest (AES-256) and in transit (TLS 1.3); key management goes through your existing KMS (AWS KMS, OCI Vault, Azure Key Vault, or on-prem HSM).

All of them. We've built archive retention rules for every US state's adult medical record retention (typically 5–10 years post last encounter), every state's pediatric medical record retention (age-of-majority + 5–10 years, capping at 21–28 years in most states), HIPAA accounting-of-disclosures (6 years), IRS records (7 years), Medicare/Medicaid records (10 years for cost reports, 5–10 for claims), 42 CFR Part 2 substance-use records (typically 6+ years), state public records laws where applicable (for public hospital systems), and Joint Commission medical staff records (typically permanent). Retention rules are configured per record class and per legal entity. Expiry triggers automated deletion with auditable proof-of-destruction.

Indefinitely, with cost-tiered storage. The architecture uses three tiers: hot (frequently queried, last 1–2 years, SSD-backed, sub-second query), warm (occasional query, 2–7 years, standard object storage, sub-minute query), and cold (rare query, 7+ years, archive-tier storage like S3 Glacier Deep Archive, restore-then-query within hours). Storage cost drops by ~80% per tier movement. For a typical 8-hospital system carrying 15 years of finance + HCM + downstream materials data, total archive footprint is in the 20–60 TB range and total annual storage cost runs $50–200K depending on access patterns — versus often $500K–1M+ of active Clarity storage and licensing cost the archive offsets.

No license-side action required. The Epic Systems data archival reads from Clarity using the same service-account pattern as any other Clarity consumer — your existing Clarity licensing covers it. The archive itself lives outside Epic in your cloud or on-prem object storage. Where archival enables savings is downstream: legacy systems being retired ahead of consolidation (Lawson, McKesson, etc.) can have their licensing terminated because their retention obligation is satisfied by the archive. For Epic itself nothing changes — you continue running the current Clarity footprint, but you can defer Clarity storage growth by archiving older records out and trimming Clarity retention to the operational reporting window (typically 2–3 years).