Guide / Whitepaper United States European Union Canada International Regulatory Quality Manufacturing & Supply Chain IVD

Explainer · Deviations · 23 min read

Planned and Unplanned Deviations: What They Are and How to Handle Them

"Deviation" is one of the most used words in a medical device quality system, and one of the least defined. This guide explains the two kinds, what the regulations actually say, how to run each one properly, the most common mistakes, and what happens when deviations are handled badly.

Planned deviation

Approved before it happens

A deliberate, temporary departure from an approved specification, procedure or process, limited by quantity, lots or time, and justified and risk-assessed in advance.

Unplanned deviation

Found during or after

An unexpected departure that nobody approved: a step skipped, a parameter out of range, an environmental excursion. It has to be documented, assessed, investigated and closed.

The companies and devices in the worked examples are fictional. The regulations and standards cited are real.

The two kinds of deviation

A deviation is any departure from something you've approved: a specification, a procedure, a work instruction, a validated process, a test method. What separates the two kinds is when the decision was made.

Planned deviation

You know in advance that you need to depart from an approved requirement, for a short time or a set amount of product, and you get approval first. Typical reasons:

  • A component is short and a few lots will use an equivalent alternative while the permanent change is processed.
  • A piece of equipment is down and a different, already-qualified one will be used for a set period.
  • A one-off engineering or pilot run needs a step done differently.
  • A supplier asks, before shipping, to deliver material with a characteristic slightly outside your specification.

Key features: approved before use, bounded, justified, risk-assessed, expires.

Unplanned deviation

Something departed from the approved way of working and nobody approved it. You find out during the work or afterwards. Typical examples:

  • An operator skipped or reordered a step in the work instruction.
  • A process parameter ran outside its validated range.
  • A cleanroom or storage temperature excursion.
  • Production or test equipment was found out of calibration after it had been used.
  • The wrong revision of a procedure or drawing was used.

Key features: discovered, contained, assessed, investigated, closed.

Where the word comes from

"Deviation" is a company term, borrowed largely from pharmaceutical good manufacturing practice, where the drug rules say it outright: deviations from written production procedures must be recorded and justified.[1] The device rules are built differently. Neither ISO 13485 nor FDA's Quality Management System Regulation (QMSR) defines a "planned deviation" or an "unplanned deviation". They frame the same ground through production and process controls, process validation, control of nonconforming product, document and change control, and corrective action.[2]

The vocabulary standard does help. The QMSR applies the terms and definitions in clause 3 of ISO 9000:2015, alongside those in ISO 13485, except where FDA overrides them.[3][4] ISO 9000:2015 defines two terms that map neatly onto this topic:[5]

  • Deviation permit: permission to depart from the originally specified requirements of a product or service before it is realized, usually for a limited quantity or period and a specific use. That is a planned deviation.
  • Concession: permission to use or release a product or service that doesn't conform to specified requirements, again usually limited in quantity, time and use. That is a decision made after the fact, on product that already exists.

You may never see "deviation permit" in a device company's procedures, but the distinction behind it is a useful test: was permission given before the product was made, or after? Your procedure can use any names you like, as long as it defines them and each one gets the controls the requirements call for. ISO published a new edition, ISO 9000:2026, in May 2026. The QMSR references the 2015 edition specifically, so those are the definitions that apply in the US.[5]

How deviations relate to other quality records

Deviations sit in a family of records that people blur together. The table below keeps them apart. It matches how our change request vs change order guide separates a change, a planned deviation and a concession.

RecordWhat it isWhen it's approvedMain ISO 13485 hook
Planned deviationA temporary, bounded departure from an approved requirementBefore it happensNot named. Controlled through 4.1.4, 7.5.1, 7.5.6, 7.3.9 or 7.4 depending on what it touches, and your procedures
Unplanned deviationAn unapproved departure found during or after the workNever approved; recorded when found, then assessed and closedNot named. 7.5.1, 7.5.6, 7.6, 8.2.5, and 8.3 if product is affected
NonconformanceProduct (or material) that doesn't meet a requirementRecorded when found; disposition approved8.3
ConcessionA disposition: use or release nonconforming product anywayAfter the fact, on specific product8.3.2
ChangeA permanent change to a product, process or documentBefore implementation4.1.4, 4.2.4, 7.3.9, 7.5.6
CAPAAction to remove the cause of a nonconformity so it doesn't recur (or, for preventive action, doesn't occur)Planned and reviewed for effectiveness8.5.2, 8.5.3

In practice they link up like this:

Unplanned deviationproduct affected? Open or link a nonconformance and decide disposition. "Use as is" is a concession.
Unplanned deviationsystemic or repeating cause? Open a CAPA.
Planned deviationneeded again and again? Make it a permanent change, or fix the cause through a CAPA.
CAPAfix changes the product, process or documents? Implement it through change control.

Some companies keep deviations and nonconformances in one record type with a "product affected" field; others keep them separate and link them. Either works if the procedure is clear and the ISO 13485 clause 8.3 controls are applied whenever product is affected.

What the regulations say

The specific word is rare, but the expectations are clear. Here is where they come from, market by market.

United States · QMSR

Since 2 February 2026, 21 CFR Part 820 requires a quality management system that complies with ISO 13485:2016, which it incorporates by reference, plus FDA's additional requirements.[3][4] So the ISO 13485 clauses below are US requirements too. FDA's additions route advisory notices (clauses 7.2.3, 8.2.3 and 8.3.3) through 21 CFR Part 806 on corrections and removals, and failing any applicable requirement renders a device adulterated.[3]

European Union · MDR and IVDR

Manufacturers must have procedures that keep series production in conformity, and a quality management system covering, among other things, product realization, supplier control, corrective and preventive action with effectiveness checks, and monitoring of output and data analysis (MDR Article 10(9); IVDR Article 10(8)).[8][9] Under Annex IX, the quality system documentation must cover the control of devices that fail to conform, verification and quality assurance at the manufacturing stage, and the tests carried out before, during and after manufacture.[8][9]

Canada · MDSAP

Health Canada requires manufacturers of Class II, III and IV devices to be audited under the Medical Device Single Audit Program, with quality system certificates issued against ISO 13485 by MDSAP auditing organizations.[10] The same clauses therefore drive how deviations are audited.

Combination products

For a combination product that includes a device and a drug, 21 CFR Part 4 lets you base your system on either the drug CGMPs or the QMSR, adding named provisions from the other.[11] If your system is built on the drug CGMPs, the drug rule applies directly: deviations from written production and process control procedures must be recorded and justified.[1][11] If it's built on the QMSR, that drug section isn't on Part 4's list of add-ons, but the ISO 13485 controls below still apply.

In the EU, the Commission proposed a targeted revision of the MDR and IVDR on 16 December 2025. At the time of writing it was still going through the legislative process, and the regulations in force are the ones cited here.[12]

The ISO 13485 clauses that matter for deviations

Paraphrased, not quoted. Read the standard itself for the exact wording.[2]

ClauseTopicWhy it matters for deviations
4.1.4Changes to QMS processesChanges to processes must be evaluated for their impact on the quality system and on the devices produced. A planned deviation is a temporary process change, so it needs that evaluation.
4.2.4, 4.2.5Documents and recordsApproved documents define the "normal" you're deviating from. Records must stay legible, identifiable and retrievable, and changes to them must be identifiable.
6.4.1Work environmentWhere environmental conditions can affect product quality, requirements and monitoring must be documented. An excursion is a departure from them.
7.3.9Design changesA "temporary" departure from a design output is still a design question. If it touches a specification, its significance has to be judged and approved before use.
7.4PurchasingSupplier controls, purchasing information (including advance notice of supplier changes) and verification of purchased product. Supplier-requested deviations are handled here, under your control, not the supplier's.
7.5.1Control of productionProduction must run under controlled conditions, including documented procedures and monitoring of process parameters. A record for each medical device or batch (the production record, formerly called the DHR in the US) must provide traceability and be verified and approved, so it should show any deviation that applied.
7.5.6Process validationValidated processes need defined criteria for revalidation and approval of changes. Running outside validated parameters, planned or not, has to be judged against them.
7.5.8, 7.5.9Identification and traceabilityOnly product that passed its inspections and tests, or was released under an authorized concession, may be dispatched or used. Affected units and lots must be traceable.
7.6Monitoring and measuring equipmentWhen equipment is found out of specification, you must assess and record the validity of earlier results and act on the equipment and any affected product.
8.2.5, 8.2.6Monitoring processes and productWhen processes don't achieve planned results, correction and corrective action are taken as appropriate. Product release needs evidence of conformity and a record of who released it.
8.3Nonconforming productIdentify, document, segregate, evaluate and disposition nonconforming product. The evaluation includes deciding whether an investigation is needed and whether an external party responsible for the problem (such as a supplier) must be told.
8.3.2Found before delivery (concession)Nonconforming product can be accepted by concession only with a justification, an approval and regulatory requirements met, and the person who authorized it must be recorded.
8.3.3Found after deliveryTake action appropriate to the effects, and issue advisory notices under your procedures and the regulations.
8.4Data analysisTrends in processes and product feed improvement. This is where deviation trending belongs.
8.5.2Corrective actionFind causes, act without undue delay and in proportion to the effects, check the action doesn't harm safety, performance or regulatory compliance, and review effectiveness.

Risk management runs through all of it. ISO 13485 requires documented risk management in product realization, and ISO 14971 expects information from production and post-production, which includes what your deviations reveal, to be collected and reviewed for its effect on risk.[2][13]

Running a planned deviation, step by step

A planned deviation is a small, temporary change, and it deserves a change's discipline in a smaller package. The goal is that anyone looking at the record later can see what was allowed, why it was safe, who approved it, which product it covered and when it ended.

  1. Describe it precisely

    What requirement, in which document and revision, is being departed from, and what will be done instead. "Use alternative bottle" isn't enough; name the part numbers and the approved alternative.

  2. Justify it

    Why it's needed and why a permanent change isn't the answer right now. If the honest answer is "this will keep happening", raise a change request instead or alongside.

  3. Set hard limits

    A maximum quantity, named lots or serial ranges, an end date, or all three, whichever comes first. Open-ended planned deviations aren't planned deviations.

  4. Assess the risk and the impact

    Use your ISO 14971 risk analysis: does the departure add a hazard or weaken a risk control?[13] Check the validated state of any process involved against your revalidation criteria, the design outputs and labeling it touches, and your regulatory commitments. A departure that would change something described in your 510(k), PMA or technical documentation needs the same regulatory assessment as a permanent change; the regulatory impact check in our change control guide walks through it.

  5. Define extra controls

    Additional inspection, testing, sampling or sign-offs that compensate for the departure, and the acceptance criteria for them.

  6. Approve before use

    By the functions your procedure names for this kind of departure: typically quality plus the owners of the process, the design and, where filings could be affected, regulatory. No product is made under the deviation until it's approved.

  7. Communicate and mark the product

    Train or brief the people doing the work, make the deviation available at the point of use, and reference its number in the production record of every lot or unit made under it so traceability is complete.[2]

  8. Expire and close

    When the limit is reached, stop. Confirm the extra controls were done and results met the criteria, list the affected lots, and close the record. Anything that went outside the approved limits is an unplanned deviation in its own right.

  9. Decide what's next

    If you'll need it again, make the permanent change through change control, or fix the underlying cause through CAPA. Don't renew. Include planned deviations in trending.

What a planned deviation record should contain

  • Unique number, title and owner
  • The requirement departed from: document, revision, section
  • What will be done instead, precisely
  • Justification, and why not a permanent change
  • Limits: quantity, lots or serials, start and end dates
  • Risk assessment and link to the risk management file
  • Validation, design, labeling and regulatory impact conclusions
  • Extra controls and acceptance criteria
  • Approvals, dated, before the start date
  • Affected lots or units, referenced in their production records
  • Closure: results, actual quantities, follow-up change or CAPA

Handling an unplanned deviation

An unplanned deviation is a problem to manage, not a form to fill in. The order of the first steps matters: protect product and patients first, then understand what happened.

  1. Stop and contain

    Stop the affected operation if needed. Identify and segregate product that could be affected, including work in progress and finished goods, and put it on hold.[2]

  2. Record it right away

    What happened, where, when, who found it, which equipment, materials, lots or units, and what was done immediately. Capture data and evidence before it's lost: charts, logs, photos, retained samples.

  3. Assess the impact

    Does it affect product quality, safety or performance, the validated state of a process, or a regulatory commitment? How far back does it go? For equipment found out of calibration, assess every result produced since the last good calibration.[2] Update the risk analysis if the deviation reveals a new hazard or failure mode.[13]

  4. Classify it

    Many companies grade deviations so the investigation effort fits the risk (see the table below). This is common practice, not a regulatory requirement. Define the levels in your procedure.

  5. Investigate in proportion

    Find the root cause, not just the immediate trigger. A minor, one-off procedural slip may need a short documented rationale; a major or critical deviation needs a structured root cause analysis. "Human error" alone is rarely a root cause: ask why the error was possible.

  6. Disposition affected product

    If product doesn't meet requirements, handle it as nonconforming product: rework, scrap, return, or use or release under concession, which needs a justification, an approval, regulatory requirements met and the authorizer recorded.[2] If testing shows the product does conform, record that evidence.

  7. Check reportability if product left your control

    Decide whether field action is needed. In the US, a correction or removal made to reduce a risk to health, or to remedy a violation that may present one, must be reported to FDA within 10 working days of starting it; one that isn't reportable still needs a record, including the justification for not reporting.[14] In the EU, field safety corrective actions and serious incidents are reported under the MDR and IVDR vigilance articles.[8][9]

  8. Decide on CAPA

    Open a CAPA when the cause is systemic, the risk is significant, or the same deviation has happened before. Write down the reasoning when you decide not to.[2]

  9. Close on time, and trend

    Close only when the investigation, product disposition and any field decision are complete and approved. Set a closure target in your procedure, and require justified, approved extensions. Trend deviations by process, product, equipment, supplier and cause, and review the trends in management review.

A common classification scheme

Not required by any regulation, but widely used. The names and definitions are yours to set.

LevelTypical meaningTypical response
MinorNo plausible effect on product quality, safety, performance or validated state; for example a documentation slip caught and correctedRecord, correct, short rationale, trend
MajorCould affect product quality or a validated process, but no likely harm to patients or usersContainment, documented root cause investigation, product disposition, CAPA decision
CriticalCould affect patient or user safety, or affected product may have reached the fieldImmediate escalation to management, full investigation, CAPA, reportability and field action decision

Planned or unplanned? Which record do I need?

A quick guide to the usual record for common situations. Use it as a starting point for your own procedure, not a substitute for it.

SituationUsual recordMust-haves
We want to depart from a requirement for a few lots or a short timePlanned deviationJustification, limits, risk assessment, approval before use, lots referenced in production records, expiry
The departure touches a validated process, design output, labeling or filingPlanned deviation with full impact assessment, or a change if it can't be justified as temporaryRevalidation decision, design and labeling review, documented regulatory conclusion
We want the departure to be permanentChange request and change orderThe controls in our change control guide
A procedure wasn't followed, but no product could be affectedUnplanned deviation (often minor)Record, impact rationale, correction, trend
Something went wrong and product could be affectedUnplanned deviation plus nonconformanceContainment, investigation, disposition under 8.3, concession only with justification and authorized approval
Affected product has left our controlUnplanned deviation, nonconformance and field action assessmentAction under 8.3.3, reportability decision (21 CFR 806, EU vigilance), CAPA
The same deviation keeps happening or keeps being renewedCAPA, or a permanent changeRoot cause, action, effectiveness check
A supplier asks to ship material outside our specificationPlanned deviation (before shipment) or concession (after receipt), under our QMSOur own risk assessment and approval; supplier corrective action request if it recurs

Two worked examples

Both companies and products are fictional.

Planned deviation IVD reagent kit

Halvern Diagnostics: a temporary bottle for a wash buffer

Situation. Halvern makes the Corvane CRP immunoassay kit. Its wash buffer concentrate is filled into a 50 mL bottle, and the bottle supplier warns of a six-week backorder. The same supplier can deliver a 60 mL bottle made from the same resin, with the same closure.

Decision. Manufacturing raises a planned deviation rather than waiting: fill volume stays at 50 mL, only the container changes.

  • Limits: kit lots 26-114 to 26-116 only, or until 31 March, whichever comes first.
  • Impact and risk: same material and closure, so the container's contact surface chemistry is unchanged; the stability team reviews the existing data, including the effect of the extra headspace, and agrees it supports the 60 mL bottle for this use, with real-time stability samples pulled from the first deviation lot as a check. The label fits without change. Regulatory checks the submissions and technical documentation, finds the bottle size isn't specified there, and records "no submission needed" with the reason.
  • Extra controls: fill volume check at an increased sampling rate; leak test of the closure on the new bottle.
  • Approvals: quality, manufacturing, R&D and regulatory, all before the first fill.
  • Traceability: the deviation number is entered in the batch record of each of the three lots.
  • Closure: three lots made, all checks passed. Because the supplier says shortages may recur, Halvern opens a change request to qualify the 60 mL bottle as a permanent alternate instead of renewing the deviation.

Unplanned deviation Surgical stapler

Brevik Surgical: a torque driver found out of tolerance

Situation. At its scheduled calibration, a torque driver used to fasten the anvil assembly on the Tessaro linear stapler reads below its tolerance. Since its last good calibration it has been used on four lots: two are still in the warehouse, one is at a distribution center and one has shipped to hospitals.

  • Contain: the driver is tagged out of service; the two in-house lots and the distribution center lot are placed on hold.
  • Record and assess: an unplanned deviation is opened the same day. Under-torque could let the anvil shift, which could malform staples, a hazard already in the risk file. The team assesses the validity of everything the driver produced since its last good calibration, as clause 7.6 requires.
  • Classify: critical, because affected product may have reached the field. That means immediate escalation to management and a field action decision.
  • Investigate: retained samples and units pulled from the held lots are tested for fastener torque and staple formation. All meet specification, because the actual shortfall was inside the design margin. Root cause: the driver had been dropped and nobody checked it afterwards; there was no daily verification.
  • Disposition: held lots are re-torqued under an approved rework instruction, re-inspected and released.
  • Field decision: with test evidence that shipped units conform, the team decides no correction or removal is needed and documents the rationale in the deviation record. Had they decided to correct or remove product, 21 CFR Part 806 would apply.
  • CAPA: opened, because the same gap exists at every torque station: daily verification against a reference, a drop-and-check rule, and a review of calibration intervals. Effectiveness is checked after three months of verification records.

Common mistakes, and the fix

The retroactive "planned" deviation

Approved after the product was made. That's an unplanned deviation, and calling it planned makes the record misleading. Record it as unplanned and investigate why approval was skipped.

A back door around change control

Planned deviations used to make what are really permanent changes, without the full assessment. If you intend to keep it, it's a change.

Open-ended or serial deviations

No end date, or the same deviation renewed again and again. Set hard limits and convert repeats into a change or a CAPA.

No risk assessment

"Low risk" with no reasoning. Tie the assessment to the risk management file and state which risk controls are affected.[13]

Ignoring the validated state

Running outside validated parameters without checking them against your revalidation criteria.[2]

Closing without a root cause

"Operator retrained" as the only action. Ask why the error was possible, and fix that.

Downgrading to avoid CAPA

Classifying a deviation as minor so it doesn't need a CAPA. Define the levels objectively and have quality confirm the classification.

No link to lots or serials

Nobody can say which units were made under the deviation. Reference it in every affected production record.

Overdue closures

Deviations open for months with product decisions pending. Set targets, track ageing and approve extensions with a reason.

No trending

Each deviation closed on its own, so patterns are missed. Trend by process, product, equipment, supplier and cause, and review it in management review.

Informal supplier deviations

A supplier emails "slightly out of spec, OK to ship?" and someone replies yes. Route every supplier request through your deviation or concession process, and request supplier corrective action when it repeats.

Product released before the record is closed

Affected product shipped while the impact assessment is still open. Keep it on hold until disposition is approved, or document a justified, approved early release.

What's at stake

Inspectors and auditors routinely review deviation records, because they show how a company behaves when things don't go to plan. Weak handling has real consequences:

  • FDA inspection observations. At the end of an inspection, FDA issues a Form 483 listing conditions that may violate the law. It isn't a final agency determination, and FDA encourages companies to respond in writing with a corrective action plan and to carry it out promptly.[15]
  • Warning letters. FDA issues a warning letter when it finds what it considers significant violations, and if violations are still found later, it may take further action without further notice.[16] Under the QMSR, failing an applicable requirement renders a device adulterated.[3]
  • Notified body findings and certificate action. EU notified bodies audit at least every 12 months and make unannounced audits at least once every five years. Where samples diverge from the technical documentation or approved design, the notified body must suspend or withdraw the certificate or restrict it.[8]
  • Field actions. Product released outside its approved state may need correction or removal, with reporting to FDA and vigilance reporting in the EU.[14][8][9]
  • Patients and users. Behind every one of these is the real reason for the rules: product that doesn't perform as intended can harm the people relying on it.

Common questions

Can we approve a planned deviation after work has started?

No. Once product has been made under the departure, it's an unplanned deviation. Record it as one, assess the product, and look at why approval came late.

Is a planned deviation the same as a concession?

No. A planned deviation (ISO 9000's "deviation permit") is approved before product is made. A concession is a decision to use or release product that already exists and doesn't conform.[5] ISO 13485 sets conditions for concessions in clause 8.3.2.[2]

How long can a planned deviation last?

As long as your procedure and the approved limits allow, and no longer. There's no regulatory maximum, which is why the limits on the record matter. If it needs to continue, make a permanent change.

Do we need a deviation if the product still meets specification?

Usually yes, if an approved procedure or process wasn't followed. The production record should reflect how the product was actually made, and the deviation shows someone assessed it.[2] It may well be minor.

Do deviations have to be reported to FDA or a notified body?

Not as such. Reporting comes from other rules: corrections and removals, adverse event and vigilance reporting, and notifying changes that need regulatory review. A deviation that leads to any of those triggers that reporting.[14][8]

A supplier wants to ship material slightly out of spec. Whose deviation is it?

Yours. Assess and approve it under your own process before shipment, or handle it as a concession on receipt. Purchasing controls and nonconforming product rules apply, including notifying the responsible external party.[2]

References

  1. 21 CFR 211.100, written procedures; deviations (drug current good manufacturing practice), paragraph (b). www.law.cornell.edu/cfr/text/21/211.100
  2. ISO 13485:2016, Medical devices — Quality management systems — Requirements for regulatory purposes, clauses 4.1.4, 4.2.4, 4.2.5, 6.4.1, 7.1, 7.3.9, 7.4, 7.5.1, 7.5.6, 7.5.8, 7.5.9, 7.6, 8.2.5, 8.2.6, 8.3, 8.4, 8.5.2 and 8.5.3. Last reviewed and confirmed by ISO in 2025. www.iso.org/standard/59752.html
  3. 21 CFR Part 820, Quality Management System Regulation (QMSR), §§ 820.3 (definitions), 820.7 (incorporation by reference of ISO 9000:2015 clause 3 and ISO 13485:2016) and 820.10, including (b)(4) advisory notices and (e) adulteration; final rule 2 February 2024, effective 2 February 2026. www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-820/subpart-A/section-820.10
  4. U.S. FDA, Quality Management System Regulation (QMSR) (overview page). www.fda.gov/quality-systems-regulation
  5. ISO 9000:2015, Quality management systems — Fundamentals and vocabulary, clause 3.12 (terms related to action: concession, deviation permit). This is the edition incorporated by reference in 21 CFR 820.7(a); ISO published a fifth edition, ISO 9000:2026, in May 2026. www.iso.org/standard/9000
  6. ISO 14155:2026, Clinical investigation of medical devices for human subjects — Good clinical practice, fourth edition, March 2026 (replaces ISO 14155:2020). www.iso.org/standard/83968.html
  7. 21 CFR 812.150(a)(4), investigator reports: deviations from the investigational plan (with § 812.35(a) for changes that also need FDA and IRB approval). www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-812/subpart-G/section-812.150
  8. Regulation (EU) 2017/745 on medical devices (EU MDR), as amended: Article 10(9) (series production conformity and quality management system), Articles 87 and 89 (serious incidents and field safety corrective actions), and Annex IX, Sections 2.2 (quality management system documentation), 3.3, 3.4 and 3.7 (surveillance audits and certificate action). eur-lex.europa.eu/eli/reg/2017/745/oj/eng
  9. Regulation (EU) 2017/746 on in vitro diagnostic medical devices (EU IVDR), as amended: Article 10(8) (quality management system), Articles 82 and 84 (serious incidents and field safety corrective actions), and Annex IX, Section 2.2. eur-lex.europa.eu/eli/reg/2017/746/oj
  10. Health Canada, Notice: Medical Device Single Audit Program (MDSAP) Transition Plan — Frequently Asked Questions. www.canada.ca/en/health-canada/services/drugs-health-products/medical-devices/activities/international/notice-transition-plan-medical-device-audit-program.html
  11. 21 CFR 4.4, current good manufacturing practice requirements for combination products (as amended 2 February 2024 and 18 June 2024). www.ecfr.gov/current/title-21/chapter-I/subchapter-A/part-4
  12. European Commission, Proposal for a regulation to simplify rules on medical and in vitro diagnostic devices, COM(2025) 1023, 16 December 2025 (proposal, not yet adopted). health.ec.europa.eu/publications/proposal-regulation-simplify-rules-medical-and-vitro-diagnostic-devices_en
  13. ISO 14971:2019, Medical devices — Application of risk management to medical devices, including clause 10 (production and post-production activities). Last reviewed and confirmed by ISO in 2025. www.iso.org/standard/72704.html
  14. 21 CFR Part 806, Medical Devices; Reports of Corrections and Removals, §§ 806.10 (reports, within 10 working days) and 806.20 (records of corrections and removals not required to be reported). www.ecfr.gov/current/title-21/chapter-I/subchapter-H/part-806/subpart-B
  15. U.S. FDA, FDA Form 483 Frequently Asked Questions. www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/inspection-references/fda-form-483-frequently-asked-questions
  16. U.S. FDA, About Warning and Close-Out Letters. www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/about-warning-and-close-out-letters

Regulations and guidance were checked against primary sources at the time of writing. ISO clause content is paraphrased; read the standards for exact wording. Record names such as "planned deviation" and the minor, major and critical grades are common industry usage, not regulatory definitions.

Next
Next

Change Request, Change Order, ECO or Deviation: Which One Do You Need?