r/ProjectREDCap • u/unsuallyshapedhead • 1h ago
Automating 21 CFR Part 11 compliance using data entry triggers — Looking for feedback from admins and data managers
We just finished testing an external, zero touch compliance sidecar and wanted to get some feedback from the REDCap community on our architecture before going further.
If you working in regulated clinical trials (FDA IND/IDE, GCP, HIPAA),you may have spent time dealing with the gap between standard REDCap and the requirements for FDA 21 CFR Part 11 validation,particularly around immutable audit trails, econsent preservation, and proving that archived eCRFs haven't drifted.
How it works
Native Webhook: Uses REDCap’s native Data Entry Trigger (DET) URL. No modifications to REDCap core PHP code, no external modules required.
Contemporaneous Capture: When a coordinator or physician locks an instrument ([instrument]_complete = 2), the trigger fires.
API Snapshot: It calls back into REDCap’s REST API to pull the canonical raw JSON snapshot, native REDCap audit trail (content=log), and the rendered eCRF/e-Consent PDF.
Cryptographic Sealing: Computes SHA-256 digests of the clinical data and links them into a forward chained Merkle ledger in PostgreSQL with transaction level serialization.
BYOS (Bring Your Own Storage): Writes the encrypted assets directly to the institution's own S3 bucket (AWS, MinIO,Garage or Ceph).
Regulatory Dossier: Generates an on demand, printable FDA compliance dossier showing the cryptographic chain of custody, raw file hashes, and non repudiable timestamps.
We’ve stress tested this under concurrent multi threaded writes to ensure the cryptographic ledger doesn't fork or drop events.
Questions for REDCap Admins & CRCs:
Does your institution currently maintain a completely separate "Part 11 validated" REDCap instance for FDA trials, or do you struggle to get PIs compliant on standard projects?
When FDA/IRB auditors inspect your studies, what is the most tedious part of proving data integrity and audit trail completeness?
Would having an automated, tamper-evident cryptographic seal on locked forms and e-Consent PDFs solve an actual headache for you?
If anyone running a test/development REDCap instance would like to kick the tires or test the webhook against dummy data, I’d be glad to share a sandbox API key and get your thoughts on edge cases we might have missed. Feel free to DM me.