Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document labeling and structured product data while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
EU MDR
The MDR establishes rules for placing medical devices on the EU market and covers economic operators, conformity assessment, quality systems, clinical evidence, technical documentation, UDI, registration, vigilance, post-market surveillance, and market surveillance. MDR work crosses QMS, product lifecycle, regulatory registration, UDI, technical documentation, clinical evidence, and post-market systems. Buyers need explicit system boundaries and reliable traceability across them.
EU IVDR
The IVDR establishes rules for in vitro diagnostic devices, including classification, conformity assessment, quality systems, performance evidence, technical documentation, UDI, registration, vigilance, post-market surveillance, and performance studies. IVD quality and regulatory records require device-specific classification, evidence, registration, and post-market workflows. Generic pharma or medical-device templates may not cover performance-study and IVD data needs.
ISO IDMP
The ISO IDMP family standardizes the identification and description of substances, dose forms and routes, units of measurement, regulated pharmaceutical products, and regulated medicinal products. EMA is implementing these concepts through substance, product, organization, and referential master-data services. IDMP readiness is a data-governance and operating-model question, not just a product feature. Buyers need to examine source ownership, data quality, terminology services, submission interfaces, stewardship, and change propagation.
Operating domains
Regulatory product and registration lifecycle
Risk that product, substance, device, market, registration, license, activity, authority, commitment, correspondence, and approval information is fragmented or too unreliable to support global regulatory decisions and market continuity.
Structured product data and labeling governance
Risk that medicinal-product, device, substance, pack, presentation, identifier, label, and artwork data is inconsistent across source systems, submissions, authority databases, markets, safety processes, and supply operations.
Complaints, post-market quality, and safety handoffs
Risk that complaints, adverse-event indicators, product-quality complaints, vigilance, field actions, recalls, post-market surveillance, and regulatory reporting are delayed or fragmented across quality, safety, medical, regulatory, and commercial systems.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should labeling and structured product data produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
EMA documents release of the public PMS API beta — The release increases the testability and reuse of some authority product data but does not remove the need for internal master-data ownership, reconciliation, and controlled regulatory workflows.
First four EUDAMED modules become mandatory — Medical-device organizations need controlled data ownership and change propagation across quality, product, certificate, operator, and regulatory records.