top of page
Search

Does MDR Article 18 Set the Language for Implant Cards and Patient Information

  • 5 hours ago
  • 5 min read
Translator reviewing medical device documents at a desk

The member state where a device is implanted sets the language of the patient information that travels with the implant card. Not the country of manufacture, and not one English master file. Article 18 of the Medical Device Regulation, Regulation (EU) 2017/745, ties that language to the place of the procedure. A hip implant placed in Lisbon carries Portuguese. The same implant placed in Helsinki carries Finnish.


For regulatory affairs and labelling managers at implantable-device manufacturers, that one rule breaks the tidy idea of a single master version signed off once. You owe patient information in every official language of every member state where surgeons implant your device, and the check happens where patients receive care.


What Article 18 actually asks for


Article 18 covers two things, an implant card and the information supplied to the patient. The card carries the data that identifies the device, so a clinician or a patient can trace exactly what was implanted years later. The information supplied to the patient is the wider set a layperson needs to live with the device safely.


The MDR is blunt about language. That information must be stated in the language the concerned member state determines, and written so a layperson understands it. The European Commission guidance, MDCG 2019-8, fixes the card's format and content. Read together, they leave no room for a device to reach a patient with English-only information in a country that requires its own language.


What actually goes on the implant card


The card itself stays short. Under Article 18(1) it carries the identifying data rather than the full clinical story:


  • The device name, type, and model

  • The serial number or the lot number

  • The Unique Device Identifier, the UDI code that ties the card to the EUDAMED record

  • The manufacturer's name, address, and website


The warnings, the expected lifetime, the follow-up schedule, and the safe-use guidance sit in the accompanying patient information, and that is the text carrying the heaviest language load.


Why no single master version covers the EU


The EU has 24 official languages. Your device does not pick which one applies. The country of implantation does. Sell one implantable across 15 member states and you can owe patient information in 15 languages, each a controlled document that has to match the rest.


Hospitals sit inside this chain. Article 18(2) requires health institutions to make the card and its information available to every patient who receives the device, by a means that gives rapid access. The surgical team adds the patient's identity and hands the card over at discharge. If the wording you supplied is in the wrong language, the gap shows up at the bedside, not in your quality system.


Language professional checking medical device instructions

Where a language gap gets flagged


Patient-facing non-compliance is the kind a market surveillance authority can see without opening your technical file. A national competent authority, or a hospital reporting upward, can flag an implant card that reached a patient in a language the member state does not accept.


The reach behind that check grew this year. Since 28 May 2026 the four EUDAMED modules have been mandatory under Decision (EU) 2025/2371, and devices already on the market must be registered by 28 November 2026. The UDI printed on the card has to match the device data in EUDAMED, so a gap between what the card says and what the database holds is now simple to spot. A translation error stops being a private QA note and becomes a checkable defect.


Align the card with the SSCP and the IFU


An implant card never travels alone. The same device carries an instructions-for-use document, the IFU, and for implantable and class III devices a summary of safety and clinical performance, the SSCP required under Article 32 in a patient version and a professional version and uploaded to EUDAMED.


Three documents describe one device, so they have to speak one vocabulary. When the card names a component one way, the IFU another, and the SSCP a third, a reviewer sees three products. The control is a governed term base: the device name, the material terms, the warning phrases, and the follow-up wording locked once per language and reused across the card, the IFU, and the SSCP.


Reviewer checking a terminology checklist for consistency

Certified review is the real control


A term base only holds if a qualified person enforces it. At AD VERBUM we run implant-card and patient-information translation through certified subject-matter review rather than raw machine output, because language that reaches a patient after surgery has to be right the first time. Our medical-device workflow pairs ISO 13485, the device quality-management standard, with ISO 17100 for the translation process and independent revision, and ISO 27001 for how we hold patient and device data along the way.


That stack answers the three questions a surveillance auditor asks: was the translator qualified for the device class, did a second qualified linguist check the work, and can you show where the wording came from. We keep the term base, the reviewer sign-off, and the version history in one EU-hosted trail, so when a member state asks why a card reads the way it does, the answer is a record and not a reconstruction. For a manufacturer shipping one implant into a dozen language markets, that traceability separates a clean device registration from a market surveillance finding.


Our medical device translation services


Our translation services for regulated sectors run on ISO 27001 and ISO 42001 certified, EU-hosted infrastructure, with no reliance on public cloud tooling for core processing. Every project runs through our AI+HUMAN hybrid workflow: we ingest client Translation Memories and Term Bases first, our proprietary LLM-based LangOps System generates output constrained by client terminology on client-tuned open-weight models, and our certified subject-matter experts review for technical accuracy and regulatory compliance. Our QA is aligned to ISO 17100 and ISO 18587, with sector-specific requirements such as MDR (Regulation (EU) 2017/745) labelling and ISO 13485 device quality management applied where relevant. We serve Life Sciences, Legal, Finance, Defense, and Manufacturing clients across 150+ languages with 3,500+ subject-matter linguists. For teams managing audit-sensitive content, contact us to discuss your security and compliance requirements directly.


FAQ


Does MDR Article 18 require the implant card in the patient's language?


Yes. Article 18 of Regulation (EU) 2017/745 requires the information supplied with the implant card to be stated in the language the member state of implantation determines, and written so a layperson can understand it.


Which implantable devices are exempt from the implant card?


Article 18 exempts sutures, staples, dental fillings, dental braces, tooth crowns, screws, wedges, plates, wires, pins, clips, and connectors. Every other implantable device needs a card and its patient information.


Who hands the implant card to the patient?


The health institution that implants the device. Article 18(2) requires hospitals to make the card and its information available to every patient who receives the device, with the patient's identity added at the point of care.


What information belongs on the implant card itself?


The identifying data under Article 18(1): the device name and type, the serial or lot number, the UDI, and the manufacturer's name, address, and website. Warnings, expected lifetime, and follow-up guidance sit in the accompanying patient information.


How does the implant card relate to the SSCP?


Both describe the same implantable device. The summary of safety and clinical performance under Article 32 has a patient version and a professional version uploaded to EUDAMED, and its wording has to match the card and the IFU, which a shared term base keeps aligned.


What happens if the language is wrong?


It is patient-facing non-compliance a market surveillance authority can flag. With EUDAMED mandatory since 28 May 2026 under Decision (EU) 2025/2371, a UDI mismatch between the card and the database is easy to detect, and the finding can hold up sales in that market.


Recommended



 
 
bottom of page