Why tracking cards fail the clinical evaluation test

Hatem Rabeh

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

I reviewed a clinical evaluation last month where the manufacturer had a perfect implant tracking system. ISO 13485 certified. Database validated. Traceability from production to patient. The Notified Body still issued a major non-conformity. The reason? No connection between tracking data and clinical follow-up.

Most manufacturers treat implant tracking as a post-market surveillance task. A regulatory box to tick under MDR Article 27. They build systems to locate devices. They issue implant cards. They register serial numbers.

But they miss the clinical purpose.

Tracking is not just about knowing where the device is. It is about being able to follow what happens to the patient who received it. And that information must feed back into your clinical evaluation.

When this link is missing, your entire post-market system becomes mechanically compliant but clinically useless.

What MDR Article 27 Actually Requires

Article 27 of the MDR establishes the obligation for implant tracking. It requires manufacturers to provide an implant card with each device. The card must contain identification details, warnings, and information on how to retrieve safety updates.

But the regulation does not stop at traceability.

It explicitly states that the implant card must allow identification of the device and the patient. This is not administrative paperwork. It is the foundation for long-term clinical monitoring.

The purpose is clear: if a safety issue arises, you must be able to reach patients. If patients experience adverse events, you must be able to link them to specific device versions. If you need to update your clinical evaluation with long-term data, you must have access to real patient outcomes.

Many manufacturers read Article 27 and think logistics. The regulation expects clinical accountability.

Key Insight
Implant tracking is not a standalone requirement. It is the infrastructure that makes meaningful PMCF possible for Class III and implantable devices.

The Gap Between Tracking Systems and Clinical Data

Here is what I see repeatedly in clinical evaluations:

The manufacturer has a tracking database. Serial numbers are recorded. Batch codes are logged. Distribution records are maintained. But when I ask for clinical outcomes linked to tracked devices, the data does not exist.

The tracking system knows which hospital received which device. It does not know if the patient is doing well two years later.

This disconnect creates a major problem during clinical evaluation updates. You are required to include post-market clinical data in your CER. For implantable devices, that means long-term follow-up. But if your tracking system never captured clinical outcomes, you have no data to analyze.

The result is predictable. The clinical evaluation relies on literature and registry data. The manufacturer’s own tracked devices contribute nothing. The Notified Body asks why you are not using data from your own patients. You have no good answer.

Common Deficiency
“The manufacturer has implemented a tracking system compliant with Article 27 but has not established a process to collect and analyze clinical outcomes from tracked implants. No link between traceability data and PMCF objectives.”

What Reviewers Expect to See

When a Notified Body reviews your clinical evaluation for an implantable device, they look for evidence that tracking serves a clinical purpose.

They expect to see a defined pathway from implant card issuance to clinical data collection. They want to understand how you will use the tracking system to identify patients for follow-up. They need to see that the data collected through tracking feeds into your CER updates.

This is not theoretical. The reviewer will check your PMCF plan. They will look at your data collection forms. They will ask how you link adverse event reports to specific device versions. They will verify that your registry participation or follow-up protocols reference the tracking system.

If these connections are missing, the tracking system becomes a compliance gesture. It looks good on paper but contributes nothing to patient safety or clinical evidence generation.

Building the Link: Tracking to Clinical Evaluation

The solution is not complicated. But it requires planning before the device reaches the market.

Start with your clinical evaluation objectives. What long-term outcomes matter for your device? What risks need monitoring over time? What safety signals would require patient notification?

Then design your tracking system to support those objectives.

If you need five-year survival data, your tracking system must enable patient follow-up at five years. If you need to monitor a specific complication, your tracking system must capture relevant clinical endpoints. If you participate in a registry, your tracking identifiers must be compatible with registry data formats.

The implant card itself should reflect this purpose. It should tell patients why follow-up matters. It should provide clear instructions on how to report problems. It should make it easy for clinicians to contribute outcome data.

Most importantly, the tracking system should integrate with your post-market surveillance and vigilance processes. When an incident is reported, you should be able to identify other patients with the same device version. When you update your CER, you should be able to pull tracked patient outcomes into your analysis.

Key Insight
The implant tracking system is not a separate deliverable. It is part of the evidence generation infrastructure for your clinical evaluation. Plan it as such from the start.

Practical Implications for CER Updates

This integration becomes critical during periodic CER updates.

For implantable devices, you are required to provide clinical data that reflects real-world performance over time. Literature may not cover your specific design. Registries may not include your device yet. Your own tracked patients are often your best source of long-term evidence.

But only if you planned for it.

If your tracking system captures only administrative data, your CER update will rely entirely on external sources. If your tracking system includes clinical endpoints, you can present manufacturer-specific outcomes. If your tracking system links to structured follow-up protocols, you can demonstrate proactive safety monitoring.

The difference is substantial. One approach shows that you can locate devices. The other approach shows that you are actively learning from real patient outcomes.

Notified Bodies and competent authorities notice this difference immediately.

Common Mistakes I See

The most frequent mistake is treating tracking and PMCF as separate workstreams. Different teams. Different timelines. Different systems.

The tracking team focuses on compliance with Article 27. They build a database, print cards, train distributors. Meanwhile, the clinical team builds a PMCF plan. They define endpoints, draft protocols, plan publications.

These two efforts never connect. The tracking system does not support PMCF objectives. The PMCF plan does not reference tracking infrastructure. When it is time to collect data, everyone realizes the systems are incompatible.

Another mistake is assuming that distribution records equal clinical follow-up. I see manufacturers present shipment logs as evidence of traceability. They show that devices reached hospitals. But they have no mechanism to reach patients.

Distribution tells you where devices went. Clinical follow-up tells you what happened next. These are not the same thing.

Common Deficiency
“The manufacturer’s implant tracking system records distribution and sales data but does not include provisions for clinical outcome collection. No interface between tracking database and PMCF data collection tools.”

What Happens When Tracking Fails Clinically

When tracking is disconnected from clinical evaluation, several consequences follow.

First, your PMCF plan becomes aspirational. You promise long-term follow-up but have no infrastructure to deliver it. Reviewers see this immediately. They ask how you will identify patients. You point to the tracking system. They ask how tracking data flows into PMCF. You cannot answer.

Second, your incident response becomes reactive rather than proactive. When a serious adverse event occurs, you investigate the reported case. But you have no way to systematically check if other tracked patients experienced similar issues. You wait for reports instead of actively monitoring outcomes.

Third, your CER updates rely entirely on external data. You cite literature, reference registries, discuss competitor incidents. But you present no evidence from your own tracked devices. The Notified Body wonders why. You explain that data collection was not planned. The deficiency is recorded.

These are not hypothetical problems. I see them in review cycles every year.

Building It Right From the Start

The time to integrate tracking and clinical evaluation is during design and development. Not after CE marking. Not during the first CER update.

During risk management, identify which risks require long-term monitoring. During clinical investigation planning, define endpoints that tracking must support. During technical documentation, specify how tracking data will feed into post-market surveillance.

Then build the tracking system accordingly.

Choose identifiers that work across systems. Design data collection forms that match PMCF endpoints. Establish interfaces between tracking databases and surveillance platforms. Train commercial teams on the clinical purpose of tracking.

When you submit your clinical evaluation, the Notified Body should see a clear line from Article 27 compliance to clinical evidence generation. The implant card is not just a label. It is a tool for patient engagement. The tracking database is not just a registry. It is a source of real-world evidence.

This level of integration takes planning. But it is not optional for implantable devices.

Key Insight
Implant tracking that does not support clinical evidence generation is regulatory overhead. Tracking that feeds PMCF becomes a strategic asset.

What This Means for Your Next Submission

If you are preparing a clinical evaluation for an implantable device, review your tracking system against your PMCF objectives.

Ask yourself: Can I use this tracking system to collect the clinical endpoints defined in my PMCF plan? If a safety issue emerges, can I reach patients through this system? When I update my CER, will I have real-world data from tracked devices?

If the answer is no, your tracking system needs redesign before submission.

If the answer is yes, document it clearly. Show the linkage in your PMCF plan. Reference the tracking system in your CER. Demonstrate that Article 27 compliance serves a clinical purpose.

Notified Bodies reward this kind of integration. They see it as evidence that you understand the regulation’s intent, not just its text.

The difference between mechanical compliance and clinical accountability is often what separates smooth approval from extended review cycles.

In the next part of this series, I will address another critical integration point: how to structure PMCF plans when your device relies on equivalence. When your clinical evaluation is built on similar devices, your PMCF must fill specific evidence gaps. Most manufacturers miss which gaps matter most.

Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.

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). MDR Article 27

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.

References:
– MDR 2017/745 Article 27 (Implant Card and Information to be Supplied)
– MDR 2017/745 Article 61 (Clinical Evaluation)
– MDR 2017/745 Article 83 (Post-Market Surveillance)

Deepen Your Knowledge

Read Complete Guide to Clinical Evaluation under EU MDR for a comprehensive overview of clinical evaluation under EU MDR 2017/745.