Implement 21 CFR Part 11-compliant electronic signatures in a custom clinical trial application using time-stamped signing and non-repudiation controls
Implement unique user identification and password authentication for each signer; 21 CFR 11.300 requires electronic signatures based on at least two distinct identification components (e.g., user ID and password, or biometric plus ID) for non-biometric signatures
Bind each electronic signature to its associated electronic record by storing a cryptographic link (hash of the record content) alongside the signature record; this ensures the signature is invalidated if the record is altered post-signing (21 CFR 11.70)
Capture and store with each signature: the printed name of the signer, the date and time the signature was applied (server-side timestamp, not client-side), and the meaning of the signature (e.g., 'reviewed and approved', 'entered by') per 21 CFR 11.50
Ensure the signature display on the screen and in any printout includes all three required elements (name, date/time, meaning) so that paper printouts of the signed record are legally equivalent to the electronic original under 21 CFR 11.20(b)
Implement session management controls: limit session duration, require re-authentication for signing after session timeout, and log all sign-in attempts including failures per 21 CFR 11.10(g)
Include the signed records and signatures in the audit trail, with separate audit entries for the act of signing distinct from the record creation or modification entries, to satisfy both 11.10(e) and 11.50 requirements simultaneously
Known gotchas
21 CFR 11.100(c) requires that signatories certify to the FDA that their electronic signatures are legally binding equivalents of handwritten signatures; this certification must be submitted to FDA before the electronic signatures are first used in a regulated application
Copying-and-pasting a displayed signature image from a PDF is not an electronic signature under Part 11; the system must capture the affirmative act of signing with the signer's authenticated identity at the moment of signing
Time stamps must be generated server-side using a synchronized, reliable clock; client-side timestamps can be manipulated and do not satisfy the 'computer-generated' requirement of 11.10(e)
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp