PIM for medical devices: UDI, EUDAMED data and hospital catalogues

What makes product data hard for medical device manufacturers?

Medical device data carries legal weight before it carries marketing value. Under the EU Medical Device Regulation and the In Vitro Diagnostic Regulation, manufacturers assign Unique Device Identification to their devices and register device data in EUDAMED, the European database for medical devices. The same data appears on labels, in instructions for use, in hospital catalogues and on distributor websites.

Four challenges recur in PIMvendors selections:

• Regulatory master data: UDI device identifiers, the grouping identifier for device families, risk class and registration attributes that must match the technical documentation.
• Governance: every change to a regulated attribute needs an approver, an audit trail and often a change control process.
• Hospital channels: purchasing organisations, national healthcare catalogues and distributors, each with GS1-based requirements and procurement codes.
• Content split: regulatory teams own some attributes, marketing owns others, and both edit the same product.

The PIM by industry heatmap rates medical devices high on technical depth, regulatory data and standards, and low on supplier onboarding. That profile favours PIMs with strict governance over PIMs built for speed. The requirements for regulatory product data page covers the evidence model.

Which standards and regulations apply to medical devices?

UDI and EUDAMED set the regulatory core, and GS1 standards set the channel core. In PIMvendors selections, medical device manufacturers typically face this set:

EUDAMED becomes mandatory in stages, module by module. The timeline has shifted before, so check the European Commission's current EUDAMED timeline when writing requirements. The PIM requirement stays the same either way: regulated attributes must match what is registered.

Decisive requirements for a medical device PIM

Four requirements decide most medical device selections. They sit mainly in the process and data model domains of the PIMvendors checklist.

1. Regulatory data governance: controlled attributes, approval workflows, audit trails and role separation between regulatory affairs and marketing.
2. System of record: a clear decision on whether UDI and registration data are mastered in the PIM, an ERP or a regulatory information system, with defined flows between them.
3. Packaging hierarchy with identifiers: device identifiers per packaging level, consistent with labels and with data pool output.
4. Healthcare channel output: data pool publication, national catalogue formats and procurement codes such as UNSPSC in the version each recipient requires.

The second requirement decides the architecture. PIMvendors sees manufacturers succeed with the PIM as master and with the PIM as consumer of regulatory data. Failure comes from leaving the decision open. The PIM vs MDM page covers the master data question.

{{list:requirements:PR}}

Three demo scenarios worth running

Run the demo with regulatory affairs in the room. PIMvendors' scenario method gives each vendor the same sample data and script.

1. Regulated change: change a regulated attribute for one device family, route it through regulatory approval, and show the audit trail with user, timestamp, old value and new value.
2. Packaging hierarchy: create a device with each, box and case levels, device identifiers per level, and publish the hierarchy to a data pool test environment.
3. Hospital catalogue: export 50 devices with UNSPSC codes in the version a national catalogue requires, plus a second version for a distributor.

Score scenario 1 with regulatory affairs and quality. Their acceptance matters more than marketing's in this profile. Ask the vendor to export the audit trail as a report, in the form an auditor would request. The Demo Theatre scenario library holds the script format.

Shortlist considerations for medical devices

Medical device manufacturers shortlist on governance and auditability first. PIMvendors describes capability profiles instead of vendor names at this stage:

• Enterprise multi-domain platforms: strong governance, audit trails and flexible master data models. Limitation: implementation effort and the need for validated configuration.
• Regulatory information systems with product data features: strong UDI and registration processes. Limitation: weak commercial content and channel syndication.
• Syndication-first platforms with healthcare data pool connections: strong hospital channel output. Limitation: internal governance and approval depth vary.
• Mid-market SaaS PIMs: quick to deploy for commercial content. Limitation: audit and validation requirements often exceed standard features.

Many manufacturers combine a regulatory system with a PIM. In that case, test the integration in the demo with a real change. Validation effort belongs in the business case as well, because a validated configuration takes longer to change after go-live. The vendor directory lists vendors alphabetically.

Composite pattern: a device maker separating regulatory and commercial data

This composite pattern combines situations PIMvendors sees regularly, and it describes no single client. A manufacturer of single-use surgical devices sells around 3,000 items to hospitals in Europe through distributors and purchasing organisations. UDI data sits in ERP, registration preparation runs in spreadsheets, and marketing maintains a separate catalogue for the website.

The selection started as a website content project. Regulatory affairs joined after the first vendor demo and changed the scope. The team decided the system of record for each attribute group, then wrote requirements for audit trails and approvals before any content requirement.

The demos ran with regulatory affairs scoring the regulated change scenario. One vendor showed an audit log but could not enforce a separate approval for regulated attributes. The shortlist kept the vendors that could separate regulatory and marketing ownership on the same product record.