ISO 13485:2016
The international standard for medical device quality management systems. Each clause below says what it asks for, in our words, and how nil answers it.
Built 11Partly built 4Planned 1
| Clause | Asks for (paraphrased) | How nil answers it | Status |
|---|---|---|---|
| §4.1.6 | Documented procedure to validate QMS software for its application; before first use and after changes; proportionate to risk; records kept | The core of nil's design: a vendor validation report per release; validated templates; the configuration specification, baselines, and diffs; and the Configuration Validation record, through which every change to validated configuration is tested in a validation environment, approved and released, with generated validation documents Proved by requirementAC-configuration-validation-1and testconfiguration_ | Built |
| §4.2.4 | Document control: review, approval, revision status, availability, obsolete documents | Document Control module: signed review and release, frozen numbered revisions effective by date, the Library for everyone, signed withdrawal to Obsolete, redlines of each change, stamped PDFs of released revisions, signed periodic reviews on a per-document interval; files on documents (stored for good, hash-checked), external documents as files, abandoning a revision, the administrative-change route Proved by requirementAC-document-control-1and testdocuments_ | Built |
| §4.2.5 | Records legible, identifiable, retrievable, protected; retention at least the device lifetime or 2 years; changes identifiable | Nothing deleted; audit trail; record type versions Proved by requirementAC-audit-trail-1and testaudit_ | Partly built |
| §5.6 | Management review inputs (feedback, complaints, CAPA, audits, …) | Reporting across modules | Planned |
| §6.2 | Competence, training, effectiveness | A training sandbox: a copy of production's configuration and sample records where people practice without touching real records. Planned: a Training module (curricula tied to document revisions, assignments, effectiveness) Proved by requirementAC-environments-3and testenvironments_ | Partly built |
| §7.3.9 | Design and development changes controlled | Change Control template Several requirements; see nil’s validation report. | Built |
| §7.4 | Purchasing; supplier evaluation and monitoring | Supplier Management template: a supplier’s qualification or status change is a Supplier status record, and QA’s signed decision sets the supplier’s Status and requalification date on the Suppliers list Proved by requirementAC-data-objects-20and testsupplier_ | Built |
| §7.5.8 | Identification of product throughout realization | Parts as controlled data on every instance; records name the part they concern, its values copied with their version and frozen once signed Proved by requirementAC-data-objects-19and testtemplates_ | Built |
| §7.6 | Monitoring and measuring equipment kept calibrated and identified | Instruments as controlled data with a next calibration date: past it they show Expired and aren’t offered on records. The calibration template is planned. Proved by requirementAC-data-objects-16and testdata_ | Partly built |
| §8.2.1–8.2.2 | Feedback; complaint handling with investigation and reporting decision | Complaints, Returns, and Feedback template: everything is logged as a complaint; a vigilance reviewer decides whether it is one and whether it is reportable, a decision that it isn’t being signed and justified, with the feedback kept as its own record; returned product goes through RMA records Proved by requirementAC-modules-10and testcomplaints_ | Built |
| §8.2.3 | Reporting to regulatory authorities | Complaints: reportable and report reference Several requirements; see nil’s validation report. | Built |
| §8.2.4 | Internal audits | Audits template Several requirements; see nil’s validation report. | Built |
| §8.3 | Nonconforming product | Nonconformance and Deviations templates; a nonconformance names the part affected, from the Parts list, and its revision Proved by requirementAC-data-objects-21and testsupplier_ | Built |
| §8.3.3 | Nonconforming product detected after delivery | RMA records: a returned product evaluated as nonconforming can’t be dispositioned without its resulting nonconformance; the disposition is signed Proved by requirementAC-modules-11and testcomplaints_ | Built |
| §8.4 | Analysis of data | Dashboards today; reporting later Several requirements; see nil’s validation report. | Partly built |
| §8.5.2–8.5.3 | Corrective and preventive action, with effectiveness checks; without undue delay | CAPA template; due dates per phase, overdue on dashboards, audited extensions Proved by requirementAC-record-links-13and testrecords_ | Built |
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.