Medical Devices

AI for medical device quality

Every device or batch you ship needs a record proving it was built to the device master record, inspected, labeled correctly and released by someone authorized to release it. Litewave reads those device history records, travelers and inspection sheets, checks them against your specifications and the regulation you are inspected to, and surfaces the exceptions before release.

The rulebook your site is held to

US: the Quality Management System Regulation

  • 21 CFR Part 820 as amended by the QMSR, which incorporates ISO 13485:2016 by reference and took effect on February 2, 2026
  • The requirements the QMSR keeps on top of ISO 13485, including control of records under 820.35 and labeling and packaging controls under 820.45
  • Unique device identification under 21 CFR Parts 801 and 830
  • Medical device reporting under 21 CFR Part 803, and corrections and removals under Part 806

ISO 13485:2016

  • 4.2.3 medical device file and 4.2.5 control of records
  • 7.5.1 a record for each device or batch, giving traceability and the quantity manufactured and approved for distribution
  • 7.5.8 identification and 7.5.9 traceability, with the added requirements for implantable devices
  • 8.2.6 monitoring and measurement of product, including the identity of the person authorizing release
  • 8.3 control of nonconforming product and 8.5.2 corrective action

Records and computerised systems

  • 21 CFR Part 11, electronic records and signatures, audit trails and authority checks
  • ISO 13485 clause 4.1.6, validation of software used in the quality management system, proportionate to risk
  • Data integrity expectations expressed as ALCOA and ALCOA+, for paper and electronic records alike

EU, UK and international

  • EU MDR 2017/745 and IVDR 2017/746, including the manufacturer obligations in Article 10 and notified body assessment of the quality management system
  • UK MDR 2002, enforced by the MHRA, for devices placed on the Great Britain market
  • MDSAP audits covering the requirements of the participating regulators, including Health Canada, TGA, ANVISA and PMDA
  • ISO 14971 risk management, which ties nonconformances and complaints back to the risk file

Process-specific standards

  • Sterilization validation and routine control under ISO 11135, ISO 11137 and ISO 17665
  • Cleanroom classification and monitoring under ISO 14644
  • Your own process validation, inspection and test procedures

The QMSR retired the term DHR, not the record

The QMSR dropped the terms device master record, device history record and design history file. The obligations did not go away. ISO 13485 still requires a record for each device or batch that shows traceability, the quantity manufactured and the quantity approved for distribution, and the QMSR keeps its own requirement to inspect labeling before release for the correct UDI, expiration date, and storage and handling instructions. Most sites still call that record a DHR, and so do we.

What changed is the yardstick. FDA now inspects against ISO 13485 as incorporated by the QMSR, the same standard your notified body and your MDSAP auditor already use. One record set now has to satisfy all three, which makes the quality of each device record matter more, not less.

The documents this actually touches

Device history records, travelers and routers. Work orders and build records. Device master records, drawings, bills of material and specifications. Incoming, in-process and final inspection records. Functional and electrical test reports. Labeling inspection records, UDI and lot or serial number assignments.

Sterilization load records and certificates of processing. Cleanroom and environmental monitoring. Equipment calibration and maintenance records. Supplier certificates of conformance and analysis. Nonconformance reports, MRB dispositions and CAPA. Complaint files. Engineering change orders. Training records. Process validation protocols and reports.

What Litewave checks here

Device history record

  • Every operation on the traveler completed in sequence, signed and dated
  • Components and lot numbers match the bill of material at the revision in effect on the build date
  • Quantity started, scrapped, reworked and released reconciled, with no unexplained loss
  • Every in-process and final acceptance activity present, with results inside specification
  • Release signed by someone authorized to release, after every other record was complete

Labeling and identification

  • Labels issued, used, destroyed and returned reconciled for the lot
  • The label matches the approved revision, including UDI, lot or serial number and expiration date
  • The UDI recorded in the device record matches the one on the label
  • Labeling inspection performed and recorded before release

Nonconformance and rework

  • Every out-of-specification result has a nonconformance report
  • Every nonconformance has a disposition, and reworked product was re-inspected to the original acceptance criteria
  • Use-as-is dispositions and concessions carry the justification and approvals your procedure requires
  • Recurring nonconformances linked to CAPA rather than closed one at a time

Suppliers and processing

  • Supplier certificates checked against your purchasing specification
  • Supplier approved for this part at this revision
  • Sterilization load records inside validated parameters, with the certificate of processing tied to the lot
  • Calibration current on every instrument used for acceptance on the build date

Contract manufacturers work to more than one rulebook

If you build devices for other companies, every customer brings its own specifications, its own record format and its own release expectations, on top of your own quality system. Reviewers end up carrying several rulebooks in their heads at once.

Litewave applies the right rulebook to each customer’s records, so a reviewer starts from the exceptions for that customer rather than from a blank checklist.

Your workflow, mapped

What your team does today

Device history record review and release

What Litewave automates

DHR Review & Release

What your team does today

Nonconformance, MRB, complaint and CAPA investigations

What Litewave automates

Deviation Investigations

What your team does today

Supplier certificates, purchasing controls and supplier qualification

What Litewave automates

Supplier Quality & CoA Review

What your team does today

Procedure control, internal audit and QMSR gap assessment

What Litewave automates

QMS & Regulatory Compliance

What your team does today

Nonconformance, complaint and yield trending, management review

What Litewave automates

Quality Analytics

Where our evidence comes from

Litewave was built in pharmaceutical manufacturing, which is the strictest records regime in regulated industry. At a leading global generic API manufacturer, batch disposition time fell by 85% across 100 to 150 page paper batch records, with no eBPR migration and no SOP changes.

That matters for your site because the artifacts are structurally the same as yours: a master record defining what should happen, an executed record saying what did, in-process checks, supplier certificates, deviations, and a release decision somebody has to sign and defend. The engine that reconciles a 150 page executed record against a master record and a specification does not care what the product is. What changes is the rulebook it applies, and that is configuration.

Your device history record checks are configured to your specifications and your governing standard, by the team that built the pharmaceutical deployments.

Step 1

Bring one real record

A device history record, or a stack of supplier certificates. Something you actually execute, not a mock-up.

Step 2

We run a scoped evaluation

We configure the checks to your specification and your governing standard, run them on your records, and show you every finding with the source page cited.

Step 3

You compare it with your own reviewer

Your team reviews the same records the way they always do. You see where we agree, where we disagree, and where we found something they did not. Then you decide.

Questions we get asked

Does the QMSR change what a DHR review has to cover?

The name changed more than the substance. ISO 13485 still requires a record for each device or batch showing traceability and the quantities manufactured and approved for distribution, and the QMSR keeps its own requirement to inspect labeling, including the UDI, before release. Litewave is configured to the requirements as they now stand, and to whatever your procedures call the record.

Our device records are paper travelers. Is that a problem?

No. Our pharmaceutical deployments ran on paper records with no system migration. Litewave reads scanned travelers and inspection sheets as they are, so the floor keeps recording the way it does today.

Who releases the device?

You do. Litewave performs the review and assembles the evidence, with every finding linked to its source page. The release decision stays with the person your procedure authorizes, in your own quality system.

How is Litewave validated in our quality system?

As software used in the quality management system, under ISO 13485 clause 4.1.6 and your own procedure, with validation proportionate to the risk of each intended use. We supply the documentation you need to do that, scoped with you during procurement.

Guides for Medical Devices

All guides →

Related

Built for validated environments

Your data stays where your auditors expect it

Hosted in the region you choose

Litewave runs in a secure cloud environment in the region you choose, with your data encrypted in transit and at rest. Dedicated deployment options are scoped with you during procurement.

Your data never trains our models

Your documents are processed only in the cloud region you choose, under enterprise terms that do not allow any provider to train on them. They never train a model that any other customer touches. Where a model adapts to your site, such as the handwriting engine learning your operators, what it learns stays with your deployment.

21 CFR Part 11

Electronic records, electronic signatures and complete audit trails on every action, built to ALCOA+ data integrity principles.

EU GMP Annex 11, and building for what is next

Meets the currently effective Annex 11 expectations for computerised systems. We are building to the draft revised Annex 11 and the draft Annex 22 on AI while both remain in consultation, so nothing here is claimed as compliance with a standard that is not yet in force.

Ready for your validation

The validation documentation your quality unit needs to qualify Litewave under its own CSV or CSA procedure, risk-based and scoped with you during procurement, alongside Part 11 and Annex 11 assessments covering audit trail, electronic signature and access control.

AI governance you can inspect

Context of use, model versions, performance monitoring and change control are documented in line with the EMA and FDA guiding principles of good AI practice in drug development, so the model sits inside your quality system rather than beside it.

Advised from both sides of the inspection

A former FDA division director who edited the Investigations Operations Manual, the field guide its investigators follow on site. A former FDA investigator who then decided enforcement outcomes at CDER. A Qualified Person who certifies batch release under EU GMP. They advise in a personal capacity, and FDA does not endorse products or companies.

Evidence on every flag

Every extraction, check and recommendation links back to its source page. Nothing asserted is unverifiable.

Human in the loop by design

Litewave proposes, qualified people approve. Litewave never dispositions a batch or device on its own.

See it run on one of your own records

Bring something real. We will show you what Litewave finds in it and what it cites as evidence.