Skip to main content
Matrix One>Blog>Best eIFU Software in 2026: Top Electronic IFU Platforms Compared

Best eIFU Software in 2026: Top Electronic IFU Platforms Compared

Last updated on

Best eIFU software in 2026, ranked for medical device and IVD manufacturers who supply instructions for use electronically under EU MDR and Regulation (EU) 2021/2226.

Short answer: the best eIFU software in 2026 is Matrix eIFU, formerly Dokspot, followed by DocuLiv, RealBit eIFU, SmartEIFU, eIFU.com from enLabel, tracekey, Soom, Kallik, Innovatum and eIFUApp. Matrix eIFU ranks first because hosting, version management and the Article 5(3) paper request, which must reach the user within 7 calendar days at no additional cost, run as one white label service, and because it publishes its price: plans start at €420 a month for three product lines, with unlimited products and IFU documents. Which platform suits you depends on your SKU count and whether labelling or hosting is your real problem.

I am Chief Customer Officer at Matrix One, the company behind Matrix eIFU, and it is first on this list. Read the page knowing that. Every competitor entry below says what that tool is built for, and the axis where other tools beat us has its own section further down.

What is the 10 best eIFU software shortlist for 2026?

ToolBest for
Matrix eIFUCompliant hosting, version management and paper requests as one white label service
DocuLivA lean, EU centred eIFU portal and nothing more
RealBit eIFUValidation documents handed over rather than assembled
SmartEIFUAn IQ/OQ/PQ validation package and permanent QR codes in the subscription
eIFU.com (enLabel)Manuals, videos and CAD published alongside the IFU
tracekeyConsolidating serialisation, traceability and eIFU with one supplier
SoomScan to IFU on a phone at the point of care
KallikLabel and artwork management at global scale
InnovatumAutomating eIFU from an existing labelling database
eIFUAppRegulatory, QA/RA and operations teams buying by role, in English, Spanish or French

How do the ten compare at a glance?

The shortlist above is the one-line version. This is the same ten with what each is built for and where it is strongest, so you can tell in one pass which three belong on your evaluation list.

ToolBuilt forStrongest on
Matrix eIFUDevice and IVD makers who want eIFU run as a serviceHosting, versions and paper requests in one service, from €420 a month
DocuLivEU centred manufacturers with a contained catalogueA fast, lean portal with no hardware and a short path to live
RealBit eIFUQuality teams who want validation paperwork suppliedValidation documents shipped with the software, strong in Italy
SmartEIFURegulatory teams that want a validation package from day oneIQ/OQ/PQ package included and QR codes that survive revisions
eIFU.com (enLabel)Capital equipment and complex reusable devicesManuals, brochures, videos and 3D CAD served next to the IFU
tracekeyOrganisations already running track and traceOne supplier for serialisation, packaging data and eIFU
SoomUS hospitals and clinical staff holding the deviceScanning a device or implant card to pull the current IFU
KallikGlobal manufacturers with a large label portfolioEnterprise label and artwork depth across markets
InnovatumManufacturers with a structured labelling databaseeIFU generated from the ROBAR database, so versions cannot drift
eIFUAppRA, QA/RA and operations buyersRole based workflows for controlled release and multilingual access

What changed for eIFU in 2025 and 2026?

If you last evaluated eIFU platforms before July 2025, the eligibility question you were solving no longer exists in the same form. Commission Implementing Regulation (EU) 2025/1234 entered into force on 16 July 2025 and rewrote the scope of Regulation (EU) 2021/2226. That matters when you choose a vendor, because it moves the hard part of the job from "may we do this at all" to "can we prove we did it properly for every SKU we sell".

Which devices can use eIFU now?

Article 3 of Regulation (EU) 2021/2226 used to list the specific device categories allowed to ship electronic instructions. Regulation (EU) 2025/1234 removed that list. Electronic instructions are now available for medical devices and accessories intended for professional use across Regulation (EU) 2017/745, for legacy devices relying on the Article 120 transitional provisions, and for the products without a medical purpose listed in Annex XVI. We walk through the amendment clause by clause in our guide to eIFU under Regulation (EU) 2025/1234.

Does the paper obligation go away?

No, and this is the single most common misreading of the 2025 amendment. A device intended for professional use that can reasonably be expected to be used by a lay person, a patient at home for example, still needs a paper instruction for use in the box. Separately, Article 5(3) of Regulation (EU) 2021/2226 requires you to supply a paper copy free of charge, within seven calendar days of the request, to anyone who asks. Widening eIFU eligibility widened the number of SKUs that obligation now attaches to.

What did the amendment take away?

The duty to keep users who downloaded an instruction informed of every later update was deleted: Regulation (EU) 2025/1234 removed Article 5 point (12). Do not read that as permission to stop tracking versions. Article 5 point (13), as replaced, still requires every issued electronic version and its date of publication to be on the website for the whole retention period, except that obsolete versions may instead be made available on request. The notification burden moved. The evidence burden did not.

How does EUDAMED change the job?

Article 7(3), added by Regulation (EU) 2025/1234, requires you to supply the eIFU internet address to the UDI database under Part B, point 22, of Annex VI to Regulation (EU) 2017/745, at the latest from the date device registration in that database applies under Article 123(3), point (d) or (e), of the MDR. That makes the address a registered attribute you have to keep accurate, so a URL restructure on your website is a regulatory change, not a marketing one. See our walkthrough of registering your eIFU URL for EUDAMED and how unique device identification connects to it.

What does eIFU software actually need to do?

It is easy to think of eIFU as a PDF on a website. That framing is exactly what gets teams into trouble at audit. A serious eIFU platform carries regulatory, quality and operational weight at the same time. These are the criteria I weigh when I evaluate a tool, or help a customer evaluate one.

CriterionWhat to check
Regulatory coverageEU MDR and Regulation (EU) 2021/2226 as amended by 2025/1234, plus FDA electronic labelling and 21 CFR Part 11 if you sell there
Hosting and securityISO 27001 certified data centres, an availability record you can evidence, and a documented plan for when the site is down
Paper fulfilmentWho receives the request, who prints and posts it, and where the record lives that it went out inside seven days
UDI and EUDAMED linkageEach eIFU tied to the correct Basic UDI-DI, and the address kept current as product data changes
Version controlApproval workflow, full change history, and superseded versions retired but still retrievable
White label experienceUsers reach the document through your branding, not a third party portal that confuses patients and clinicians
Language and regionThe correct language and content served by market, with releases planned around local requirements
Validation and QAComputer system validation under a risk based approach, with the evidence and templates supplied rather than assembled
Pricing and supportPredictable cost, and a team that answers when a document has to change today rather than next week

What is the most common eIFU failure?

If I had to name the failure I see most often, it is teams treating the website as marketing infrastructure rather than regulated infrastructure. The document is controlled, the hosting is controlled, and the process around both has to be controlled too. Our multi-market eIFU guidance covers how the language and region criterion plays out in practice.

How did we rank these tools?

We have not scored these tools on a spreadsheet of ticked boxes, because every one of them will tell you it ticks every box. Instead we grouped them by who they serve best, from how each positions itself on its own website, the markets it focuses on, the certifications it publishes and the kind of company we see choosing it. SmartEIFU and eIFUApp were added on 29 October 2026 from their own sites, read that day.

How should you use this ranking?

Your job is to match the tool to your device portfolio, your target markets and the size of your regulatory team, not to pick whichever vendor claims the longest feature list.

1. Matrix eIFU (formerly Dokspot)

I am obviously not neutral about this one, so let me be specific about what it is built for. Matrix eIFU is a white label electronic instructions for use service for medical device and IVD manufacturers: users reach the current instructions on your own branded site in three clicks. It is developed and managed under an ISO 9001 certified quality management system, hosted in ISO 27001 certified data centres, and it ships with templates for the eIFU quality assurance processes, including software and system validation reports.

How does Matrix eIFU handle the paper request?

What sets it apart is that the paper request in Article 5(3) and the version history Article 5 point (13) asks for are handled by the same service that hosts the document. Audit logs, change records, approvals, paper orders, version management, website translations and geo-fencing are modules of the platform, and paper requests are managed by Matrix One within the time the regulation sets. Support answers in an average of one hour.

How much does Matrix eIFU cost?

Pricing is published rather than quoted: plans start at €420 a month for three product lines, with unlimited products and IFU documents, and updates and maintenance sit inside the subscription with no upfront investment. Matrix eIFU is one of four Matrix One products alongside Matrix Req for design controls and Matrix Quality for quality management, and each is bought on its own.

We publish what we do for specific situations rather than asking you to infer it: EU MDR compliance, EUDAMED readiness, FDA eLabeling, high SKU portfolios, IVDR, migrating off a homegrown CMS and PPWR and sustainability. The detail sits on the Matrix eIFU product page.

Built for: medical device and IVD manufacturers that want hosting, version retention and paper fulfilment run as one service by a vendor that hands over the validation evidence, from a handful of product lines to high SKU portfolios.

2. DocuLiv

DocuLiv is a focused, cloud based eIFU tool that advertises conformity with MDR 2017/745 and Regulation (EU) 2021/2226 and the ISO 27001 standard, with no special hardware to buy. It is straightforward to stand up and it does not try to be anything else.

For an EU centred manufacturer that wants a lean, dedicated eIFU portal and nothing more, it is a sensible shortlist entry, and being quick to deploy is worth real money when a certification date is close.

Built for: EU centred manufacturers with a contained catalogue who want a dedicated eIFU portal live quickly, and who will buy quality, labelling or requirements tooling separately.

3. RealBit eIFU

RealBit provides eIFU software together with the validation documents needed for certification, which is genuinely appealing to quality teams that would rather receive the paperwork than assemble it from a vendor questionnaire. Its footprint is strongest in the European market and particularly in Italy.

If bundled validation evidence is high on your list and your markets are mainly European, it deserves a look, and handing over the validation package up front removes one of the slowest steps in an eIFU implementation.

Built for: European, and particularly Italian, manufacturers whose quality team wants the validation package supplied with the software rather than built from a vendor questionnaire.

4. SmartEIFU

SmartEIFU is a dedicated eIFU platform that lists EU MDR 2017/745, EU IVDR 2017/746, Regulation (EU) 2021/2226, ISO 13485, FDA 21 CFR Part 801 and GDPR on its homepage. Its headline promise is validation: an IQ/OQ/PQ validation package is included with every subscription, so the system is audit ready before the first document goes live.

Two features stand out on its own site. Device QR codes and URLs stay the same across document revisions, which protects printed labels and, under Article 7(3), the address you registered. And a paper request workflow captures, logs and manages fulfilment inside the seven day window. It states an average of 72 hours from onboarding to the first live eIFU, a vendor figure rather than one we have tested.

Built for: regulatory affairs teams that want a validation package and stable QR codes from day one. Its homepage still describes competent authority notifications under an Article 8 that Regulation (EU) 2025/1234 deleted, so ask how that workflow maps to the current text.

5. eIFU.com (enLabel)

enLabel Global Services is a Boston based packaging and labelling integration house, and eIFU.com is its dedicated product information site. The pitch is breadth of content type: instructions for use sit alongside labels, manuals, brochures, videos and 3D CAD files in one place your customers can reach.

That suits manufacturers of capital equipment and complex reusable devices, where the instruction for use is genuinely one document among many that a clinical engineering team needs. Our eIFU.com alternatives page covers how it compares for a pure eIFU brief.

Built for: capital equipment and complex reusable device makers whose customers need manuals, videos and CAD files in the same place as the IFU.

6. tracekey

tracekey comes at eIFU from a serialisation and traceability heritage. If your organisation already thinks in terms of track and trace, there is a real argument for bringing labelling, serialisation and electronic instructions under one supplier and one data model.

I would consider it mainly when consolidating vendors is an explicit objective, for example when a packaging data programme is already in flight and eIFU can be absorbed into it rather than run as its own project.

Built for: organisations already running a serialisation or packaging data programme that want eIFU absorbed into it under one supplier and one data model.

7. Soom

Soom approaches the problem from the point of care. Its solution is built around scanning a device or an implant card with a phone to pull the current instructions for use, safety information and FDA recall data, and it integrates with PLM and content management systems so the document served is the current one.

That is a genuinely different answer to the access question, and it is the strongest fit where your users are nurses and clinical staff holding the device rather than someone at a desk with a browser. Its centre of gravity is the US market.

Built for: US focused manufacturers whose users are nurses and clinical staff scanning the device or implant card at the point of care.

8. Kallik

Kallik focuses on enterprise label and artwork management, with eIFU as part of that larger platform. For a global manufacturer wrestling with a large and complex label portfolio across many markets and languages, that depth is the entire point, and eIFU riding on the same content model is a real advantage.

If your artwork approval chain is the thing that actually slows your releases down, solving that and getting eIFU alongside it is the right order to do the work in.

Built for: global manufacturers whose bottleneck is label and artwork approval across a large portfolio, with eIFU riding on the same content model.

9. Innovatum

Innovatum's eLabeling offering is driven from its ROBAR database, which holds the relationships between products, their versions, the eIFU documents and the language translations. The eIFU is generated from labelling data rather than maintained as a separate set of files, which is a sound answer to version drift.

It suits manufacturers who already run structured labelling data and want eIFU to inherit it automatically, rather than maintaining the same version relationships twice in two systems.

Built for: manufacturers that already hold structured labelling data and want eIFU to inherit product, version and translation relationships from it automatically.

10. eIFUApp

eIFUApp, a brand of Corporation Pangea Holdings S.A., sells eIFU compliance software for publishing, controlling and distributing IFUs across EU MDR, IVDR and FDA requirements. Its site is organised by buyer: separate pages for regulatory affairs across the EU and US, for QA/RA workflow with controlled updates and revision visibility, and for operations teams delivering multilingual IFUs.

The site runs in English, Spanish and French and positions the product on affordability. It does not publish a price or name certifications on its homepage, so ask for both in the first call.

Built for: regulatory, QA/RA and operations teams that want a role based eIFU tool, particularly in Spanish or French speaking markets.

What Matrix eIFU is built for, and what you would buy alongside it

Matrix eIFU is built to host, version and serve the instruction for use and to answer the paper request, with the validation evidence supplied. It is not an artwork management suite. If your real bottleneck is label and artwork approval across thousands of SKUs and many languages, Kallik goes deeper on that job than we do, and Innovatum generates eIFU straight from a structured labelling database, which is a stronger answer to version drift when that database already exists.

What would a large manufacturer run alongside Matrix eIFU?

A large manufacturer with that problem would typically run Kallik or Innovatum for artwork and labelling data and an eIFU host alongside it. Article 6 is where the two meet: the packaging has to say the instructions are electronic and where to find them, so the artwork system and the eIFU address have to agree.

Which eIFU obligations generate the most tooling work?

These are the duties that decide whether a platform is adequate, and they are the ones to pressure test in a demo. Every number below is an article of Regulation (EU) 2021/2226 as amended by Regulation (EU) 2025/1234.

ArticleWhat it requires
Article 3Which devices may ship electronic instructions. The category list was replaced by Regulation (EU) 2025/1234
Article 4A documented risk assessment covering the move to electronic delivery
Article 5(3)A paper copy at no additional cost, at the latest within 7 calendar days of a request, or with delivery if asked at order
Article 5(9) and (10)Electronic IFU kept available for 10 years after the last device is placed on the market, or 15 for implantables
Article 5(13)Every issued version and its publication date on the website, or obsolete versions available on request
Article 6The packaging or device indicates the instructions are electronic, and where to find them
Article 7(3)The eIFU address supplied to the UDI database under Annex VI Part B point 22 of the MDR

What does Article 4 require of your risk management?

Article 4 requires a documented risk assessment covering the move to electronic instructions. It is not a formality. It has to consider the realistic failure modes of electronic delivery, including a user without reliable internet access, a site outage, and a user who cannot find the document. Your existing risk management file under ISO 14971 has to absorb this, and your chosen platform has to give you the availability and access evidence that closes those hazards.

What does Article 5(3) require on paper copies?

Article 5(3) requires a system that provides the instruction for use in paper form at no additional cost, within the period set in your Article 4 risk assessment and at the latest within 7 calendar days of the request, or with the device itself if the customer asks for paper at the time of order. That is an operational commitment with a clock on it, and it is the requirement most often left out of a software evaluation. Ask every vendor who receives the request, who prints and posts it, and where the record lives that it went out in time.

How long do you keep superseded versions?

Article 5 point (9) keeps the electronic instruction available for 10 years after the last device is placed on the market and at least 2 years past the expiry date of the last device produced; point (10) makes it 15 years for implantables and devices without an expiry date. Point (13), as replaced in 2025, wants every issued version and its publication date on the website for that period, though obsolete versions may instead be supplied on request. Either way you need an immutable history, not a folder of dated PDFs.

What has to appear on the packaging?

Article 6 requires that the packaging for each unit, or the device itself where there is no unit packaging, clearly indicates that the instructions for use are supplied electronically and where they can be found. This is a labelling change, not a website change, which is why an eIFU project always reaches back into artwork and packaging. Our notes on medical device labelling cover the knock-on work.

What does Article 7 tie to device registration?

Article 7(3) ties the eIFU address to UDI database registration, so the URL where your instructions live is registered information under Part B, point 22, of Annex VI to the MDR. Changing your URL structure then becomes a regulatory change management task with a registration update attached. Choose a platform whose addresses you can keep stable, and read our EUDAMED and eIFU walkthrough.

Does eIFU eligibility still need a notified body sign-off?

Regulation (EU) 2025/1234 deleted Article 8, which had written notified body review of Articles 4 to 7 into the eIFU regulation. Recital 7 gives the reason: compliance with the information the manufacturer supplies is already part of conformity assessment under Regulation (EU) 2017/745. So treat the eIFU evidence as part of your technical documentation. Your notified body still reviews it, in the place it reviews everything else.

What do notified bodies actually check on eIFU?

Because I have sat on the other side of the table, here is what tends to get examined, so you can pressure test any vendor before you sign.

What they checkWhat you need to be able to show
AvailabilityThe site was reachable across the period, and your documented plan for when it is not
Version controlWhich version was live on a given date, and that superseded versions were retired but remain retrievable
Paper fulfilmentThe request log, and that each copy went out free of charge inside seven calendar days
UDI linkageeIFU addresses mapped to the correct Basic UDI-DI and maintained as product data changes
Security and retentionISO 27001 certified hosting, and documents retained for the required period
ValidationComputer system validation covering the software, the device data and the eIFU processes

A good vendor will have honest answers and supporting documents for every one of these. If a sales team gets vague when you ask, treat that as data.

Where do eIFU projects go wrong?

Four patterns come up again and again.

  1. Choosing on price alone. The licence saving is recovered within a year in internal effort making an underpowered tool audit ready, and you pay for it again at every recertification.

  2. Forgetting the paper obligation. Teams read the 2025 scope expansion as the end of paper. It is not. Lay use that is reasonably foreseeable still means paper in the box, and Article 5(3) still means paper on request within seven days for everything.

  3. Underestimating change management. Moving from paper to electronic touches supply chain, labelling, packaging, artwork and your quality processes, not just your website. Article 6 alone puts an artwork revision on the critical path.

  4. Treating the URL as a marketing asset. A site redesign that changes your eIFU paths breaks registered addresses and printed labels in the field. Decide the URL structure once, with regulatory in the room.

How should you choose an eIFU platform?

Once you strip away the feature lists, the decision comes down to your size, your markets, and how much of the work you want the vendor to carry:

  • Smaller and mid size device makers. Prioritise published pricing, fast onboarding and ready made QA documentation. You do not have spare regulatory headcount to build and validate a system, so a service that hands you the evidence is worth more than a longer feature list.

  • Enterprises with broad labelling needs. Look at Kallik or Innovatum, which bring labelling, artwork and structured product data at scale, and accept that you are buying and implementing a bigger system.

  • EU focused, lean deployments. DocuLiv, RealBit or SmartEIFU can be quick to stand up when your markets and your catalogue are contained.

  • Teams that dread the paper request. SmartEIFU logs paper requests in a workflow and Matrix One handles them for Matrix eIFU customers, both because Article 5(3) is an operations problem, not a software problem.

  • Serialisation heavy operations. tracekey may let you consolidate a supplier you already work with.

  • High SKU portfolios. Whatever you choose, test it against your worst case: a product family with many variants and many languages. Our notes on high SKU portfolios explain why that is where platforms break.

One piece of advice regardless of size: pick the tool that makes your next audit easier, not the one that looks best in a demo. The demo is an hour. The audit is the rest of the product's life with you.

Where should you go next?

If you want to see how quickly you can move from paper to a compliant electronic IFU portal, book a Matrix eIFU demo and we will walk through your own SKU list rather than a sample one.

If the decision in front of you is specifically who hosts the eIFU website rather than which platform to standardise on, we rank that separately in the best eIFU hosting providers, scored against Article 7(2) of Regulation (EU) 2021/2226.

If your problem is the document lifecycle rather than the platform, we rank that separately in the best IFU management software for medical device companies.

Summary: which eIFU software is best in 2026?

Matrix eIFU is the best eIFU software in 2026 for medical device and IVD manufacturers who want compliant electronic instructions for use without building and validating the system themselves. It covers EU MDR and Regulation (EU) 2021/2226 as amended by Regulation (EU) 2025/1234, keeps every issued version on a controlled white label site, handles the Article 5(3) paper request inside the 7 calendar day limit as part of the service, and ships the QA and validation templates a notified body expects. It publishes its price, from €420 a month for three product lines with unlimited products and IFU documents, so the cost is known before the first call.

  1. Matrix eIFU. Best overall for medical device and IVD manufacturers who want compliant eIFU as a service, with paper fulfilment, validation templates and a published price.

  2. DocuLiv. Best for EU centred manufacturers who want a lean, dedicated eIFU portal live quickly.

  3. RealBit eIFU. Best for European quality teams that want the validation documents supplied with the software.

If you are a small manufacturer sizing this for the first time, the scoped version of this ranking is the best eIFU options for small medical device manufacturers, which covers what changed for smaller companies on 16 July 2025.

Last updated: 29 October 2026.

Watch: eIFU explained, the complete guide to electronic Instructions for Use (2026)

A full walkthrough of electronic IFU for medical devices: what EU 2025/1234 requires, who may use eIFU, and how Matrix eIFU handles hosting, versioning and access.

Best eIFU software: frequently asked questions

What is eIFU software?

eIFU software hosts and manages the electronic version of a medical device's instructions for use, so that users reach the current, approved document through a controlled website instead of a printed leaflet. A compliant platform adds version control, an audit trail, language and market handling, UDI linkage, paper copy fulfilment and the validation evidence that shows the system itself is controlled.

How much does eIFU software cost?

It depends on the vendor, and few publish a figure. Matrix eIFU does: plans start at €420 a month for three product lines, with unlimited products and IFU documents, and updates and maintenance are included in the subscription with no upfront investment. When you compare quotes, check whether validation documents, paper request handling and translations are included or billed separately, because those are the costs that appear after signature.

Is eIFU software compliant with EU MDR?

The software is not compliant on its own. Compliance is a property of your implementation. Regulation (EU) 2017/745 read with Regulation (EU) 2021/2226, as amended by Regulation (EU) 2025/1234, sets out when you may supply instructions electronically and the conditions attached. A good platform makes meeting those conditions straightforward and hands you the evidence, but the obligation stays with the manufacturer.

What did Regulation (EU) 2025/1234 change?

It entered into force on 16 July 2025. It replaced the device category list in Article 3, so electronic instructions are now available for devices intended for professional users, including legacy devices under the Article 120 transitional provisions and the Annex XVI products without a medical purpose. It deleted Article 5 point (12), the duty to inform users of later updates, and Article 8 on notified body review. It replaced Article 5 point (13) so obsolete versions may be made available on request, and added Article 7(3) on supplying the eIFU address to the UDI database. It did not remove the paper obligations.

Do I still need to offer a paper instruction for use?

Yes, in two separate ways. A device intended for professional use that can reasonably be expected to be used by a lay person still needs paper in the box. And under Article 5(3) of Regulation (EU) 2021/2226, anyone may request a paper copy, which you must provide free of charge within seven calendar days.

Can I host eIFU myself instead of buying a platform?

You can, and some manufacturers do. What you are taking on is computer system validation of your own hosting, an availability record you can evidence, an immutable version history, a paper fulfilment process with a seven day clock, and maintenance of the address registered in the UDI database. Teams usually underestimate the validation and the paper process rather than the hosting. Our notes on migrating from a homegrown CMS cover what the move looks like in the other direction.

How long do I have to keep old versions of an eIFU?

For the periods in Article 5 points (9) and (10) of Regulation (EU) 2021/2226: 10 years after the last device is placed on the market and at least 2 years past the expiry date of the last device produced, or 15 years for implantables and devices without an expiry date. Under point (13), as replaced in 2025, every issued version and its publication date stays on the website for that period, although obsolete versions may instead be made available on request.

Does eIFU apply to IVDs?

In vitro diagnostics sit under Regulation (EU) 2017/746 rather than the MDR, and the eIFU framework developed under Regulation (EU) 2021/2226 has long been used by IVD manufacturers. Check the specific route for your device class with your notified body, and see our IVDR eIFU notes.

How does eIFU work for the FDA?

The FDA permits electronic labelling for certain prescription devices intended for use in health care facilities, on conditions that differ from the EU route, including what has to appear on the label and what you must provide on request. Do not assume an EU compliant portal satisfies the US route. Our FDA eLabeling notes cover the difference.

Written by
Eva Kautenburger
CCO

Eva Kautenburger is Chief Customer Officer at Matrix One, where she leads Customer Success & Supp across the full portfolio of regulatory and quality management solutions for the medical device industry. A certified I. and II. Party Auditor with deep expertise in ISO 13485, EU MDR/IVDR, IEC 62304, and 21 CFR Part 820, she brings both the technical fluency and regulatory grounding that MedTech customers need to navigate complex compliance landscapes. In her role, Eva oversees a cross-functional team of Solution Consultants, Solution Engineers and Account Managers, driving onboarding, retention, support and strategic growth for customers ranging from emerging device companies to global enterprises as well as consulting intiatives to support customers in their regulatory journey.

View profile →