Medical Device Labeling: The Unexpected Adventure in Fine Print and Frustration

A few weeks ago I explained to my teammates my dislike for labeling topics in medical devices. My colleagues found it so interesting that they suggested sharing my opinion on labeling with the world, so here it goes.

When I first started working on labeling regulations for medical devices, I thought it would be a simple project. The regulations define the content that must be included on the medical device or the instructions for use (IFU). Standards like IEC 60601 – Medical electrical equipment standard impose additional requirements. Nothing to worry about – kind of like IKEA instructions, except instead of assembling a coffee table you’re trying to prevent people from accidentally misusing a medical device that could affect patient, user, or third-party safety.

Taking a look in the Medical Device Regulation (MDR) one finds the first requirements on labeling in article 7. The requirements of this article are understandable: the labeling shall not provide information that may mislead the user regarding the intended use and functionality of the medical device but inform the user of risks associated with the medical device. Although the requirements are actually quite understandable, this is where the first hurdles arise in implementation.

Where do you draw the line? Extent of Medical Device Labeling Detail

We all heard the horrific stories in which an animal was dried in a microwave and unfortunately died. Since then there is supposed to be a safety hint in the microwave’s IFU stating that animals should not be microwaved (I never verified that claim). But is this the level regulators expect, given that medical devices are used by healthcare professionals?

Usability engineering provides the answer to this question by considering the intended use, the anticipated users, the disease/injury to be diagnosed or treated, and the usage environment. And if the usability engineers do their homework, they might discover that medical devices are not only used by medical professionals, but also by laypeople. A blood pressure monitor can be used by a tech-savvy teenager just as easily as by his/her 90-year-old grandmother. The safety hints in the IFU should therefore address both. This makes it all the more important to include meaningful safety hints in the IFU and not to let the IFU serve as a dumping ground for risk control measures that can not be implemented into the medical device by the planned release date.

Lost in Translation: The Trials of Medical Device IFU Language Requirements

Let’s move on to the requirements, which takes us to translations. Also a straight forward topic, right? That’s until you have to validate a Chinese translation. You start looking for a translation agency that ideally translates into all required languages ​​and has a technical background. If you want to keep the finance department happy, the translation agency will even work for free (as if). Once you find a translation service provider, you’ll quickly learn that Portuguese in Portugal is not the same as in Brazil, Norwegian differs in different parts of the country, and the claim that Austrian German is the same as German German could lead to the ambassadors of both countries being summoned.

Once you receive the required translations, you have to validate them. Unfortunately, it’s not enough to simply certify that something that looks Chinese is Chinese. Since many companies now operate internationally, there might be someone who can validate one or another translation. If these resources aren’t available, some manufacturers try to perform the validation using Google Translate. But wait, wasn’t there something in ISO 13485 about computerized systems that influence product quality and the need to validate these computerized systems?

By now we know that translations are annoying and we’re looking for a solution. This is where we come across the guidance on MDR/IVDR language requirements for manufacturers and quickly realize that many European countries would accept English if the medical device is used by healthcare professionals. However, anyone who thinks they’re off the hook and can get by with the English version is mistaken. Many of your customers will insist on labels and IFUs in their national language. So back to the beginnings and choosing the right translation service. Fortunately, some translation agencies are certified for ISO 9001 and ISO 13485. Additionally, a suitable translation agency holds a EC/IEEE 82079‑1 and/or ISO 17100:2015 certificate.

Verena Wieser, Medical device consultant at Lorit

Verena Wieser, Medical device consultant

Need support with labeling, compliance, or implementation across IEC and ISO standards?
We advise medical device manufacturers on IEC 60601, IEC 62304, IEC 61010, IEC 62366, ISO 13485 and more — through every stage of development, documentation, and certification.

Learn more

It’s Not a Drill: What to Do if Customer Requests IFU Paper Copy

The EU MDR says:” The instructions for use may be provided to the user in non-paper format (e.g. electronic) to the extent, and only under the conditions, set out in Regulation (EU) No 207/2012 [..].” Fun fact: the regulation (EU) 207/2012 referenced in the MDR has already been replaced by the implementing Regulation (EU) 2021/2226. Especially for SaMD it make sense to provide the IFU electronically. To do so the manufacturer has to carry out a risk assessment and determine if there are any risks if the eIFU is not available due to a technical issue like bad internet connectivity. Additionally, the manufacturer has to place the IFU on an prominent place on their website leading to gruesome discussions with the marketing team, that a link to the boring eIFU destroys the well designed homepage layout.

Last but not least, the manufacturer has to document a process in the QMS for printing and sending a paper copy of the IFU upon customer’s request within the set out time frame (at maximum seven calendar days). Not to forget the training of customer support team – because no, it’s not a joke when a customer asks for a paper copy of IFU; it actually has to be sent out within seven calendar days, or faster, if the risk management folks conclude seven days is too generous. All in all a lot of effort for a simple topic.

Understanding “Symbolism” in Medical Device Labeling

Next topic in the labeling saga is usage of symbols. Symbols can be found in ISO 15233-1 (for which a new amendment was published recently and added 25 new symbols). Depending on the intended use of the medical device, one might go through the ISO 15233-1 and pick the symbols that are suitable. Not every symbol is that straightforward, though. I would really like to know how a white church is related to the date of manufacturing. Maybe the ancient authors meant that one needs to start praying as soon as the device is assembled, who knows now. Another interesting symbol is the ISO 7000-1641 – book with the “i” in it – to inform the user to read the manual. Then there is IEC 60601-1 introducing another symbol – ISO 7010-M002 – indicating to read the manual because there are important safety hints in the manual. So what symbol shall be used?

Making Sense of UDI in EU MDR and US FDA

Last topic I strongly associated with medical device labeling is the Unique Device Identifier (UDI) topic. As a former software engineer I really appreciate clear requirements and IDs identifying different components. UDIs in medical devices are supposed to be, well, unique, but in reality they are more like distant cousins than identical twins across different regulatory systems. The US FDA and the EU MDR both require UDIs, but they have their quirks. In the US, the FDA’s system focuses on a single database (GUDID), while the EU requires registration in EUDAMED, which comes with additional data elements and complexities. The EU also has stricter requirements on label placement and direct marking for reusable devices. And let’s not forget the fun of different date formats – because why make things easy when you can have 01/07/2025 mean two different things depending on where you are? So while UDIs aim for global traceability, navigating them can feel like learning two dialects of the same confusing language.

Heartfelt conclusion

After all the headaches, mix-ups, and moments of sheer disbelief at how something so small can be so complicated, I still wouldn’t say I love labeling. Wrestling with content requirements, language regulations, and ever-changing standards has been a challenge – but it’s also given me the knowledge to help others through it. If my struggles mean that someone else doesn’t have to spend hours figuring out whether their label meets compliance, then it’s been worth it. So while I may not love labeling, I do love making it easier for those who need it.

By Verena Wieser, Medical Device Consultant

From risk management to regulatory compliance, we help medical device teams navigate standards like IEC 60601, 62304, 61010, and ISO 13485. Whether you’re reviewing your labeling approach or scaling up development, our team supports you with practical, tailored guidance and training.

CONTACT

Form

We look forward to hearing from you.

    Show privacy policy