Regulations

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

ISO 13485, clause by clause
ClauseAsks for (paraphrased)How nil answers itStatus
§4.1.6Documented procedure to validate QMS software for its application; before first use and after changes; proportionate to risk; records keptThe 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_validation_test::the_specification_shows_the_linePassing

Built
§4.2.4Document control: review, approval, revision status, availability, obsolete documentsDocument 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_test::released_revisions_are_frozen_and_read_by_everyonePassing

Built
§4.2.5Records legible, identifiable, retrievable, protected; retention at least the device lifetime or 2 years; changes identifiableNothing deleted; audit trail; record type versions

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

Partly built
§5.6Management review inputs (feedback, complaints, CAPA, audits, …)Reporting across modules Planned
§6.2Competence, training, effectivenessA 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_test::every_configuration_table_is_copiedPassing

Partly built
§7.3.9Design and development changes controlledChange Control template

Several requirements; see nil’s validation report.

Built
§7.4Purchasing; supplier evaluation and monitoringSupplier 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_status_test::supplier_status_records_decide_the_suppliers_statusPassing

Built
§7.5.8Identification of product throughout realizationParts 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_test::shipped_data_types_install_first_with_their_originPassing

Built
§7.6Monitoring and measuring equipment kept calibrated and identifiedInstruments 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_object_fields_test::entries_expire_by_their_valid_untilPassing

Partly built
§8.2.1–8.2.2Feedback; complaint handling with investigation and reporting decisionComplaints, 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_feedback_test::vigilance_decides_whether_a_complaint_is_feedbackPassing

Built
§8.2.3Reporting to regulatory authoritiesComplaints: reportable and report reference

Several requirements; see nil’s validation report.

Built
§8.2.4Internal auditsAudits template

Several requirements; see nil’s validation report.

Built
§8.3Nonconforming productNonconformance and Deviations templates; a nonconformance names the part affected, from the Parts list, and its revision

Proved by requirementAC-data-objects-21and testsupplier_status_test::nonconformances_name_the_part_affectedPassing

Built
§8.3.3Nonconforming product detected after deliveryRMA 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_feedback_test::returns_are_authorized_received_evaluated_and_dispositionedPassing

Built
§8.4Analysis of dataDashboards today; reporting later

Several requirements; see nil’s validation report.

Partly built
§8.5.2–8.5.3Corrective and preventive action, with effectiveness checks; without undue delayCAPA template; due dates per phase, overdue on dashboards, audited extensions

Proved by requirementAC-record-links-13and testrecords_test::resulting_records_are_linked_to_their_originPassing

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.