Retention policies own the long tail of a FHIR storage bill. A deployment that keeps everything forever writes a check every quarter for data nobody will read. A deployment that expires too aggressively loses audit surface when a regulator asks about it. Naming the policy explicitly is the discipline that keeps both failure modes off the invoice.
The trade lives in the specifics. For related walkthroughs, more on US digital health infrastructure collects the surrounding material.
What Retention Actually Decides
A retention policy says how long each class of FHIR data stays in the archive before it is expired or migrated. Different classes usually have different windows:
- Current-state resources: often kept for the lifetime of the deployment.
- Version history: kept for a defined window, often between one and seven years.
- Attachments and DocumentReference payloads: often kept longer than history because the regulatory expectation is stricter.
- Audit trail entries: kept for the compliance framework the deployment is subject to.
Each line is a separate decision. A pass through the site's FHIR storage bill projector can bracket the total against different retention windows.
The Compliance Floor
Most retention decisions start with a compliance floor. HIPAA implies six-year retention for certain data classes; state laws add their own floors; specific regulatory frameworks push further. The floor is not a suggestion; it is the minimum the archive must hold.
Deployments that inherit the strictest floor across every framework pay the most for storage. Deployments that name the applicable floor per data class pay the actual regulatory cost, no more.
The Business Ceiling
Above the floor sits a business ceiling: the point at which extra retention no longer adds value. Clinical decision support usually reads recent data; longitudinal research reads older data; billing usually reads a defined trailing window. Above the ceiling the data is legally retained but functionally unread.
The disciplined pattern is to migrate data above the ceiling to cold storage. For the tiering framing, the cold storage line is where retention past the ceiling belongs.
History Retention Interacts With Cost
Version history is where retention policy has the largest cost impact. A deployment that keeps full history for seven years and updates resources frequently accumulates a history table many times the size of current state. For the specific split, history table vs current state: doubling your storage bill quietly covers the mechanics.
Compaction is a partial mitigation. Older history rows can be compacted into monthly snapshots that lose fine granularity but preserve the outline. Whether compaction is acceptable depends on the compliance framework and the audit use case.
Attachment Retention Is a Category of Its Own
Attachments carry a different regulatory expectation than resource metadata. Clinical documents, imaging results, and lab reports often have longer retention floors than the enclosing resources. A retention policy that treats attachments uniformly with other resources will either over-retain or under-retain.
Name attachment retention as its own line. The number is usually different from the resource retention window, and the difference matters.
Documenting the Policy Publicly
Every retention decision should be documented in a policy that names the class, the window, and the framework driving it. When a regulator or auditor asks why the deployment retains a specific class for a specific window, the policy is the answer.
Policies that live in institutional memory decay when the person who authored them leaves. Public documents survive.
Reading the Curve Backwards
A useful exercise is to project the archive size under the current retention policy for five years, ten years, and permanent retention. The three numbers are usually revealing. For the estimation method that supports the projection, estimating storage before you commit to a FHIR platform is the accompanying reference. And for the wider hidden-cost framing, the FHIR storage costs you forgot to budget collects the other lines that scale with retention.
Retention policy is where finance meets compliance in a FHIR deployment. Owning the answer is the shortest path to controlling the bill.
Sources
- HHS canonical HIPAA FAQ covering record retention - HHS canonical HIPAA FAQ covering record retention obligations that shape FHIR retention policy