Licence scope is jurisdiction-specific
An active Canadian medical-device licence demonstrates home-market status; it does not itself authorise placement on the EU market.
Sell medical devices in the EU from Canada · MDR / IVDR Article 11 
EU Authorized Representative for Canadian manufacturers.
Our name goes on the label only after your file stands up to review.
Canadian licensing, MDSAP and ISO 13485 records can support an efficient review. MEDDEV maps them against the separate MDR or IVDR file, EC REP mandate, labelling and EUDAMED responsibilities.
For Canadian medical-device and IVD manufacturers adding the European Union to an established home-market operation.
Established in the European UnionWarsaw, Poland · EC REP under MDR and IVDR Article 11
Online intake Secure connection MEDDEV brand serving medical-device companies since 2012 MDR 2017/745 & IVDR 2017/746 Mandate accepted only after review
Manufacturers who have worked with MEDDEV
Canada → European Union
Reuse strong evidence without assuming regulatory equivalence.
Health Canada issues medical-device licences under the Canadian framework. Union market access remains a separate route, with its own conformity, representative and registration obligations.
Quality evidence can travel
MDSAP and ISO 13485 records may support the quality-system review, while MDR or IVDR product obligations still need explicit mapping.
Close EU-specific gaps
We record owners for the EU declaration, certificates, clinical or performance evidence, labelling, UDI and EUDAMED work before appointment.
Official basis: Health Canada: about medical devices, European Commission: EUDAMED overview, MDR Article 11, European Commission: EUDAMED UDI/Device registration.
Local review focus
What usually needs attention for Canada manufacturers.
Canadian manufacturers may bring Health Canada, MDSAP and ISO 13485 evidence into the review. MEDDEV maps those records to the proposed MDR or IVDR route and checks where the Canadian product family, intended purpose or post-market evidence does not match the planned EU portfolio.
Need the wider comparison? Compare home-market evidence with the EU MDR/IVDR route →
Qualification file
What to prepare for the first EU review.
The initial website form contains no document upload. After the parties and scope are confirmed, MEDDEV provides a controlled transfer route for the records below.
- 01
Active Medical Device Licence or establishment records relevant to the product scope and the current Canadian label.
- 02
MDSAP and ISO 13485 certificates, audit scope and manufacturing-site list.
- 03
EU classification rationale, conformity route, declaration draft and notified-body certificates where required.
- 04
Technical-documentation index covering risk, clinical or performance evidence, PMS, vigilance and product-liability insurance.
Typical transition gaps
Issues to resolve before the mandate starts.
Licence-to-device mapping
Canadian licence groupings and identifiers may not match the Basic UDI-DI and device families planned for EUDAMED.
EU evidence structure
Strong Canadian evidence still needs the MDR Annex II and III or corresponding IVDR documentation structure.
EU label ownership
The EC REP name and address, EU declarations, UDI data and importer verification package need controlled release.
EUDAMED is no longer a future obligation
Four modules — actor registration, UDI/Devices, notified bodies and certificates, and market surveillance — have been mandatory since 28 May 2026 under Commission Decision (EU) 2025/2371 and Regulation (EU) 2024/1860. For devices placed on the market earlier and still being placed on the market, Regulation (EU) 2024/1860 allows no later than twelve months from publication of the Commission notice, which was published on 27 November 2025. Registration data therefore belongs in the market-entry plan, not after it.
Financial coverage: what the law says, and what we ask for
MDR Article 10(16) — mirrored for in vitro diagnostics by IVDR Article 10(15) — requires manufacturers to have measures in place providing sufficient financial coverage for potential liability under Directive 85/374/EEC, in a manner proportionate to the risk class, type of device and size of the enterprise. It does not prescribe a particular insurance policy. MEDDEV asks to see those measures because Article 11(5) makes the authorised representative legally liable for defective devices on the same basis as, and jointly and severally with, a manufacturer that has not met its Article 10 obligations. Reviewing the arrangement is our acceptance condition, and that provision is why.
Country-specific route
01 02 03
Check this portfolio →
From home-market records to EU representation.
Inventory Canadian evidence
Link MDL or MDEL status, MDSAP records, sites and device families to the proposed EU portfolio.
Build the EU gap register
Record differences in classification, evidence, certificates, declarations, labels and registrations.
Appoint after acceptance
Complete file and insurance review, sign the mandate and coordinate the EUDAMED and labelling work.
Questions from Canada
What manufacturers ask before appointment.
Does an active Health Canada licence authorise EU sales?
No. It documents Canadian market status; Union market access follows MDR or IVDR.
Can MDSAP and ISO 13485 evidence be reused?
They can support the quality-system review, but product-specific MDR or IVDR obligations still require mapping.
How are Canadian device families mapped to EUDAMED?
MEDDEV reviews the legal manufacturer, intended purpose, classification, identifiers and proposed Basic UDI-DI structure before registration work starts.
Do you require product-liability insurance?
We review the arrangement before accepting a mandate, and here is the honest basis for it. MDR Article 10(16) requires measures providing sufficient financial coverage proportionate to the risk class, type of device and size of the enterprise — it does not prescribe a particular policy. Article 11(5) then makes the authorised representative liable for defective devices jointly and severally with a manufacturer that has not met its Article 10 obligations. So the review protects both sides, and it is our acceptance condition rather than a rule we are quoting at you.
Acceptance is earned, not purchased
Not every mandate is accepted.
MEDDEV accepts only defined device scopes supported by evidence, working safety controls and a manufacturer we can rely on. A commercial enquiry never guarantees appointment. Our name appears on the label only after the acceptance review is complete.
MEDDEV mandate reviewAcceptance gate
Manufacturer, device and intended purposeAcceptance criterion
Conformity route and regulatory evidenceAcceptance criterion
Safety, post-market and vigilance controlsAcceptance criterion
Communication, response and liability arrangementsAcceptance criterion
Outcome: mandate accepted, conditions issued or mandate declined.
A status worth displaying
Turn regulatory acceptance into a visible trust signal.
Accepted manufacturers may use the mark where professional buyers assess regulatory readiness. Each use must remain connected to the active MEDDEV mandate and its defined device scope.
- Manufacturer websiteAlongside EU market-access information and the represented device portfolio.
- Product catalogueOn pages covering devices included in the accepted mandate.
- Distributor dossierAs a verifiable representation status during onboarding and due diligence.
- Sales presentationFor procurement, partner meetings and trade-fair communication.
Use boundary: the mark must not appear as a CE mark, product certificate or safety approval. It should not be added to the regulated device label, instructions for use or sterile-packaging information panel.
Before you enquire
Know what shapes the review and the fee.
We do not publish a one-size-fits-all price because the mandate depends on the device, portfolio and level of responsibility. The initial review identifies the scope before a fee is proposed.
Device and portfolio
Classification, IVD or medical device route, number of families, intended purpose and higher-risk features.
Evidence readiness
Technical documentation, clinical or performance evidence, quality-system records, certificates and labelling.
Ongoing responsibility
EUDAMED coordination, vigilance, authority response, importer interface, PRRC support and required review depth.
Fee principle: after the qualification review, we provide a defined scope and a proposal matched to the accepted mandate. No document upload is required in the first contact form.
01
Legal manufacturer
Confirm the entity, country of establishment, device family and intended EU market.
02
Core evidence
Have the classification rationale, technical-file index, conformity route and quality evidence available.
03
Post-market readiness
Identify complaint, vigilance, field-safety and authority-response owners before the mandate begins.
Typical review scenarios 01 02 03
The questions we resolve before a mandate starts.
These anonymised composite scenarios reflect recurring qualification patterns. They are not attributed client case studies or performance claims; the exact scope and outcome depend on the manufacturer and device file.
New EU launch
Problem: home-market approval is mistaken for EU access. Work: map MDR/IVDR, labelling, EUDAMED and importer responsibilities. Typical result: a defined launch route and a documented list of open evidence.
Change of EC REP
Problem: the outgoing representative controls records and dates are unclear. Work: plan custody, vigilance ownership and handover steps. Typical result: a controlled transition with responsibilities recorded before the new mandate starts.
Higher-risk review
Problem: a Class IIb, Class III or complex IVD portfolio has unresolved evidence or liability gaps. Work: enhanced file and response-readiness review. Typical result: accept, request defined evidence, or decline before exposure is created.
Regulatory briefings
EUDAMED · Article 123(3)
Cyber Resilience Act
Article 10a MDR
Manufacturers outside the EU
The obligations manufacturers outside the Union ask about most.
Each briefing states the provision it relies on and links to the official text. They are written for companies deciding whether, and in what order, to enter the European market.
Device data falls due on 27 November 2026.
Four modules became mandatory on 28 May 2026. The twelve-month obligation does not cover every device, and the wording decides which.
Read the EUDAMED briefing →Reporting duties start on 11 September 2026.
Products covered by the MDR are excluded. Companion software without a medical purpose, portals and service tools are not.
Read the cybersecurity briefing →Withdrawing a device now takes six months of notice.
The notice goes to the authority of the Member State where the manufacturer or its authorised representative is established.
Read the supply briefing →Not every part of a domestic file has to be rebuilt.
What transfers into a European file, what has no equivalent at home, and where a representative is required by law.
Open the compliance hub → Published acceptance criteria
Six tests every device scope must pass.
Priority goes to complete, traceable applications with a named regulatory owner. Meeting the entry criteria qualifies a scope for a decision; it does not guarantee acceptance.
- 01
Verified legal manufacturer and scope
The legal entity, authorised signatory, manufacturing sites, device families, models and intended purposes are consistent and traceable.
- 02
Defensible EU regulatory route
The qualification, classification and conformity-assessment route are documented, with valid notified-body involvement where required.
- 03
Controlled regulatory evidence
The EU declaration, agreed technical-documentation index, certificates, labelling and registration data describe the same device scope.
- 04
Working safety and post-market controls
Risk management, surveillance, complaints, vigilance, recalls and corrective actions have current records, owners and escalation routes.
- 05
Responsive manufacturer relationship
Named decision-makers can provide records, samples and technical answers and can act within agreed authority-response times.
- 06
Liability and continuity secured
Insurance, contractual responsibility, document access, sanctions screening, change notification and mandate continuity are acceptable.
What the status means: “MEDDEV Mandate Accepted” confirms MEDDEV’s written acceptance of an EC REP mandate for the defined device scope. It is a trust signal about regulatory readiness and the manufacturer relationship. It is not a CE certificate, product approval, independent safety claim or substitute for the applicable conformity assessment.
Meet MEDDEV in your own time zone. Live reference times for manufacturer markets. MEDDEV’s registered office is in Warsaw.
Request a 30-minute online meeting Vancouver–:–
New York / Toronto–:–
Warsaw–:–
Dubai–:–
Tokyo / Seoul–:–
Sydney–:–
The people behind your mandate
Director-level governance. Named specialists for regulatory execution.
Mikołaj Junosza-Szaniawski leads mandate governance, risk oversight and international delivery. Marta Junosza-Szaniawska and Barbara Jęcka-Izdebska remain the named specialists for conformity assessment, registration and ongoing regulatory coordination.
MEDDEV Compliance sp. z o.o. · Warsaw, European Union ul. Mydlarska 47, 04-690 Warszawa, Poland biuro@meddev.pl
Check my eligibility → 
Mikołaj Junosza-Szaniawski
Managing Director · EC REP Operations & GovernanceMikołaj brings more than 25 years of experience at KPMG, including as a Director in Audit Assurance, where he oversaw major sustainability-reporting assurance projects. He combines international project governance with a product-life-cycle perspective encompassing LCA, reuse, recyclability and environmental performance. At MEDDEV, he oversees mandate governance, risk escalation, specialist assignment and continuity of manufacturer communication.
25+ years at KPMG Director, Audit Assurance MBA · Carlson School of Management Specialist LCA training · MIT ESG lecturer · Kozminski University Programme manager · EPD Polska
One accountable contact, specialist depth when the device requires it.
The manufacturer does not need to coordinate a loose group of advisers. The named coordinators define the review scope, assign the relevant specialists and remain accountable for communication and the agreed regulatory work.
Regulatory affairsQuality systemsClinical evaluationPhysiciansBiomedical engineeringSoftware and cybersecurityAesthetic devicesPost-market surveillance
Marta Junosza-Szaniawska
Conformity assessment & EC REP mandate reviewMarta coordinates the initial regulatory assessment, defines the file-review scope and confirms whether MEDDEV can accept the representative mandate.
marta.szaniawska@meddev.pl +48 791 480 270
Barbara Jęcka-Izdebska
Registration, notifications & ongoing coordinationBarbara coordinates registration and notification work and remains a named contact for the practical steps that follow appointment.
barbara.jecka@meddev.pl +48 730 354 190