Rental and Reprocessed Devices: Who Owns Clinical Evidence?

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

I see this pattern repeatedly: a manufacturer submits a technical file for a device intended for rental or reprocessing, and the clinical evaluation treats it as a standard single-use or permanent device. The sections on clinical data, post-market follow-up, and risk management read exactly like any other submission. Then a Notified Body reviewer asks a simple question: “Who is collecting clinical data when the device is no longer in your direct control?”

That question exposes a gap most regulatory teams have not considered. The clinical evaluation framework under MDR assumes a linear path: design, manufacture, place on market, monitor performance, collect data. But rental and reprocessing introduce non-linear patterns. The device cycles through multiple users. The manufacturer may lose visibility after first placement. Clinical data that should flow back to inform risk management and design changes becomes fragmented or absent.

This is not about technicalities. This is about whether the clinical evaluation remains valid across the actual lifecycle of the device.

What Changes When a Device Is Rented or Reprocessed

Under MDR Article 61, the manufacturer must establish, document, implement, and maintain a system for clinical evaluation. The regulation does not exempt rental or reprocessed devices. It does not lower the bar. It does not adjust timelines. The same requirements apply.

But the practical execution changes.

When a device is sold to an end user, the manufacturer typically maintains some connection through complaint handling systems, vigilance reporting, and PMCF activities. The user may be trained. The institution may report adverse events. The manufacturer can trace the device if needed.

When a device is rented, the connection weakens. The device moves between institutions. Each rental cycle introduces a new user environment, new handling procedures, new potential failure modes. The manufacturer must still collect clinical performance data, but the infrastructure to do so becomes more complex.

When a device is reprocessed—whether by the OEM or a third party—the question becomes: does reprocessing alter the clinical performance? Most manufacturers answer “no” without evidence. They assume that if the device meets technical specifications after reprocessing, the clinical data from first use still applies. That assumption does not hold under scrutiny.

Where Clinical Evaluation Files Break Down

The most common deficiency I encounter is the absence of reprocessing-specific clinical data. The CER will cite studies performed on new devices. It will reference post-market data from single-use contexts. It will include bench testing that validates the device meets specifications after cleaning. But it will not include data on clinical outcomes after reprocessing.

Notified Bodies look for this. They ask: “Do you have clinical data comparing first use to second use? Do you have data on infection rates after reprocessing? Do you have performance metrics across multiple cycles?”

If the answer is no, the clinical evaluation is incomplete.

Another gap: the PMCF plan does not account for rental or reprocessing workflows. The plan describes how data will be collected, but it assumes the device stays within a known user base. It does not describe how the manufacturer will track devices as they move between sites. It does not explain how adverse events will be linked back to a specific reprocessing cycle. It does not define what happens when a device is returned after rental and no feedback is provided by the user.

These are not hypothetical problems. These are the questions that stop submissions.

The Reprocessing Burden: OEM vs Third Party

If the OEM reprocesses the device, they control the process. They can build clinical data collection into the reprocessing workflow. They can track each cycle. They can correlate device history with clinical outcomes. The regulatory burden is high, but it is manageable.

If a third party reprocesses the device, the situation becomes more complex. The third party may operate under their own quality system. They may not report back to the OEM. They may not collect clinical data at all.

MDR does not give the OEM a pass in this scenario. Under Article 10(9), if a device is reprocessed, the reprocessor is considered the manufacturer for that reprocessed device. But the original manufacturer still holds responsibility for the initial design and clinical evaluation. If the reprocessing alters performance, the original clinical evaluation may no longer apply.

This creates a gap. The OEM cannot claim equivalence to their own device if the reprocessed version behaves differently. They must either gather data on the reprocessed version or demonstrate that reprocessing does not alter clinical performance. That demonstration requires evidence, not assumption.

What the Clinical Evaluation Must Address

If your device is intended for rental or reprocessing, the CER must explicitly address the following:

1. Clinical performance across use cycles. This means data showing that safety and performance do not degrade with reprocessing. If such data does not exist, the PMCF plan must describe how it will be generated.

2. Reprocessing validation from a clinical perspective. Bench testing is not enough. The validation must include clinical endpoints. If the device is reprocessed ten times, do clinical outcomes remain consistent? Is there a threshold beyond which performance declines?

3. Data collection strategy for rental scenarios. The PMCF plan must explain how clinical data will be captured when the device is not permanently placed at one site. This might include tracking systems, user agreements that mandate reporting, or registry participation.

4. Traceability across reprocessing cycles. The clinical evaluation must show that adverse events can be linked back to specific devices and specific reprocessing cycles. Without traceability, trend analysis becomes impossible.

5. Risk management integration. The risk management file must account for risks introduced by reprocessing and rental. This includes risks related to user variability, handling between sites, loss of traceability, and degradation over cycles.

Each of these points connects back to MDR Article 61 and the general safety and performance requirements in Annex I. They are not optional. They are not recommendations. They are requirements that Notified Bodies enforce.

PMCF for Rental Devices: Practical Challenges

PMCF for rental devices introduces logistical challenges that most plans ignore. The device moves. The users change. The feedback loops are weak. How do you systematically collect clinical data in that environment?

Some manufacturers attempt to address this through user agreements. The rental contract requires the institution to report adverse events and provide outcome data. In theory, this works. In practice, compliance is poor. Institutions may not have systems in place to collect the required data. They may not prioritize reporting for a device they do not own. They may return the device without any feedback at all.

Other manufacturers try to build data collection into the device itself. Smart devices with embedded sensors can log performance metrics. When the device is returned, the manufacturer downloads the data. This approach works better, but it requires design integration from the start. It also raises questions about data privacy and user notification.

A third approach: participation in clinical registries or post-market studies that track device performance independent of ownership. This approach spreads the data collection burden across multiple sites and provides comparative data. But it requires planning, resources, and ongoing coordination.

The key point: you cannot leave PMCF data collection to chance. If your device model depends on rental or reprocessing, your PMCF plan must be explicit about how data will flow back to you. If you cannot describe that flow, your plan will not pass review.

What Reviewers Look For

When I review a clinical evaluation for a rental or reprocessed device, I look for evidence that the manufacturer understands the full lifecycle. I look for clinical data that reflects actual use patterns, not idealized single-use scenarios. I look for a PMCF plan that acknowledges the complexity of rental and reprocessing workflows.

I also look for honesty. If the manufacturer does not yet have reprocessing-specific data, the CER should state that clearly and describe how the data will be generated. If traceability is limited, the plan should acknowledge that and propose mitigation. If rental introduces data collection challenges, the PMCF plan should address those challenges directly.

What raises red flags: a CER that treats a rental or reprocessed device exactly like a standard device. That signals the team has not thought through the implications. It signals the clinical evaluation is not tailored to the actual device lifecycle.

Notified Bodies push back on this consistently. They will not approve a device if the clinical evaluation glosses over rental or reprocessing. They will ask for data. They will ask for PMCF plans that match the reality of use. They will hold the line.

Moving Forward

If your device is intended for rental or reprocessing, start with this question: can I demonstrate that clinical performance remains consistent across the device lifecycle? If the answer is uncertain, you have a clinical evaluation gap.

Close that gap before submission. Build reprocessing into your PMCF plan from the start. Design data collection systems that match your distribution model. Acknowledge the challenges in the CER and show how you will address them.

The clinical evaluation is not a checkbox. It is a live document that must reflect the reality of how your device is used, reused, and monitored. Rental and reprocessing change that reality. Your clinical evaluation must change with it.