News|Articles|September 4, 2026

Q&A: McKesson's Scott Mooney on Closing DSCSA Data Exchange Gaps

Listen
0:00 / 0:00

Key Takeaways

  • Integrating DSCSA repositories with warehouse management systems supports high-volume product movement decisions while accommodating unit-level serialized data complexity.
  • Scaling ERP-to-EPCIS connectivity requires standards-based processes and sustained investment to maintain accurate, efficient transaction data exchange.
SHOW MORE

McKesson's Scott Mooney discusses the technical and operational challenges of DSCSA compliance, from linking ERP systems to EPCIS to recurring friction in 340B transaction data exchange.

Serialized data exchange under the Drug Supply Chain Security Act (DSCSA) has moved from a compliance mandate to a daily operational reality for wholesale distributors. As part of Pharmaceutical Commerce's ongoing coverage of HDA’s 2026 Traceability Seminar, we spoke with Scott Mooney, vice president of distribution operations, traceability, at McKesson about the practical side of serialization: linking ERP systems to EPCIS, the industry's uneven progress migrating from GLN to sGLN and the persistent friction points around 340B transaction data. His answers offer a look at where interoperability stands today from the distributor's side of the supply chain, and what still needs to happen for trading partners to close the remaining gaps.

PC: What are the main technical hurdles in connecting back-office ERP systems to EPCIS for a distributor handling large volume?

Mooney: At McKesson, our focus has been on building scalable, standards-based processes that support the accurate and efficient exchange of serialized transaction data. We've made significant investments in our systems and capabilities to support DSCSA requirements while helping ensure continuity of service for our customers.

McKesson integrates its DSCSA data repository with warehouse management systems, which support key product movement and distribution decisions. This approach helps manage the significantly greater volume and complexity of data generated by serialization, which tracks products at the individual unit level rather than the product level.

How is the transition from GLN to sGLN going across the industry so far, and where are trading partners encountering friction?

I can only speak from McKesson's perspective. We continue to work closely with our trading partners to support standards-based interoperability and secure, efficient data exchange across the supply chain. GLNs and sGLNs are new in use for DSCSA track and trace, so the experience in the industry is strengthening as time passes.

What are the most common challenges in 340B transactions, and how can they be avoided?

At McKesson, we focus on supporting accurate data exchange, clear processes and collaboration among stakeholders. Our goal is to help customers navigate evolving requirements while maintaining access to the medications patients depend on. One of the ongoing challenges is ensuring that DSCSA information can be efficiently accessed and utilized by the appropriate parties involved in a transaction. Continued industry collaboration, standards adoption and process refinement will be important to improving efficiency and reducing transaction-related issues over time.

What needs to change to address recurring 340B transaction challenges?

We believe continued collaboration, standards adoption and ongoing process improvements will support greater efficiency across the healthcare supply chain. McKesson remains committed to working closely with customers and trading partners to support compliance and patient safety.Data-sharing rights, established so that a contract pharmacy may see the DSCSA data provided to the covered entity, begins the resolution of the problems.