Regulations

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

Part 11, clause by clause
ClauseAsks for (paraphrased)How nil answers itStatus
11.10(a)Validation: accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered recordsVendor validation report traced from requirements; rule evaluator and SQL compiler proven equal; tamper-evident audit chain

Proved by requirementAC-validation-kit-1and testvalidation_report::specs_yield_requirements_with_regulations_and_riskPassing

Built
11.10(b)Accurate, complete copies, human-readable and electronicCanonical JSON export of configuration and snapshots; audit trail export

Proved by requirementAC-configuration-4and testconfiguration_test::exports_are_canonicalPassing

Partly built
11.10(c)Records protected and retrievable for the retention periodNothing is hard-deleted; accounts deactivated, never removed

Proved by requirementAC-user-administration-7and testadmin_users_test::users_are_never_deletedPassing

Partly built
11.10(d)Access limited to authorized peopleAllow-only roles, groups, module-scoped grants, visibility per record type; sessions time out

Proved by requirementAC-navigation-9and testrecords_test::the_jump_box_finds_records_only_the_person_may_seePassing

Built
11.10(e)Secure, computer-generated, time-stamped audit trail; changes don't obscure earlier entries; kept as long as the recordsAppend-only hash-chained audit trail, written in the same transaction; nobody can edit or switch it off

Proved by requirementAC-audit-trail-1and testaudit_trail_test::entries_record_actor_time_record_changes_and_reasonPassing

Built
11.10(f)Operational checks that enforce the permitted order of stepsWorkflows with phases and steps; rules checked on the server at every save and transition

Proved by requirementAC-record-types-5and testrecords_test::rules_are_enforced_on_every_save_and_stepPassing

Built
11.10(g)Authority checks: only authorized people sign, change, or use functionsEvery route requires a permission; per-module scopes; signing steps limited to holders

Proved by requirementAC-record-types-6and testrecords_test::only_assignees_act_and_unanimous_phases_votePassing

Built
11.10(h)Device (terminal) checks on the source of data, as appropriateNot claimed: a browser application with no device-bound inputs Not applicable
11.10(i)People who develop, maintain, or use the system are trainedUsers: Training module. Developers: vendor competence records Planned
11.10(j)Written policies holding people accountable for their signaturesThe 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 revisionsRecord 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_test::only_what_was_tested_is_releasedPassing

Built
11.30Open 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.50Signature shows printed name, date and time, and meaning; included in any display or printoutSignature 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_test::the_signature_shows_name_time_meaning_and_whether_it_holdsPassing

Built
11.70Signatures linked to their record; can't be copiedSignature 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_test::the_signature_shows_name_time_meaning_and_whether_it_holdsPassing

Built
11.100(a)Signature unique to one person; never reused or reassignedAccounts 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_users_test::invitations_refuse_bad_and_reused_addressesPassing

Built
11.100(b)Verify a person's identity before giving them a signatureInvitation by an administrator; the identity check is procedure Customer's procedure
11.100(c)Certify to FDA that e-signatures are legally bindingA 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 ownerThe 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_test::the_first_signing_needs_the_id_and_later_ones_the_passwordPassing

Built
11.300(a)Unique combination of ID and passwordUnique, 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_users_test::invitations_refuse_bad_and_reused_addressesPassing

Built
11.300(b)Passwords checked and revised periodicallyPassword policy and optional expiry; deactivation ends sessions

Proved by requirementAC-settings-2and testsettings_test::an_expired_password_must_be_changed_firstPassing

Built
11.300(c)Lost or compromised tokens deauthorizedTwo-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 reportedFailed 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_test::failed_signing_is_audited_and_throttledPassing

Built
11.300(e)Token devices tested periodicallyNo 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.