21 CFR Part 11
US FDA regulation on electronic records and electronic signatures. Each clause below says what it asks for, in our words, and how nil answers it.
Built 13Partly built 2Planned 1Gap 1Customer's procedure 3Open question 1Not applicable 2
| Clause | Asks for (paraphrased) | How nil answers it | Status |
|---|---|---|---|
| 11.10(a) | Validation: accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records | Vendor validation report traced from requirements; rule evaluator and SQL compiler proven equal; tamper-evident audit chain Proved by requirementAC-validation-kit-1and testvalidation_ | Built |
| 11.10(b) | Accurate, complete copies, human-readable and electronic | Canonical JSON export of configuration and snapshots; audit trail export Proved by requirementAC-configuration-4and testconfiguration_ | Partly built |
| 11.10(c) | Records protected and retrievable for the retention period | Nothing is hard-deleted; accounts deactivated, never removed Proved by requirementAC-user-administration-7and testadmin_ | Partly built |
| 11.10(d) | Access limited to authorized people | Allow-only roles, groups, module-scoped grants, visibility per record type; sessions time out Proved by requirementAC-navigation-9and testrecords_ | Built |
| 11.10(e) | Secure, computer-generated, time-stamped audit trail; changes don't obscure earlier entries; kept as long as the records | Append-only hash-chained audit trail, written in the same transaction; nobody can edit or switch it off Proved by requirementAC-audit-trail-1and testaudit_ | Built |
| 11.10(f) | Operational checks that enforce the permitted order of steps | Workflows with phases and steps; rules checked on the server at every save and transition Proved by requirementAC-record-types-5and testrecords_ | Built |
| 11.10(g) | Authority checks: only authorized people sign, change, or use functions | Every route requires a permission; per-module scopes; signing steps limited to holders Proved by requirementAC-record-types-6and testrecords_ | Built |
| 11.10(h) | Device (terminal) checks on the source of data, as appropriate | Not claimed: a browser application with no device-bound inputs | Not applicable |
| 11.10(i) | People who develop, maintain, or use the system are trained | Users: Training module. Developers: vendor competence records | Planned |
| 11.10(j) | Written policies holding people accountable for their signatures | The customer's procedure; nil can host and train it | Customer's procedure |
| 11.10(k) | Control of system documentation, with change control and an audit trail of revisions | Record type versions (immutable once published), a configuration specification generated from the live system, signed validated baselines and their differences, a vendor validation report per release, and Configuration Validation records that release exactly what was tested. Proved by requirementAC-cv-records-3and testcv_ | Built |
| 11.30 | Open systems: extra controls (encryption, signature standards) | Deployment is not decided yet. Whether a hosted instance is an open or a closed system is the customer's determination; TLS is used throughout either way. | Open question |
| 11.50 | Signature shows printed name, date and time, and meaning; included in any display or printout | Signature block on the record and in the audit trail; the signing panel names the record, the step, and the outcome, and the receipt names meaning and time Proved by requirementAC-e-signatures-3and testsignatures_ | Built |
| 11.70 | Signatures linked to their record; can't be copied | Signature bound to a hash of the exact content signed; a revision-controlled record shows each signature under the revision it was signed on Proved by requirementAC-e-signatures-4and testsignatures_ | Built |
| 11.100(a) | Signature unique to one person; never reused or reassigned | Accounts and sign-in addresses are never reassigned; under Microsoft Entra ID, each Microsoft account links to one nil account, never relinked Proved by requirementAC-user-administration-2and testadmin_ | Built |
| 11.100(b) | Verify a person's identity before giving them a signature | Invitation by an administrator; the identity check is procedure | Customer's procedure |
| 11.100(c) | Certify to FDA that e-signatures are legally binding | A letter from the customer | Customer's procedure |
| 11.200(a) | Two components; first signing in a session asks for both, later ones at least one; only the genuine owner | The first signing in a session asks for the user ID and the password; every later signing asks for the password again. Under Microsoft Entra ID, each signature takes the signer through a fresh Microsoft sign-in. Proved by requirementAC-e-signatures-1and testsignatures_ | Built |
| 11.300(a) | Unique combination of ID and password | Unique, never-reassigned sign-in addresses; under Microsoft Entra ID, one Microsoft credential per person, and one audited emergency administrator account Proved by requirementAC-user-administration-2and testadmin_ | Built |
| 11.300(b) | Passwords checked and revised periodically | Password policy and optional expiry; deactivation ends sessions Proved by requirementAC-settings-2and testsettings_ | Built |
| 11.300(c) | Lost or compromised tokens deauthorized | Two-factor recovery codes exist; an administrator can't yet reset someone's two-factor, and deactivation is the only lever | Gap |
| 11.300(d) | Unauthorized attempts detected and reported | Failed signing attempts throttled and audited; repeated failed sign-ins pause sign-in, warn the owner by email, and lock the account until an administrator unlocks it Proved by requirementAC-e-signatures-5and testsignatures_ | Built |
| 11.300(e) | Token devices tested periodically | No hardware tokens | Not applicable |
Reading this table
- Built
- In nil today. Where one requirement answers the clause, its trace names that requirement and the test that proves it, passing in nil’s suite; where several do, the row says so and nil’s validation report lists them.
- Partly built
- Part of the clause is in nil today; the row says which part is not yet.
- Planned
- On the roadmap, not in nil today.
- Gap
- A known shortfall, named in the row, to be closed.
- Customer's procedure
- Met by your procedures; nil may record or support it.
- Open question
- Depends on a decision not yet made; the row says which.
- Not applicable
- The clause does not apply to a system like nil; the row says why.