Article 70: The Notification Most Teams Get Wrong

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

Article 70 of the MDR establishes a specific notification mechanism that sits outside the typical Notified Body pathway. It applies to class I devices and certain situations involving established manufacturers. Yet many regulatory teams misunderstand when it applies, what it requires, and how quickly it must happen.

The confusion is understandable. Article 70 is procedural, not technical. It doesn’t evaluate safety or performance. But missing or mishandling this notification creates administrative blocks that delay market access just as effectively as a failed conformity assessment.

Let me walk through what actually happens when Article 70 applies, what the Competent Authority expects to receive, and where teams typically fail.

When Article 70 Notification Is Required

Article 70 applies in two main scenarios. First, when a manufacturer of class I devices places a device on the market for the first time. Second, when an existing manufacturer makes significant changes to registration or identification data already held by the Competent Authority.

The first scenario is straightforward. If you are a class I manufacturer and you have never placed a device under the MDR before, you must notify the Competent Authority before or at the moment of placing your first device on the EU market.

The second scenario generates more confusion. What counts as a significant change? The regulation speaks of changes to the manufacturer’s name, address, or contact details. It also covers changes to the range of devices or device categories covered by the registration.

But here is where teams stumble. They assume Article 70 only applies to class I devices. That is incorrect. Article 70 also covers situations where an authorised representative is designated or changes, or when there are updates to certain administrative details affecting any device class.

The timing matters. The notification must be submitted before or at the time of the event. Not after. Not weeks later when someone realizes the notification was required. This is an administrative gate, and regulatory authorities enforce it precisely because it feeds directly into surveillance systems and market oversight.

What the Notification Must Contain

Article 70(3) specifies the information required. The notification must include the manufacturer’s name, address, contact details, and information about the devices covered. If applicable, it includes details of the authorised representative.

This sounds simple. But the practical difficulty comes from ensuring consistency across systems. The information submitted in the Article 70 notification must match the information in EUDAMED once that system becomes fully functional. It must also align with the data on the device label, the Declaration of Conformity, and the technical documentation.

I see inconsistencies constantly. The registered address on the Article 70 notification differs from the address on the Declaration of Conformity. The authorised representative’s contact details submitted to the Competent Authority do not match those on the label. These inconsistencies signal poor quality management, and they trigger additional scrutiny.

Another point: the notification is not a one-time event. Any change to the data covered by Article 70 requires an updated notification. If you change your authorised representative, you must notify the Competent Authority. If you expand your device range into a new category, you must update your notification.

The Submission Process

Each EU Member State designates its own Competent Authority. The process for submitting Article 70 notifications varies by country. Some Competent Authorities have online portals. Others require email submissions with specific templates. Some request additional documentation beyond what the regulation explicitly requires.

This fragmentation creates operational risk. A manufacturer placing devices in multiple Member States must track different submission formats, timelines, and follow-up procedures. Missing one jurisdiction means non-compliance in that market, even if all other jurisdictions are satisfied.

I recommend establishing a centralized tracking system for all Article 70 submissions. Document which Competent Authorities have been notified, when the notification was submitted, and what response or acknowledgment was received. Maintain copies of all submission emails and attachments. Treat this as you would any other regulatory submission, with version control and audit trails.

The Competent Authority may request additional information or clarification. Respond quickly. Delays in responding extend the administrative uncertainty and can trigger enforcement questions about whether your device is legally on the market.

What Happens If You Miss the Notification

Missing or late Article 70 notifications do not invalidate your CE marking. But they do create legal exposure. The device may be considered not properly placed on the market in that Member State. This opens the door to enforcement actions, including orders to cease supply until the notification is corrected.

I have worked with manufacturers who discovered, during a market surveillance audit, that no Article 70 notification had been submitted years after the device was placed on the market. The regulatory response varied by Member State, but in every case, the manufacturer faced administrative penalties and immediate corrective action requirements.

More practically, missing the notification creates confusion during inspections. The Competent Authority has no record of your device or your organization. You appear on the market without proper registration. This triggers deeper scrutiny of your entire regulatory compliance posture.

Integration with EUDAMED

Article 70 notifications are transitional in nature. Once EUDAMED becomes fully operational for all device classes, registration will shift to that centralized system. But until then, Article 70 notifications remain mandatory and enforceable.

What changes when EUDAMED goes live? The notification mechanism will migrate to the electronic system. Manufacturers will register once in EUDAMED, and all Competent Authorities will have access to that data. The fragmented submission process will consolidate.

But the underlying obligation remains the same. You must notify before placing the device on the market. You must update when key data changes. The only difference is the mechanism and interface.

I advise teams to prepare now for EUDAMED registration even while managing Article 70 notifications. Ensure your data is clean, consistent, and centrally managed. When EUDAMED becomes mandatory, migration will be smoother if your current Article 70 data is already standardized.

Practical Steps for Compliance

First, establish a clear internal trigger for Article 70 notifications. Define in your quality management system when a notification is required. This includes initial market placement, changes to manufacturer details, changes to authorised representatives, and expansion of device categories.

Second, assign ownership. One person or team should be responsible for monitoring the trigger conditions and executing the notification. This responsibility should be documented in job descriptions or quality procedures.

Third, create templates for each Member State where you place devices. Even if the Competent Authority does not provide a standard form, develop your own template that ensures all required information is included consistently.

Fourth, track all submissions and responses. Use a spreadsheet or regulatory software to log submission dates, acknowledgment receipts, and any follow-up actions. Audit this log periodically to ensure no gaps exist.

Fifth, integrate Article 70 compliance into your device lifecycle procedures. When you change your authorised representative, the same change control process that updates labels and Declarations of Conformity should also trigger Article 70 updates.

How This Connects to Broader Compliance

Article 70 may seem administrative, but it reflects a deeper regulatory principle: transparency and traceability. Competent Authorities need to know who is placing devices on the market, where they are located, and how to contact them.

This principle runs through the entire MDR. Clinical evaluation, post-market surveillance, vigilance reporting—all depend on clear identification and accountability. Article 70 is the first step in that chain.

When teams neglect Article 70, they signal a broader lack of attention to regulatory obligations. Competent Authorities notice. Notified Bodies notice. And when something goes wrong—a complaint, an incident, a field safety corrective action—the absence of proper Article 70 notification compounds the regulatory problem.

I have seen enforcement actions escalate specifically because the manufacturer was not properly registered. The underlying device issue may have been minor, but the failure to notify under Article 70 added an administrative violation that increased penalties and reputational damage.

Final Thoughts

Article 70 is not glamorous. It does not involve clinical data, risk analysis, or technical performance. But it is mandatory, enforceable, and often overlooked.

The manufacturers who manage Article 70 well treat it as part of their routine regulatory operations. They know which Competent Authorities they have notified. They update notifications promptly when changes occur. They maintain records that would satisfy any audit or inspection.

The manufacturers who struggle treat Article 70 as an afterthought. They submit notifications late, inconsistently, or not at all. They discover the gap only when a Competent Authority or Notified Body raises the issue.

Which type of manufacturer are you? The answer is visible in how you manage Article 70 compliance.

And if you are still unsure whether your Article 70 notifications are in order, now is the time to check.

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