bg-left bg-right

Managing Design Changes Across the Drug and Device Lifecycle

background
user-icon 21 Oct 2026

A change that appears minor in a medical device can have consequences for the safety, performance or quality of the complete drug-device combination product. Replacing a syringe stopper, changing a supplier, updating delivery-device software or modifying the instructions for use may affect more than one component. It may also affect drug compatibility, dose delivery, usability, stability or the regulatory status of the product.

For this reason, design change management must consider the complete combination product, not just the component being changed. A change that is acceptable from an engineering perspective may still require additional testing, risk assessment or regulatory evaluation before implementation.

For manufacturers, the challenge is to establish a controlled process that identifies the impact of a change across development, manufacturing and post-market activities.

What Is Design Change Management?

Design change management is the controlled process of evaluating, documenting, reviewing, verifying or validating, and approving changes to a product design before implementation, as applicable.

The traditional FDA Quality System Regulation addressed design changes under 21 CFR 820.30(i). Since the Quality Management System Regulation (QMSR) became effective on February 2, 2026, FDA-regulated device manufacturers must consider the applicable design and development change requirements under ISO 13485:2016, including Clause 7.3.9. The change-control process should maintain evidence that changes have been evaluated and approved appropriately.

For combination products, the process must also consider the applicable drug quality requirements and regulatory pathway. In the EU, certain changes to a device’s design or intended purpose can have specific significance under the MDR, including transitional provisions for devices covered by older certificates. Not every operational or manufacturing change is automatically a significant design change; the applicable criteria must be assessed.

How to Manage Design Changes in Practice

1. Identify and Document the Proposed Change

Every change should begin with a controlled request that explains what is changing and why.

The record should identify the affected component, current and proposed design, reason for the change, originator, proposed implementation date and relevant product versions.

Changes may originate from supplier discontinuation, manufacturing problems, customer feedback, complaints, risk assessments, new regulatory requirements or opportunities to improve product performance.

For example, if a supplier proposes a new polymer for a prefilled syringe component, the request should identify the material change and the affected product configurations. It should not be treated as a routine purchasing update until its potential effect on the drug-device combination has been assessed.

Practical check: Is the change clearly described, and can the organization identify every product, component and document potentially affected?

2. Assess the Impact on the Complete Product

A combination product requires an impact assessment that considers both the device and the medicinal product.

The review should consider, as applicable:

  • Device functionality and dose-delivery performance.
  • Drug-device material compatibility, including extractables and leachables where relevant.
  • Drug stability, shelf life and storage conditions.
  • Biocompatibility and sterility assurance.
  • Packaging integrity and transportation conditions.
  • Labeling, instructions for use and human factors.
  • Manufacturing processes, suppliers and inspection controls.

Consider a change to the lubricant used in a syringe. Although the change may be intended to reduce injection force, it could also affect material compatibility, functionality or drug-contact risks. The organization should identify which assessments are needed rather than assuming that successful mechanical testing is sufficient.

3. Reassess Risk and Define the Required Evidence

Changes can introduce new hazards or alter previously evaluated risks. Risk management should therefore be updated as necessary before the change is approved.

The assessment should identify affected hazards, existing risk controls, potential new failure modes and whether additional verification or validation is needed.

For example, a software update to an autoinjector may alter the timing of an alarm or the sequence of delivery steps. The review should consider whether the change affects dose delivery, user interaction, essential performance or existing risk controls.

The evidence required will depend on the nature and extent of the change. Some changes may need document review and focused testing; others may require broader performance testing, usability validation, stability studies or clinical and regulatory assessment.

Practical check: Has the organization justified why the proposed evidence is sufficient for the risks introduced by the change?

4. Determine Regulatory and Submission Implications

A technically acceptable change is not automatically acceptable from a regulatory perspective. Before implementation, the manufacturer should assess whether the change affects the applicable marketing authorization, device conformity assessment, certification or premarket submission.

In the United States, the assessment depends on the product’s regulatory pathway. For example, certain changes to a device cleared through a 510(k) may require a new premarket notification if they could significantly affect safety or effectiveness. Changes to a device approved through a PMA may require a supplement, depending on the change and applicable requirements.

For combination products, the drug-related regulatory impact must also be considered. A device modification may affect information in the medicinal product dossier, including device description, performance, compatibility or labeling.

In the EU, manufacturers should assess applicable MDR requirements and, where relevant, whether a change affects the device conformity assessment or the medicinal product marketing authorization. The significance of the change depends on the product and the applicable regulatory provisions; it should not be determined solely by the change’s internal classification.

Practical check: Has Regulatory Affairs documented whether notification, approval, consultation or additional submission evidence is required before implementation?

5. Verify, Validate and Approve the Change

Once the impact assessment is complete, the organization should define the activities needed to demonstrate that the modified design remains suitable.

Verification determines whether the changed design continues to meet its specified requirements. Validation, where needed, determines whether the modified product meets user needs and intended use.

For example, changing an autoinjector’s needle shield may require dimensional and functional testing, assessment of activation forces, and review of user interaction. Depending on the impact, the manufacturer may also need to evaluate whether existing usability validation remains representative.

The change record should include approved test protocols, acceptance criteria, results, deviations, conclusions and required approvals. Testing should use a clearly identified design revision, and unresolved issues should be addressed before release.

A common mistake is to approve a change based on a successful test alone. The test result must be evaluated against the change’s intended purpose, the relevant risks and the complete set of affected requirements.

6. Control Suppliers, Manufacturing and Design Transfer

Changes frequently affect more than the design specification. A new supplier, manufacturing location, assembly process or sterilization method may affect product consistency and the evidence supporting the approved design.

The manufacturer should evaluate whether supplier qualification, incoming inspection, process validation, sterilization validation, packaging assessment or other manufacturing controls need to be updated.

Consider a supplier change for a component used in a drug delivery device. Even when the component’s nominal dimensions remain unchanged, differences in material formulation or manufacturing conditions may affect performance or compatibility. The organization should determine what evidence is needed before the new source is released for production.

The approved change should be reflected in the relevant drawings, specifications, work instructions, inspection criteria and supplier records. Obsolete documents must be controlled to prevent unintended use.

7. Update Lifecycle Records and Monitor the Outcome

Design change management does not end when a change is approved. The organization should ensure that the change is implemented as authorized and that relevant records remain consistent.

These may include the design and development file, risk-management file, technical documentation, regulatory submissions, manufacturing records and instructions for use. Under FDA’s QMSR, the design and development file should contain or reference the applicable records demonstrating conformity with design and development requirements.

After implementation, relevant complaints, deviations, process data and product performance should be reviewed to determine whether the change achieved its objective without introducing unexpected problems.

For example, if a revised component was introduced to reduce delivery force, post-implementation data may help establish whether the improvement is sustained and whether any new complaints or failure patterns have emerged.

Practical check: Can the organization trace the approved change from the original request through testing, implementation and any required follow-up?

Conclusion & How TS Quality & Engineering Can Help

Effective design change management protects the integrity of a combination product throughout its lifecycle. It ensures that changes are evaluated not only for their immediate technical benefit, but also for their effects on risk, drug-device compatibility, manufacturing, regulatory obligations and patient safety.

The key is to establish a documented process that connects the change request with its impact assessment, risk evaluation, testing, approvals and implementation. This approach helps prevent uncontrolled modifications and makes regulatory reviews more straightforward.

TS Quality & Engineering (TSQE) supports medical-device and combination-product organizations with design controls, risk management, technical documentation and quality-system implementation. We can help assess existing change-control processes, identify documentation gaps and establish practical procedures for managing changes across the product lifecycle.

Related reading

References

  1. U.S. Food and Drug Administration (FDA). Quality Management System Regulation (QMSR). Official FDA overview of the regulation effective February 2, 2026, including incorporation of ISO 13485:2016. FDA QMSR.
  2. U.S. Food and Drug Administration (FDA). QMSR: Risk and Design and Development. FDA presentation covering design and development under the updated framework. FDA presentation (PDF).
  3. International Organization for Standardization (ISO). ISO 13485:2016 — Medical devices — Quality management systems — Requirements for regulatory purposes. Refer particularly to Clause 7.3.9, Control of design and development changes. ISO standard page.
  4. Medical Device Coordination Group (MDCG). MDCG 2020-3 Rev.1: Guidance on significant changes regarding the transitional provision under Article 120 of the MDR. Guidance for assessing changes to the design or intended purpose of certain legacy devices. European Commission guidance (PDF).
  5. European Commission. MDCG endorsed documents and other guidance. Official directory of guidance supporting the implementation of the EU MDR and IVDR. European Commission guidance directory.
  6. Team-NB. Team-NB Documents. Industry association publications and position papers that may provide supplementary interpretation of notified-body practices. Select the specific document relevant to the device and change being assessed. Team-NB document library.

About the author:
Gianluca Tordi

Tags

MDR Guidelines

Worldwide regulation resources

Latest News

Contact us / Ask a quote now

We will help You find the right solution for Your Projects

CONTACT US

SOME OF OUR CLIENTS