Electronic IFU, Symbols, and Language Requirements: Three Areas Where Labels Commonly Fail

Why these three areas cluster together

Electronic IFU, symbol management, and language obligations do not appear in the same section of MDR — they are spread across Annex I Section 23, Article 27 (for UDI), and Regulation (EU) 207/2012 (for eIFU). But they cluster together in practice because they are the three areas where labelling compliance most commonly breaks down during MDR transition work. Teams that handle label content correctly still run into problems here because the rules are either newer than MDD practice, or more specific than most teams realise.

Electronic IFU — conditions that must all be met

Regulation (EU) 207/2012 permits manufacturers to supply the IFU electronically rather than on paper for certain categories of devices — primarily devices intended for use by professionals in healthcare facilities. The conditions for eIFU are specific and all of them must be met; partial compliance does not count.

The key conditions are: the device must fall within a category listed in the Regulation as eligible for eIFU; the healthcare facility must agree to receive the IFU electronically (this is not a manufacturer decision alone); the manufacturer must ensure the eIFU is available on a website throughout the entire expected lifetime of the device; the IFU must be freely accessible without login or registration; and — this is the one that catches most manufacturers — the user must be able to request a paper copy free of charge at any time, and the manufacturer must supply it within seven calendar days.

The last condition is operationally significant. It means you need a process for receiving and responding to paper IFU requests, a stock of printed IFUs ready to dispatch, and a way to track that your seven-day commitment is consistently met. If you have moved to eIFU without setting this up, you are not meeting the eIFU conditions under the Regulation.

One more thing: when a new or revised IFU is published, the user must be notified. This means the manufacturer needs a mechanism for informing the healthcare facilities using the device that a document has changed — a simple URL that stays live is not sufficient if updated content is silently replacing previous versions.

Symbol rules — what "ISO 15223" actually means in practice

Symbols on labels are permitted under MDR, but only under specific conditions. A symbol must either appear in a recognised standard (primarily ISO 15223 for medical device symbols) or be explained in the IFU. Using a symbol that is not in ISO 15223 without an IFU reference is a non-conformity — even if the symbol is intuitive or widely used in the industry.

The practical problem is that ISO 15223 is a living standard. Symbols are added, revised, and occasionally retired. A symbol that was in the 2012 version of the standard may not be in the current version in the same form, or may have been superseded by a revised version. Your label must reference the current applicable standard version, and you need a process to detect when standard revisions affect your symbols.

Two issues come up repeatedly in audits. The first is that manufacturers use symbols from multiple standards — ISO 15223 for some, proprietary or regional standards for others — without a complete reference list. The second is custom symbols. If you have a symbol on your label that does not appear in any recognised standard, it must be explained in the IFU with the symbol itself, its meaning, and the context for its use. Many teams overlook this for symbols they consider obvious ("this means 'fragile'" or "this means 'keep upright'") — but obvious is not the same as standardised.

A practical approach: build a symbol register for each label. For every symbol used, record which standard it comes from, the version of the standard, and whether there is an IFU reference. Review this register whenever the label changes or when the referenced standards are revised.

Language obligations — the multi-country distribution problem

MDR requires that labelling — including the IFU — be provided in the official language(s) of the EU member states in which the device is made available. This is not optional and there is no EU-wide single-language exemption. If you sell in Germany, France, and Poland, your label and IFU need to be in German, French, and Polish (as well as any other required languages for those markets).

Where this becomes operationally complex is in managing multiple label variants. A physical label can only carry so much text before it becomes unreadable. For devices distributed across many EU markets, manufacturers commonly use a two-part labelling approach: a base label with the UDI, manufacturer details, and key safety symbols (which are standard-referenced and do not require translation), plus a separate translated label or language insert for the text content.

This approach works, but it creates a document control challenge. When the base label changes — a new UDI format, an updated storage condition, a revised warning — the translated versions may need updating. If your translation files are managed separately from your master label, a label change can create a period where the base and translated versions are out of sync. Your QMS change management process needs to address this explicitly.

Translation quality is also a compliance issue, not just a communication one. MDR requires that translated content accurately conveys the meaning of the original. A translation that changes the sense of a contraindication or a safety warning — even subtly — is a non-conformity in the translated locale. If you use a translation agency, the MDR-specific meaning of regulatory language needs to be part of your briefing to them. "Safe and effective" means something specific in an MDR context; a general translation may not preserve that precision.

Bringing it together: a pre-release label checklist

Before releasing any label version, run through three checks: first, that every symbol on the label is traceable to a current recognised standard or has an IFU reference; second, that every translated version accurately reflects the master and that your document control records confirm synchronisation; and third, if you are using eIFU, that all the conditions under Regulation 207/2012 are met — including the paper copy request process and the user notification mechanism for IFU updates. These are not one-time checks — they apply to every label revision you release.