Industry Workshop: IDMP-Native Product Data as a Shared Foundation

Across pharma, medicinal product data is still fragmented: multiple names for the same compound, function-specific definitions, and weak links across R&D, CMC, Regulatory, Manufacturing, and Commercial. The challenge is increasingly urgent: How can organisations create a shared foundation that provides the context each function needs without becoming the next silo?

‍

IDMP-native platforms are opening that path. Real value, though, comes from how companies implement them: durable identity, governed registration, cross-system linking, and a semantic core that can stretch across modalities and local needs.

‍

Hosted by Johnson & Johnson and facilitated by ACCURIDS and ZS, this Industry Workshop brings pharma peers together to exchange practical approaches and lessons learned. We will explore how organisations establish stable identity as names evolve, create a shared business language, and connect registration, ELN, RIM, MDM and enterprise data environments. We will also showcase how unstructured data, from public sources as well as internal documents, can be brought into that same foundation.

‍

The workshop will also look beyond today’s implementations and explore what these foundations could enable next: better cross-functional impact assessment, more intelligent automation and trusted context for AI-supported decisions.

‍

• When: Wednesday, 16 September 2026, 09:00–16:00 ET (15:00–22:00 CET)‍
• Where: Johnson & Johnson, Cambridge, Massachusetts (Boston area)‍
• Format: Interactive World Café / table rounds — short framing, peer dialogue, joint synthesis‍
• Who: Pharmaceutical and biopharma companies only.
• Takeaway: A sharper, practical view of what “good” looks like for IDMP-native product data and what peers implemented first, what they deferred, and where common patterns are emerging across the industry.

‍

On-site capacity is limited and requires advance registration for site access. Remote participation available.

Submitting the form is a request to participate, not a confirmed registration.