For medical device manufacturers, process validation is often associated with the manufacturing floor. That’s not wrong, but successful medical device process validation starts much earlier, well before a manufacturing team begins executing validation activities.
It begins with the requirements, risks, specifications, and design decisions established during product development, as well as how effectively that information makes its way into manufacturing.
Design transfer, while sometimes mistakenly thought of as a regulatory milestone or documentation exercise, is a critical connection point between R&D and manufacturing.
When traceability stops at that handoff, manufacturing teams can be left reconstructing relationships among design outputs, process requirements, specifications, equipment, risks, and validation activities. That can mean lost context, missing traceability, and risks that are harder to identify before production begins.
The more effective approach is to extend traceability beyond R&D and into manufacturing, creating continuity from concept to development, through manufacturing, all the way to the field.
The Problem With Treating Process Validation as a Manufacturing-Only Activity
Process validation is about confidence in a manufacturing process and its ability to consistently achieve its intended result.
Under the FDA’s Quality Management System Regulation (QMSR), which became effective February 2, 2026, medical device manufacturers are subject to ISO 13485:2016 requirements incorporated by reference into 21 CFR Part 820.
The FDA’s current inspection framework also takes a broader lifecycle view. Its 2026 medical device manufacturing compliance program encompasses a total product life cycle (TPLC) assessment, with manufacturers responsible for controlling devices from design and development through postmarket surveillance.
The FDA describes design and development and manufacturing as two connected phases:
- Establishing the device’s inherent safety and effectiveness.
- Ensuring the manufacturing process can consistently reproduce that design without degrading its quality.
The FDA’s current medical device inspection program identifies “Validation of Processes for Production and Service Provision” as a key element of the Production and Service Provision QMS area, corresponding to ISO 13485 Clause 7.5.6. The FDA also notes that processes must be validated and revalidated after changes, as appropriate.
The FDA has emphasized that manufacturers still need to consider factors including the device, manufacturing processes, and the risks and complexity associated with those processes when documenting their quality management systems.
Taken together, this lifecycle perspective shows how closely R&D and manufacturing are connected. The information that supports successful process validation begins taking shape long before validation activities are underway.
- Product requirements influence design specifications.
- Design decisions influence how a product will be manufactured and tested.
- Risks identified during development can affect manufacturing controls.
- Design outputs become inputs to production specifications and processes.
By the time a device reaches manufacturing, much of the context needed to make good process-validation decisions has already been created.
The question is whether that context travels with the design, and whether it makes it “over the wall.”
Design Transfer Shouldn’t Be an “Over-the-Wall” Handoff
The R&D and manufacturing worlds meet at design transfer, a critical point where requirements, specifications, design outputs, and other product information established during R&D begin to inform manufacturing, inspection, and testing. When this context does not carry forward clearly, problems that emerge in manufacturing can have significant downstream consequences.
A 2023 study of 189 FDA Class I recalls involving moderate- and high-risk medical devices found that manufacturing and processing errors accounted for nearly one-quarter of the recalls studied. The median recall affected 4,620 device units.
Those stakes make continuity between R&D and manufacturing especially important. Manufacturing inherits the decisions, requirements, and specifications established during R&D, along with the context behind them.
Operations teams must translate the design into something that can actually be produced consistently, which can involve:
- Manufacturing specifications and tolerances.
- Incoming inspection specifications.
- In-process testing.
- Final testing.
- Work instructions.
- Bills of materials.
- Manufacturing and test equipment.
- Process requirements.
- Process-related risks.
- Process validation activities.
R&D and manufacturing exist on a continuum, with design transfer connecting design inputs and outputs to the manufacturing and operations environment. Yet in practice, design transfer can still resemble throwing information “over the wall” from one organization to another.
Manufacturing teams inherit the design, but they may have to piece together the rationale and relationships behind it retrospectively.
When that information is distributed across numerous documents, systems, and teams, even basic questions can require significant manual effort. Teams may need to manually connect design inputs and outputs with supplier specifications, incoming inspection specifications, in-process testing, final testing, and production-unit test results.
At this point, the wall between R&D and manufacturing becomes a traceability problem.
Traceability Shouldn’t Stop at Design Transfer
Medical device teams are accustomed to thinking about traceability within product development. During R&D, teams may establish relationships among user needs, design inputs, system and subsystem requirements, risks, design outputs, and verification and validation evidence.
These relationships shouldn’t end when the product enters manufacturing. The product definition and context established during R&D should provide the foundation for the manufacturing requirements, specifications, processes, equipment, and controls needed to consistently produce the device.
For example, a design output established during development may drive a manufacturing process requirement. That process requirement can inform a process specification, which may determine the equipment needed to execute the process and the validation activities needed to demonstrate that the process performs consistently.
In this way, traceability established during R&D can continue downstream into manufacturing:
User need → design input → system/subsystem requirement → design output → process requirement → process specification → manufacturing equipment → validation activity → validation evidence
The exact relationships will depend on the device and manufacturing process, but the principle remains the same: manufacturing information should remain connected to the product-development information that drove it.
This approach extends traceability established during R&D into manufacturing. Jama Software®’s Process Validation framework is designed to support that continuity and, for equipment validation, connect process equipment, process requirements, and process validation activities.
The result is a more continuous thread of information rather than a one-time transfer of documentation that becomes difficult at scale.
The information continues to have downstream implications as manufacturing determines how the product will be built, inspected, tested, and controlled.
Just as importantly, those relationships can work in the other direction. Manufacturing constraints, process changes, or newly identified risks may require teams to reassess upstream requirements, specifications, or design decisions. Maintaining those connections across the lifecycle gives teams the context to understand those impacts in either direction.
Change Is Where Continuous Traceability Becomes Especially Valuable
A static design transfer might seem sufficient at the moment of handoff. The challenge comes when something changes.
Consider a component that becomes obsolete after production has begun. The first thought might be to replace it. But that quickly leads to other questions:
- Which design requirements are affected?
- Does the change introduce or alter a risk?
- Which supplier or manufacturing specifications need to change?
- Does incoming inspection need to change?
- Is manufacturing or test equipment affected?
- Which verification or validation activities are affected?
- Does the manufacturing process need to be revalidated?
The same problem can occur in the opposite direction, such as a newly identified hazard in the field revealing something that needs to be reassessed upstream in the design.
Changes that cross the R&D-to-manufacturing boundary require teams to understand their impact in both directions. Connected information matters for scenarios like engineering changes, part obsolescence, downstream manufacturing impact, process revalidation, and newly discovered hazards.
The FDA’s current medical device inspection program reinforces the importance of evaluating change. Its Change Control QMS area is intended to ensure that changes are evaluated for risk and impact on products and processes before implementation, including product and process changes associated with process-validation requirements.
With document-based traceability, assessing the full impact of a change can require opening multiple files, locating current versions, consulting different teams, and manually reconstructing dependencies.
With live, relationship-based traceability, teams can instead examine the upstream and downstream relationships surrounding the changed item and perform impact analysis with greater context. Traceability can help them understand what a change means before acting on it.
Bringing Manufacturing Into the Conversation Earlier
Continuous traceability can also help manufacturing teams engage earlier in the product development process.
Manufacturing and operations teams are responsible for turning a product design into production specifications and putting the processes, systems, equipment, suppliers, facilities, controls, and people in place to produce it successfully. That includes production and process scale-up, supplier and contract-manufacturer controls, production records, and ensuring that production-related processes and systems are appropriately validated.
Some of those activities require significant lead time. Facility changes, equipment procurement, supplier planning, environmental requirements, regulatory considerations, and other operational dependencies can’t always wait until design transfer to begin.
Waiting until design transfer to expose manufacturing teams to critical product information can therefore create unnecessary pressure and introduce risks that could have been addressed earlier.
Bringing manufacturing into the conversation earlier gives these teams visibility into what they will eventually be asked to manufacture and validate, while giving R&D teams earlier insight into manufacturing constraints.
Manufacturing Constraints Can Influence Design Decisions
That exchange can influence the design itself.
For example, consider a metal chassis for an instrument. A design team may specify dimensions and tolerances before determining how the chassis will be manufactured. Sand molding and machining can impose different constraints on achievable tolerances, production scale, and cost.
Manufacturing input may reveal that the proposed design would be difficult or costly to produce using the preferred process, which could lead the development team to reconsider a tolerance or other design requirement.
The tradeoff can also go in the other direction. If a particular tolerance is critical to the device’s intended performance, changing the design may not be appropriate. The organization may instead decide that a more expensive manufacturing process is necessary to satisfy the requirement. Neither decision should first surface during design transfer.
Early cross-functional discussion gives engineering and manufacturing teams time to evaluate these tradeoffs while there are still options available.
Manufacturing stakeholders can review relevant requirements and specifications, identify manufacturability concerns, contribute process expertise, and flag requirements that may be difficult to achieve consistently at production scale.
R&D teams can then weigh manufacturing constraints against product requirements, risks, performance, cost, and other program considerations before the design becomes harder to change.
That can make design transfer less of a handoff and more of a continuation of cross-functional development.
Earlier visibility also gives manufacturing teams more time to plan long-lead activities and identify potential process and validation challenges before they become late-stage problems.
Extending the Digital Thread Into Manufacturing
Extending traceability into manufacturing doesn’t require every manufacturing artifact to live in the same system. Medical device organizations rely on specialized tools across development, quality, product lifecycle management, and manufacturing. The goal is to preserve the relationships and context that matter as information moves between them.
Jama Connect® centers on Live Traceability across the development process and best-of-breed tools. Within medical device development, teams can trace user needs, design inputs, requirements, design documentation, risks, failure modes, and verification and validation testing while analyzing the impact of changes. Those relationships provide the foundation for continued traceability as the product moves into manufacturing.
Jama Software’s Process Validation framework extends that connected approach into manufacturing. Its initial equipment-validation use case establishes relationships among process requirements, specifications, equipment, and validation activities while supporting change and risk management through Live Traceability.
The result is a more continuous digital thread:
Requirements → design → design verification → design transfer → manufacturing requirements and specifications → equipment and processes → process validation → ongoing change
Where Does Computer Software Assurance Fit?
For manufacturing environments that rely on software and automated systems, Computer Software Assurance (CSA) adds another dimension to this risk-based approach.
The FDA’s February 2026 CSA guidance applies to computers and automated data-processing systems used as part of medical device production or the quality management system.
The FDA describes CSA as a risk-based approach to establishing confidence in that automation, including determining where additional rigor is appropriate and selecting suitable testing activities and objective evidence.
CSA reinforces a principle that also matters for process validation: teams should apply rigor according to risk and maintain appropriate evidence around systems that affect production and quality.
For organizations modernizing manufacturing processes and the systems that support them, CSA is therefore worth considering as part of the broader process-validation and quality-management strategy.
A More Connected Approach to Medical Device Process Validation
Successful medical device process validation is built on decisions made throughout the product lifecycle. Changes at any point can ripple upstream or downstream.
When traceability stops at design transfer, those relationships become harder to see. Extending traceability through design transfer and into manufacturing can instead help teams:
- Preserve the context behind manufacturing requirements and specifications.
- Connect process requirements with equipment and validation activities.
- Understand upstream and downstream change impact.
- Identify potential validation implications when something changes.
- Improve collaboration between R&D, quality, and manufacturing.
- Maintain a more continuous record across the medical device lifecycle.
Jama Connect for MedTech already supports Live Traceability across user needs, requirements, design information, risks, and verification and validation, along with change-impact analysis, audit trails, baselines, and export of information when documentation needs to reside in a QMS.
Extending that connected approach into manufacturing helps break down the wall created by traditional design transfer, so the traceability established during R&D can continue delivering value as the product moves into production.
The decisions and information established throughout product development lay the foundation for what manufacturing must ultimately produce, control, and validate.
Maintaining traceability across that lifecycle helps ensure that context travels with the product from R&D into manufacturing and continues through production.
Get Started With Jama Connect Today
See how Jama Connect’s Process Validation framework extends Live Traceability beyond product development and into manufacturing. Explore Jama Connect or request a demo today.
