Configurable, never unvalidated

Most quality systems keep validation simple by allowing little change, or allow anything and leave validation to you. nil allows the change and carries the validation with it.

Two validations, both supported by nil

  • nil itself Validated by us for every release. Each requirement cites its regulation and risk and is traced to the tests that prove it; the validation report is generated from the requirements and the executed tests.
  • Your configuration Validated by you, with nil doing the bookkeeping: every change to validated configuration goes through a Configuration Validation record, below.

A clear line between validated and everyday changes

nil classifies everything it stores. Validated configuration (record types, workflows, permissions, dashboard tables, and gated settings) changes only through validation. Everyday changes (who holds a role, option list values, and holidays) take effect as usual and are audited. nil’s own test suite fails if anything is left unclassified.

  • On every pageThe footer states the validation state: validated, with its baseline, or the changes awaiting validation.
  • Every daynil checks production against its validated fingerprint every day and at every start-up. If anyone changes the configuration outside nil, through a script, the database, or a server setting, nil raises an alarm. The alarm stays until the change is either reverted, or accepted and then validated, in a signed Configuration deviation record.

How a change reaches production

  1. 1

    Design in a changeset

    Designers change a workspace copied from production’s configuration, trying it on masked copies of production records. The changeset records exactly which validated items changed.

    Refused when Nobody designs in production: once nil is live, production’s design screens are read-only.

  2. 2

    Plan the validation

    A Configuration Validation record names the changeset, the intended use, and the requirements with their risk and the reason for it. High and Medium risks need a test.

    Refused when A changeset that another active validation already changes, or relies on, cannot start without a recorded rationale.

  3. 3

    Approve the protocol

    The test protocol, generated from the requirements, is approved and signed before testing begins.

    Refused when Testing does not start on an unapproved protocol.

  4. 4

    Test in a validation environment

    A validation environment is built from production’s configuration plus the changeset. Tests are scripted and run by nil, scripted and run by a person, or unscripted; failures are explained as test incidents. Evidence is the environment’s own audit trail.

    Refused when An environment whose configuration does not reproduce production’s fingerprint is not used.

  5. 5

    Freeze the release package

    The tested changes, both configuration fingerprints, and the evidence are fixed into one package, identified by its SHA-256 hash.

    Refused when Approval is refused if anything changed after the freeze.

  6. 6

    Approve independently

    Someone who did not write the validation, design the change, or test it approves it with an electronic signature.

    Refused when nil names the conflict as soon as the people are set.

  7. 7

    Release

    nil applies exactly the frozen package to production. The result becomes the validated baseline, named by the validation and signed by its approval.

    Refused when The release changes nothing unless production still matches what was tested, or has changed only in items the release neither touches nor relies on.

Try testing, approval, and release

Run the tests, approve, and release. Until the approval, production refuses the change.

Changeset CS-000014 · CAPA record type

Demo data · try it

  1. 1 · Changeset

    Recorded

    • Added:Field Containment action, long text, required in Investigation
    • Changed:Investigation due after 30 days 20 days

    Designed by Sam Ortiz

  2. 2 · Configuration Validation CV-000006

    Testing

    • T-1 Containment action is required to leave InvestigationRisk: High
    • T-2 Investigation is due 20 days after it startsRisk: Medium
    • T-3 Existing CAPAs keep their recorded valuesRisk: High

    Unavailable due to:

    • T-1 has not been run.
    • T-2 has not been run.
    • T-3 has not been run.

    Tester: Lena Fischer. Approver: Morgan Mills, who neither designed nor tested the change

  3. 3 · Production

    Unchanged

    Unavailable due to:

    • No approved Configuration Validation covers this change.

An emergency release before approval is possible, with a reason and an electronic signature, and every page then says validation is pending; it can be rolled back while no record depends on it.

Generated, not written by hand

The documents an auditor asks for are generated from the Configuration Validation record and hashed into its release package. A PDF is only ever an uncontrolled rendering of them.

  • Test protocol
  • Executed test report
  • Traceability matrix
  • Validation summary report
  • Configuration specification and validated baselines

Assurance proportionate to risk

FDA’s Computer Software Assurance (CSA) guidance recommends assurance proportionate to risk, documented with records the system generates rather than screenshots. In nil, each requirement on a validation carries a risk, the testing follows from that risk, and the evidence is the validation environment’s own audit trail.

See the rest of nil

The modules, records, documents, and data-integrity controls that validation protects.

Product