Compliance, clause by clause

Software alone does not make a company compliant. nil supplies the technical controls and the evidence that they work. Compliance also depends on your validation of nil for its intended use, your procedures, and your training. These pages show exactly where that line falls.

What nil supplies

  • Technical controlsAudit trail, electronic signatures, access control, operational and authority checks, and configuration that cannot reach production unvalidated.
  • Vendor validationA validation report for every nil release: requirements citing their regulation and risk, traced to the tests that prove them.
  • Your validation, generatedThe configuration specification, test protocols, executed reports, traceability matrices, and summary reports for your configuration, from the system itself.

What remains yours

  • Intended useValidating nil for your processes, with the evidence nil generates.
  • ProceduresWritten policies on accountability for electronic signatures, identity checks before issuing accounts, and training.
  • CertificationThe letter certifying to FDA that your electronic signatures are the legally binding equivalent of handwritten ones (21 CFR 11.100(c)).

The regulations

  • 21 CFR Part 11

    US FDA regulation on electronic records and electronic signatures.

    Built 13Partly built 2Planned 1Gap 1Customer's procedure 3Open question 1Not applicable 2

  • EU GMP Annex 11

    EU GMP guidance on computerized systems (2011 version, in force).

    Built 13Partly built 3Planned 4Customer's procedure 2Vendor 1Not applicable 3

  • ISO 13485:2016

    The international standard for medical device quality management systems.

    Built 11Partly built 4Planned 1