Equivalence Contracts: The Clause That Makes or Breaks Your Claim
I reviewed an equivalence claim last month where the contract looked perfect on the surface. Three pages of terms. Signatures from both parties. Legal review completed. The Notified Body rejected it in the first assessment. The reason was not what the manufacturer expected. The contract failed to address one critical MDR requirement that most legal teams overlook entirely.
In This Article
Equivalence claims under MDR have forced manufacturers to formalize relationships that used to happen with a handshake and a phone call. The regulation does not just require access to data. It requires a specific contractual framework that protects the validity of the claim throughout the device lifecycle.
Most contracts I see fail because they were written by legal departments who understand commercial law but not clinical evaluation requirements. They focus on liability, confidentiality, and payment terms. They miss the technical obligations that make equivalence defensible during审核.
The gap becomes visible when the Notified Body starts asking questions. When they request post-market data updates. When they challenge whether you still have access to information that demonstrates ongoing equivalence. At that point, the contract either supports your claim or it does not. There is no middle ground.
What MDR Article 61(5) Actually Requires
MDR Article 61(5) sets the foundation. If you base your clinical evaluation on equivalence, you must have a contract with the manufacturer of the equivalent device. That contract must allow full access to technical documentation.
The phrase “full access” is where manufacturers stumble. It is not a one-time data package. It is ongoing access to information that evolves as the equivalent device moves through its lifecycle. This includes design changes, post-market surveillance data, complaints, field safety corrective actions, and clinical evidence updates.
MDCG 2020-5 expands on this requirement. It specifies that the agreement must allow verification of equivalence throughout the lifetime of your device. That means the contract cannot expire. It cannot have termination clauses that cut off access while your device remains on the market. It cannot restrict access to historical data only.
Contracts with fixed terms (e.g., 3 years) that do not account for the device lifecycle. When the contract expires, the equivalence claim becomes unsupportable, but the device is still on the market. The manufacturer only discovers this when preparing for recertification.
The other critical element is verification rights. The contract must allow you to verify that the data you receive is accurate and complete. This means audit rights. This means the ability to review source documents if questions arise. This means the right to request updates when you become aware of changes to the equivalent device.
What Notified Bodies Look For
Notified Bodies assess contracts during initial review and surveillance. They are looking for three things: scope, duration, and enforceability.
Scope means the contract clearly defines what information you can access. Vague language like “relevant technical data” does not work. The contract should list specific document types: design history files, risk management reports, biocompatibility data, clinical evaluation reports, PSUR data, complaint trending, and vigilance reports.
If the equivalent device is already on the market, the contract must address historical data. How far back can you access records? Can you request data from specific time periods if you need to investigate a particular issue? These questions come up during equivalence demonstrations when reviewers challenge the comparability of materials or design features.
The most robust contracts include an appendix that lists required documents by category. This creates a clear obligation and makes it easier to demonstrate compliance during audits. It also prevents disputes about what “full access” means when you request specific information.
Duration is where many contracts fail structurally. A contract that expires while your device is on the market creates a compliance gap. The Notified Body will ask how you maintain equivalence after the contract ends. If you cannot answer, the equivalence claim collapses.
Some manufacturers address this with automatic renewal clauses. Others tie the contract duration to device lifecycle milestones: “This agreement remains in effect until Device X is withdrawn from all markets.” Both approaches work if implemented correctly. What does not work is hoping the relationship continues informally after the contract lapses.
Enforceability is the silent killer. A contract that looks complete but cannot be enforced is worthless. This happens when the contract is signed by the wrong entity, when obligations are vaguely defined, or when there are no consequences for non-compliance.
Notified Bodies sometimes ask: “What happens if the equivalent manufacturer stops providing updates?” If your answer is “we trust them,” the claim is at risk. The contract should include remedies, escalation procedures, and clear obligations tied to regulatory requirements.
The Information Access Problem
Even when the contract structure is correct, information access creates practical problems. The equivalent manufacturer has competing interests. They want to maintain confidentiality. They want to protect competitive information. They may be uncomfortable sharing post-market data that reveals problems.
The contract must balance these concerns with your regulatory obligations. This is where specific language matters. The contract should clarify what information you need, how it will be shared, what confidentiality protections apply, and what happens if there is a dispute about disclosure.
I see contracts that require the equivalent manufacturer to provide updates “upon request.” This creates ambiguity. How often can you request updates? What response time is required? What happens if they delay or refuse?
Better contracts establish a cadence. The equivalent manufacturer provides PSUR data annually. They notify you within 30 days of any design changes, field safety corrective actions, or significant complaint trends. You have the right to request additional information with reasonable justification. These obligations are mutual and enforceable.
Contracts that require “reasonable” access or “timely” updates without defining what these terms mean. During surveillance, when the Notified Body asks for evidence of ongoing equivalence, delays in receiving data become compliance issues. Vague terms make it impossible to hold the equivalent manufacturer accountable.
Confidentiality clauses can also restrict your ability to use data appropriately. The contract should allow you to share information with your Notified Body, with competent authorities, and with your internal clinical and regulatory teams. If the confidentiality terms prevent this, you cannot fulfill MDR obligations.
Who Should Be Party to the Contract
Contract parties matter more than manufacturers realize. The agreement must be with the legal manufacturer of the equivalent device, not a distributor, not a sales representative, not a subsidiary without authority.
If the equivalent device has changed ownership, the contract must be updated. If the original manufacturer sold the product line to another company, your old contract may no longer be valid. This happens more often than expected, especially with legacy devices.
The Notified Body will verify that the entity providing data has legal authority to do so. If there is any ambiguity about who manufactures the equivalent device, the contract must address it explicitly. This includes cases where manufacturing is outsourced or where intellectual property is licensed.
For devices with multiple manufacturers across regions, the contract should clarify which entity is responsible for providing data. If the equivalent device is manufactured in the US but distributed in Europe by a different company, who owns the obligation to share post-market surveillance data? The contract must answer this.
Post-Market Obligations
The contract does not end at market access. It must support your ongoing clinical evaluation activities, your PMCF plan, and your periodic safety update reports.
This means the equivalent manufacturer must provide data that allows you to monitor safety and performance over time. If a safety issue emerges with the equivalent device, you need to know about it immediately. If clinical data is published that affects the risk-benefit profile, you need access to it.
Some contracts include specific triggers. If the equivalent manufacturer initiates a field safety corrective action, they must notify you within a defined timeframe. If complaint rates exceed a threshold, they must share trending data. If new clinical evidence becomes available, they must provide summaries or full reports depending on relevance.
These obligations align with MDR Article 61(11), which requires ongoing demonstration of equivalence throughout the lifecycle. The contract is the mechanism that makes this possible. Without clear post-market obligations, the equivalence claim weakens over time.
The strongest contracts treat post-market data sharing as a proactive obligation, not a reactive request. Instead of requiring you to ask for updates, the equivalent manufacturer is obligated to push relevant information to you on a defined schedule. This reduces delays and demonstrates due diligence during audits.
What Happens When the Equivalent Device Changes
Design changes to the equivalent device create immediate implications for your equivalence claim. The contract must address how changes are communicated and how you assess their impact on equivalence.
Not every change breaks equivalence, but every change must be evaluated. A material change might invalidate your claim entirely. A minor manufacturing process adjustment might be irrelevant. You cannot make that judgment without information.
The contract should require notification of all changes that could affect safety, performance, or the characteristics on which equivalence is based. This includes changes to materials, manufacturing processes, sterilization methods, software algorithms, labeling, and intended use.
It should also define your rights after a change is communicated. Can you request supporting documentation? Can you audit the change control process? Can you terminate the agreement if a change fundamentally alters the device in a way that breaks equivalence?
I have seen equivalence claims collapse because the equivalent manufacturer made a material change without notification. The change was eventually discovered during surveillance or through published literature. At that point, the manufacturer had to scramble to rebuild the clinical evaluation, often under time pressure with the Notified Body watching.
The contract is your early warning system. If it does not obligate the equivalent manufacturer to disclose changes, you are exposed.
Termination and Exit Provisions
Contracts need exit provisions, but those provisions cannot leave you without a valid clinical evaluation. If the contract terminates for any reason, what happens to your device?
Some contracts include transition periods. If either party terminates the agreement, there is a 12-month window during which data access continues. This gives you time to develop alternative evidence, identify a new equivalent device, or conduct clinical investigations if necessary.
Other contracts prevent termination entirely unless both parties agree or unless your device is withdrawn from the market. This approach provides stability but requires careful drafting to avoid creating obligations that cannot be enforced long-term.
What does not work is a termination clause that allows either party to exit with 30 days notice. This leaves you with a device on the market and no supporting clinical evidence. The Notified Body will suspend or withdraw your certificate. The commercial and regulatory consequences are immediate.
Exit clauses that prioritize commercial flexibility over regulatory obligations. Manufacturers negotiate termination rights without considering the clinical evaluation impact. The result is a contract that protects business interests but creates compliance risks that outweigh any commercial benefit.
Documentation and Audit Trail
The contract itself is not enough. You must maintain evidence that the contract is being executed. This means documenting every data request, every update received, every review of equivalence-related information.
Notified Bodies ask for this during surveillance. They want to see that you are actively using the contract to maintain equivalence. If you signed an agreement three years ago and have never requested an update, they will question whether equivalence is still valid.
The audit trail should show regular engagement. Annual requests for PSUR data. Reviews of complaint trends. Evaluations of any design changes. Correspondence about new clinical evidence. This demonstrates that equivalence is not a one-time finding but an ongoing process.
It also protects you if the relationship deteriorates. If the equivalent manufacturer stops responding to requests, if they refuse to share data, if they terminate the contract improperly, you have documentation that supports your position with the Notified Body and with legal counsel if necessary.
Why Legal Review Is Not Enough
Legal teams draft contracts to minimize liability and protect commercial interests. This is appropriate, but it is not sufficient for equivalence agreements. The contract must also satisfy technical and regulatory requirements that legal professionals may not fully understand.
Clinical affairs and regulatory affairs must be involved in contract development. They understand what information is needed for clinical evaluation. They know what Notified Bodies will ask. They can identify gaps that create compliance risks.
The best process involves collaboration. Legal drafts the framework. Clinical and regulatory teams define the technical requirements. Quality assurance reviews for alignment with procedures and standards. The contract is reviewed against MDCG 2020-5 before finalization.
This cross-functional approach prevents the situation where a contract is legally sound but regulatorily inadequate. It ensures that commercial negotiations do not compromise clinical evaluation requirements. It creates a document that serves both business and compliance needs.
The equivalence contract is not a formality. It is not a box to check during submission preparation. It is the foundation of your clinical evaluation strategy. When it is structured correctly, it protects your device throughout its lifecycle. When it is inadequate, it creates risks that surface at the worst possible time, usually when the Notified Body is reviewing your file or when you need data urgently to respond to a safety concern.
The manufacturers who get this right involve the right people early, define obligations clearly, and treat the contract as a living document that evolves with the device. The ones who struggle treat it as a legal transaction disconnected from regulatory reality. The difference shows up in every interaction with the Notified Body.
Frequently Asked Questions
What is a Clinical Evaluation Report (CER)?
A CER is a mandatory document under MDR 2017/745 that demonstrates the safety and performance of a medical device through systematic analysis of clinical data. It must be updated throughout the device lifecycle based on PMCF findings.
How often should the CER be updated?
The CER should be updated whenever significant new clinical data becomes available, after PMCF activities, when there are changes to the device or intended purpose, and at minimum during annual reviews as part of post-market surveillance.
What causes CER rejection by Notified Bodies?
Common reasons include inadequate equivalence demonstration, insufficient clinical data for claims, poorly structured SOTA analysis, missing gap analysis, and lack of clear benefit-risk determination. Structure and logical flow are as important as the data itself.
Which MDCG guidance documents are most relevant for clinical evaluation?
Key documents include MDCG 2020-5 (Equivalence), MDCG 2020-6 (Sufficient Clinical Evidence), MDCG 2020-13 (CEAR Template), MDCG 2020-7 (PMCF Plan), and MDCG 2020-8 (PMCF Evaluation Report).
Need Expert Help with Your Clinical Evaluation?
Get personalized guidance on MDR compliance, CER writing, and Notified Body preparation.
✌
Peace, Hatem
Your Clinical Evaluation Partner
Follow me for more insights and practical advice.
– MDR 2017/745 Article 61(5)
– MDR 2017/745 Article 61(11)
– MDCG 2020-5 Clinical evaluation assessment of equivalence
