auditing-deidentification-runs

To create a tamper-evident audit trail for clinical text de-identification, run audit-enabled de-identification, generate a PHI-free report with redaction spans and detector provenance, and sign it using HMAC-SHA256. This produces verifiable compliance evidence without exposing plaintext identifiers.

A PHI-free audit report records redaction spans, labels, confidence thresholds, content hashes, and residual risk without storing protected health information values. It supports HIPAA compliance by allowing reviewers to verify de-identification decisions and redaction integrity without accessing original patient data.

To verify the integrity of a de-identification audit report, use the securely stored HMAC key to check the HMAC-SHA256 signature. This verification validates the report's integrity and its optional bindings to the original and de-identified text, ensuring the audit evidence has not been altered.

GDPR compliance benefits from PHI-free audit evidence for clinical text redaction workflows by providing reproducible, signed records of de-identification decisions. This allows internal quality checks and regulatory reviews to verify redactions and residual risk without retaining or exposing plaintext identifiers.

An OpenMed de-identification audit record includes redaction spans, labels, confidence thresholds, detector provenance, content hashes, and residual-risk reporting. It captures the full context of redaction decisions while remaining free of plaintext protected health information.

Yes, you can check de-identification residual risk without accessing original clinical notes by reviewing the generated PHI-free audit report. It includes residual-risk reporting and structured span provenance, enabling reproducibility checks and internal review without exposing plaintext identifiers.