This guide is for the marketing lead, RA/QA manager or founder of a Galway medtech company (a device maker, contract manufacturer, component or packaging supplier, or regulatory consultancy) who is deciding what regulatory information belongs on the company website and how to present it so that it is accurate, current and easy to verify.

It is not regulatory advice. Regulations, guidance and transition arrangements change, and how they apply depends on your role and your devices. Confirm the specifics with your regulatory lead, your notified body or certification body, or qualified counsel before you publish anything.

Why vague compliance statements don't help

A line such as "ISO 13485 certified and MDR-compliant" gives a buyer's quality or regulatory team nothing to check. Supplier qualification usually involves verifying credentials against the issuing body, so a website that states those credentials precisely saves the reader a step. One that is vague or out of date raises questions before you have spoken to anyone.

There is also a regulatory reason to be careful with wording. "MDR-compliant" means different things depending on who you are. Under the MDR, obligations attach to economic operators (manufacturers, authorised representatives, importers and distributors) and to the devices they place on the market. A contract manufacturer working to its customer's design is usually not the legal manufacturer: the CE certificate and the technical documentation belong to the customer. If that is your position, say what you actually hold (for example, an ISO 13485:2016 certificate for a stated scope) and how you support your customers' MDR obligations, rather than claiming MDR compliance as if the device were yours.

Start by stating your role

Before you write a regulatory page, decide which of these describes you, and say it plainly near the top:

  • Legal manufacturer of CE-marked devices: you hold the technical documentation and, for most device classes, a notified body certificate.
  • Contract manufacturer or component supplier working under customers' quality agreements.
  • Sterile packaging, sterilisation or cleanroom services provider.
  • Regulatory or clinical consultancy supporting manufacturers.
  • Software developer whose product is, or supports, medical device software.

Everything else on the page follows from this. A buyer reading a consultancy's site wants to see expertise and relevant experience. A buyer reading a contract manufacturer's site wants certifications, processes and quality-system evidence.

The credential block: one entry per certificate

For each certificate or registration, publish the same set of facts, in the same order:

  1. The standard or regulation (for example ISO 13485:2016, or Regulation (EU) 2017/745).
  2. The issuing body and, for a notified body, its four-digit number.
  3. The certificate number.
  4. The scope exactly as written on the certificate: sites, activities, device types.
  5. Issue and expiry dates.
  6. Where it can be verified (the issuing body's public register, if it has one), or "certificate available on request".

A simple table or a set of cards works well. Put a "last reviewed" date on the page and give one named person, usually the RA/QA lead, responsibility for updating it whenever a certificate is renewed, extended or changed in scope. An expired certificate left on a public page does more harm than having no page.

Check your certification body's rules before using its logo or accreditation marks. Certification bodies set rules on how their marks may appear in marketing material.

EU MDR: reference the right parts, accurately

The EU Medical Device Regulation is Regulation (EU) 2017/745. It has applied since 26 May 2021 and replaced the Medical Devices Directive. In vitro diagnostics fall under the separate IVDR, Regulation (EU) 2017/746. Regulation (EU) 2023/607 extended the MDR transition periods for certain legacy devices, subject to conditions. If customers ask how legacy certificates are being handled, describe your own situation and point to the regulation rather than restating deadlines from memory.

Where it is relevant to what you do, you can reference specific provisions by number. The ones that come up most often:

  • Article 10: general obligations of manufacturers.
  • Article 15: the person responsible for regulatory compliance (PRRC).
  • Article 27: the unique device identification (UDI) system.
  • Article 52: conformity assessment procedures.
  • Article 61 and Annex XIV: clinical evaluation and post-market clinical follow-up (PMCF).
  • Articles 83 to 86: post-market surveillance, including the PMS plan, PMS report and periodic safety update report (PSUR).
  • Annex I: general safety and performance requirements. Annexes II and III: technical documentation.
  • Annex VIII: classification rules, including Rule 11 for software.

Citing an article is only useful if the sentence around it is correct and relevant to your business. A consultancy might explain how it supports clients through clinical evaluation under Article 61. A manufacturer might state how it meets the PRRC requirement under Article 15 (the role, not necessarily a name). MDCG guidance documents, published by the Medical Device Coordination Group, are the main interpretive source: cite them by document number when you rely on them, and check that you are citing the current revision.

Notified bodies: be precise

If you are the legal manufacturer of devices that need notified body involvement (most devices above Class I, plus Class I devices that are sterile, have a measuring function or are reusable surgical instruments), name your notified body and its number exactly as they appear on your certificate. Two that Irish companies frequently work with are NSAI, the National Standards Authority of Ireland (Notified Body 0050), and BSI, whose EU notified body is BSI Group The Netherlands B.V. (2797). BSI's UK entity (0086) acts as a UK Approved Body for the Great Britain market. Notified body designations and scopes can be checked in the European Commission's NANDO database.

Don't imply a notified body relationship you don't have, for instance by listing notified bodies you have "worked with" in a way that reads like certification.

US market: what is public and what to say

If you or your customers sell into the US:

  • Establishment registration and device listing records are public in the FDA's database. If you are registered, you can give your registration number and link to the record.
  • 510(k) clearances are public in the FDA's premarket notification database. A manufacturer can list its 510(k) numbers. A consultancy can describe the types of submissions it has supported, without naming clients who haven't agreed to it.
  • 21 CFR Part 820 sets the FDA's quality system requirements. The amended rule, the Quality Management System Regulation (QMSR), incorporates ISO 13485:2016 by reference. Describe your quality system in those terms if it applies to you.
  • MDSAP, the Medical Device Single Audit Program, allows one audit to address the requirements of the US FDA, Health Canada, Australia's TGA, Brazil's ANVISA and Japan's MHLW/PMDA. If you hold an MDSAP certificate, list the auditing organisation, scope and dates, as for any other credential.

Post-market surveillance and quality processes

Buyers' audits look closely at how suppliers handle complaints, CAPA and change control, and, for manufacturers, post-market surveillance and vigilance. You shouldn't publish internal procedures, but a short, accurate description of how these processes work and which standards they are built on (ISO 13485 for quality management, ISO 14971 for risk management) shows maturity. Avoid publishing performance figures such as turnaround times or defect rates unless you can support them and are content to be held to them in an audit.

Software as a medical device

If you develop medical device software, explain how you determine classification under Rule 11 of Annex VIII and which standards your development process follows, typically IEC 62304 for the software lifecycle, ISO 14971 for risk management and IEC 62366-1 for usability engineering. Under the MDR, a good deal of software that was Class I under the old directive moved into a higher class and needs notified body assessment, so this is an area where informed readers will notice any inaccuracy.

Writing for a Galway audience

Galway's medtech cluster brings together multinational operations, indigenous device companies, specialist suppliers and the research base around the University of Galway, including the CÚRAM research centre. Many readers of your site will be regulatory, quality and engineering specialists. Write for them: precise terminology, no vague claims, and an easy route to the documents they will ask for. Membership of the Irish MedTech Association or support from Enterprise Ireland can be mentioned where it is accurate and current.

Common mistakes to fix first

  • Certificates listed without numbers, scope or expiry dates.
  • Superseded versions (such as ISO 13485:2003) still mentioned on the site.
  • "MDR-compliant" claimed by a business that is not the legal manufacturer.
  • Customer logos shown without written permission, or wording that implies an endorsement.
  • Downloadable certificate PDFs that are out of date or no longer match the register.
  • A regulatory page that nobody owns or reviews.

Making the page findable

Put regulatory information on a dedicated HTML page that search engines can crawl, not only inside PDFs. Use a clear heading for each credential and a descriptive page title. Link the page from your main navigation or footer and from each capability page. Keep your company name, address and registration details consistent across the site, your Google Business Profile, directories and certificate records, so that buyers and search engines can match them.

Getting help

If you'd like a second pair of eyes on how your regulatory and capability content reads to a buyer, and how it is structured for search, get in touch. We work with your team remotely, and your regulatory lead remains the authority on what is accurate to publish.