Delete User Data

Customer-directed deletion of the PHI this API key controls.

Deletes coding traces, coding cache entries, and chart review jobs owned by this API key, and writes an immutable purge record (see record_data_purge). Audit and disclosure ledgers are retained — see the retention note below.

⚠ This is not a "HIPAA right to deletion", and it must not be described as one. HIPAA gives individuals no right to erasure. 45 CFR grants a right of access (§164.524), a right to request amendment (§164.526) and a right to an accounting of disclosures (§164.528) — deletion is not among them. That is a GDPR concept (Article 17), not a HIPAA one.

What this endpoint actually is: a covered entity instructing its business associate to delete data the business associate holds on its behalf, which is ordinarily how a BAA works. It is a customer action, not a patient right.

Consequences for whoever maintains this:

• A patient asking us directly to erase their record is not entitled to it under HIPAA. Such a request belongs with the covered entity, which owns the designated record set and decides — unless a specific BAA delegates that response to us.
• Deleting on request is still correct when the customer directs it and no retention obligation applies. But an accepted §164.526 amendment must be appended or linked, not silently overwritten, so the historical record and its audit trail survive.
• Retention here is deliberately per-category (chart reviews 90d, coding traces 365d, cache 90d, usage events ~7y for billing/tax), not a blanket six years. §164.530(j)(2)'s six years applies to documentation required by the rule — policies, communications, actions, activities, designations — not to every patient record or coding transaction. Do not "simplify" these into one six-year default.