Getting Ready: Drug Traceability

Published June 5th, 2021

As the community prepares for the GS1 Connect 2021: Digital Edition conference next week, the FDA issued new guidance to further enhance the security of prescription drugs in the supply chain. This guidance is intended to assist trading partners in complying with the law and achieving a safer, more secure, and more trusted drug supply chain.

The Drug Supply Chain Security Act (DSCSA), enacted by Congress on November 27, 2013, outlines steps to build an electronic, interoperable system to identify and trace U.S. prescription drugs. The regulation has a ten-year horizon with requirements and applicable standards unfolding in several phases.

As the industry struggles to meet specific milestones, FDA periodically delays regulatory enforcement. Six months ago, FDA surprised many by delaying enforcement of salable returns verification by an additional three years, until November 27, 2023.

New guidance on enhanced drug distribution security establishes an integrated view of drug traceability requirements, commonly referred to as the “enhanced system.” In this guidance, FDA makes clear that salable return verification should be considered an integrated capability of enhanced verification, as opposed to developing separate processes and systems dedicated just to salable returns verification.

For the first time, the FDA clarifies the enhanced system requirements and provides recommendations on system attributes necessary for enabling secure tracing of product at the item level. The FDA establishes a blueprint for a comprehensive approach to drug traceability and sharpens the focus on specific aspects (e.g. aggregation, inference, physical security, data and system security, errors and other discrepancies) deemed important to implementing a robust enhanced system envisioned under DSCSA.

November 2023 seems far away; do I need to worry?

Traceability requires that an extensive amount of item-level information be captured and exchanged at each ownership change. Successfully establishing traceability therefore requires each trading partner within the drug supply network to connect and exchange drug product information.

Most wholesalers are looking for the majority of their customers to be onboarded in the first half of 2023. Realistically, most industry trading partners have 18 months from today to get connected and share item-level transaction record information, consistent with DSCSA data content requirements and GS1 application standards.

Expect the onboarding process to be delayed the longer one waits to engage with trading partners. According to industry surveys, only 10-20% of the manufacturers are currently connected to their trading partners, which means sharing scarce resources with hundreds of companies and thousands of products. Recognize that few onboardings succeed initially, many require multiple iterations, so plan accordingly. What seemed to be off into the future, is now around the corner.

Since the FDA expects the product tracing information to be true, accurate, and complete, consider Gateway Checker’s conformance certification and establishing an automated approach to drug traceability integrity.

To learn more about how Gateway Checker is testing and certifying traceability conformance, join our virtual presentation An Automated Approach to Drug Traceability Readiness at GS1 Connect 2021: Digital Edition, taking place June 8-10, 2021. You will lean about an automated solution that can achieve accurate, rapid, robust and reliable connectivity with minimal errors, conformance to accepted standards, and identify gaps in preparedness.

We look forward to assisting the pharmaceutical industry on its path to traceability and we hope you will journey with us! If you like what you read, please share our newsletter and invite others to subscribe.

Click on the links below for additional information:

Gary Lerner,
President and Founder
Gateway Checker

Enhanced Drug Distribution Security at the Package Level under DSCSA

Published June 4th, 2021

On June 3rd, 2021, the FDA provided new guidance to further enhance the security of prescription drugs in the U.S. supply chain. To help stakeholders understand the emerging DSCSA requirements FDA published four guidance documents to assist trading partners in complying with the law and achieving a safer, more secure, and more trusted drug supply chain.

Three of the published documents either finalize or revise guidance on suspect product and product identifiers. From an industry participant perspective there is not much new as most of the content has already been published.  See: FDA provides new guidance to further enhance the security of prescription drugs

The fourth guidance, Enhanced Drug Distribution Security at the Package Level under DSCSA, is new and brings into focus the interoperable, electronic, package level product tracing systems, and processes required by section 582(g) of the F D & C act which go into effect on November 27, 2023.

For the first time FDA clarifies the enhanced system requirements and provides recommendations on system attributes necessary for enabling secure tracing of product at the item level. FDA establishes a blueprint for a comprehensive approach to drug traceability and sharpens the focus on specific aspects (e.g. aggregation, inference, physical security, data and system security, errors and other discrepancies) deemed important to implementing a robust enhanced system envisioned under DSCSA.

The new guidance on enhanced drug distribution security establishes an integrated view of drug traceability requirements, commonly referred to as the “enhanced system.” In this guidance FDA makes clear that salable return verification should be considered an integrated capability of enhanced verification, as opposed to developing separate processes and systems dedicated just to salable returns verification.

Furthermore, FDA expects the product tracing information to be true, accurate, and complete.  Consider Gateway Checker’s conformance certification and establishing an automated approach to drug traceability integrity to ensure continuous content verification.

Some content of the guidance represents more specific or new requirements that trading partners need to consider when making plans to support the Enhanced System.

Enhance System Elements

The FDA mandated the use of product identifiers to verify the product at the package level and enable prompt response when suspect and illegitimate products were found.

DSCSA included a ten-year timeline culminating in the building of “an electronic, interoperable system to identify and trace prescription drugs as they are distributed in the United States.”

DSCSA “Enhanced System” requires trading partners to exchange drug product tracing information (TI) and a transaction statement (TS) whenever there is a transaction that involves a drug product change of ownership.

The inclusion of both a TI and a TS represents a Transaction Record (TR).  Per the DSCSA, this information, the Transaction Record, must be exchanged in electronic form.

In short, the enhanced drug distribution security aspect of DSCSA mandates the exchange of a Transaction Record it each change of ownership.

Specifically referenced in this guidance, the Enhanced System includes the following:

(A) the exchange of transaction information and transaction statements in a secure, interoperable, electronic manner;

(B) transaction information that includes the data elements of the product identifier at the package level for each package included in the transaction;

(C) systems and processes for verification of product at the package level;

(D) systems and processes necessary to promptly respond with the relevant transaction information and transaction statement for a product upon request by FDA or other appropriate Federal or State official in the event of a recall or for the purposes of investigating a suspect product or an illegitimate product;

(E) systems and processes necessary to promptly facilitate the gathering of the information necessary to produce the transaction information for each transaction going back to the manufacturer upon request by FDA or other appropriate Federal or State official in the event of a recall or for the purposes of investigating a suspect product or an illegitimate product, or upon request of an authorized trading partner for the purposes of investigating a suspect product or an illegitimate product or assisting FDA or other appropriate Federal or State official with a request; and

(F) systems and processes to associate a saleable return product with its applicable transaction information and transaction statement to allow a trading partner to accept the returned product.

Other aspects of the Enhanced System requiring further review and scrutiny:

  • Physical Security Features – FDA recommends the use of security features on shipping units (such as homogeneous cases or pallets) of product to help indicate when product may have been tampered with, previously unsealed, or damaged, rendering it suspect.
  • A trading partner should only use inference when it receives pallets or homogeneous cases with aggregated data if the integrity of the unit is intact—in other words, the tamper-evident tape or wrap, or other security seal, has not been broken. If the receiving trading partner determines that the product is suspect, it should not use inference for the aggregated data.
  • Although under section 582(k) of the FD&C Act the requirement to provide and receive transaction history sunsets November 27, 2023, the enhanced system must include the ability to promptly facilitate the gathering of information necessary to produce the transaction information for each transaction going back to the manufacturer.
  • The enhanced system should permit only an authorized trading partner to request relevant data related to a product the authorized trading partner sold or purchased
  • The Selling Trading Partner Should Ensure that the Transaction Information and Transaction Statement Accurately Reflect the Product it Sells to a Purchasing Trading Partner
  • The product tracing information that will be provided to the purchasing trading partner in an electronic format should be checked to ensure that it accurately reflects the product that will be physically shipped.
  • A purchasing trading partner should undertake reconciliation upon physical receipt of the product and then before selling the product to help confirm the veracity of the inbound and outbound transactions.
  • If a wholesale distributor, dispenser, or repackager purchases product and identifies a potential clerical error or other discrepancy in the product tracing information it received, that trading partner should FDA expects the product tracing information to be true, accurate, and complete. resolve the error or discrepancy within 3 business days.
  • Examples of how trading partners may resolve errors:
    • The selling trading partner may provide new and revised product tracing information that reflects the products received by the purchasing trading partner.
    • The selling trading partner may provide new product tracing information only for the extra product received by the purchasing trading partner.
    • Either trading partner may use internal resources for identifying trading partners and their contact information to fill in such gaps in product tracing information received.

Click Here to review the DSCSA Enhanced System guidance

FDA Extends Saleable Returns Verification Until 2023

FDA is issuing new guidance for immediate implementation in accordance with 21 CFR 10.115(g)(2).

FDA is concerned that large volume of saleable returns coupled with the challenges of establishing reliable and robust technology may disrupt the distribution of prescription drugs in the United States.

FDA does not intend to take action against wholesale distributors who do not, prior to November 27, 2023, verify the product identifier prior to further distributing returned product. This is a 3-year delay from the current date of enforcement.

FDA also does not intend to take action against dispensers who do not verify the product identifiers of suspect product as required by DSCSA before November 27, 2023.

Instead the FDA believes that the delay in enforcement will allow manufacturers, repackagers, wholesale distributors and dispensers to focus resources and efforts on implementing secure, interoperable, electronic tracing of products at the package level.

“We envision that, along with other enhanced drug distribution security requirements, wholesale distributors can increase their efficiency by incorporating the saleable return verification requirements into the enhanced verification required by 2023 instead of developing separate processes or infrastructures.”

This delay does not affect other aspects of DSCSA. Manufacturers are still obligated to conduct product verification according to section 582(b)(4)(C) of the FD&C Act upon receiving a request for verification from an authorized wholesale distributor.  Furthermore, a wholesale distributor may engage in transactions involving a product only if such product is encoded with a product identifier.

Please contact us if you have additional questions on this policy and the impact on DSCSA deliverables.

How to Ensure Conformance to EPCIS Standards in Drug Traceability

Software can preview messaging protocols to ensure conformance with industry standards

Article Published in Pharmaceutical Commerce | July 3, 2020 | Updated: July 28, 2020

By Gary Lerner, Gateway Checker Corp

Within the next 30 months, some US pharmaceutical wholesalers are planning to be traceability-ready in accordance with the Drug Supply Chain Security Act (DSCSA). To some that might sound like plenty of time. To those of us with years of experience in the industry, it sounds more like a sprint to the finish line rather than a pleasant jog.

Even now, the US drug supply network is struggling with electronic, interoperable traceability without alignment around a common set of application standards. A report from the Office of Inspector General of HHS, while evaluating the current status of DSCSA traceability, recommended that “FDA offer educational outreach to trading partners about required drug product tracing information and data standardization guidelines.” [1]

There is a broadly (but not universally) accepted standard for trading-data communication: the EPCIS standard of the GS1 organization. But to ensure that EPCIS is being effectively employed by pharma trading partners, and the software vendors serving them, a testing protocol has been developed and sanctioned by GS1. This article will explain its justification and application.

Supply chain events

Drug traceability captures transaction events as individualized medicine containers and their parent cases travel from manufacturer to the point of dispense. By aggregating these events, regulators can understand location history, who has handled the product and for what purpose. FDA wants to ensure that only legitimate, uniquely identified product moves through the supply chain and that it is being handled by legitimate, licensed, and authorized trading partners.

To attain electronic, interoperable pharmaceutical traceability, each member of the drug supply network must connect and exchange information sufficient to enable supply chain transparency and integrity.

In fulfilling more than 25,000 prescription SKUs, thousands of companies around the world must establish an electronic, interoperable dialog. There is no shortage of connections to be made. On the production side there are as many as 5,000 connections necessary to network packagers, drug manufacturers, repackagers, and third-party logistics providers assuming each of the 2,000 producers needs on average 2 -3 connections per manufacturer. The largest wholesale distributors connect to as many as 500 drug producers which means for just the “Big Three”, 1,500 connections are needed. The remaining 90+ wholesale distributors are likely to, on average, need to connect to six drug producers bringing. Therefore, an estimated 2,000 connections are necessary for drug producers to connect inbound to distribution. Finally, each point of distribution must connect and communicate with more than 200,000 healthcare providers, which is likely to require an additional 2,000 connections.

Need for standards

As complexity increases and information exchange becomes more important, it is necessary for standards to be formed to ensure that products, processes, and procedures fit together and interoperate — and that there is a “universal language” of sorts to relay this information.

When it is critical for businesses to communicate effectively, standards matter. Standards allow different businesses to act in harmony enabling uniformity, reliability, accuracy, and precision. By adhering to standards, companies and organizations can work together to build products like cars, computers, and cell phones, or securely exchange personal, patient, product, and financial information.

Without well-defined requirements and strict adherence to standards, we struggle to establish interoperability and information exchange. To achieve accurate, rapid, robust, reliable connectivity with minimal errors, conformance to accepted standards is essential.

DSCSA application standards

Application standards are necessary to trace uniquely identified medicine containers as they move from initial packaging through the warehouse and then to the point of drug dispensation. The entities and their location involved with each drug transaction from initial introduction into commerce to the point of dispense must be captured, stored in immutable records, and be easily understandable.

Fortunately, tracking, capturing, and accessing this data is made possible by the Electronic Product Code Information Services (EPCIS), a GS1 standard which enables trading partners to represent and share information about the physical movement and status of products as they travel throughout the supply chain. It is essentially a common language that knows the details of each transaction (the what, where, when, and why) and facilitates a shared view of physical objects within, and between, enterprises.

Since EPCIS is in use around the world to address a variety of business needs across many industries, application specific standards are necessary to tailor EPCIS to suit a specific purpose.

The GS1 Healthcare US working group, made up of 50+ companies representing a cross-section of the industry, published EPCIS application standards governing DSCSA traceability in 2016.

Within months, each of the major US wholesalers published EPCIS onboarding guides based on the GS1 DSCSA application standards. Impediments to change, such as re-validating an existing system, are a barrier to standards adoption. However, things are changing; most new deployments are specifying EPCIS 1.2, a prerequisite for DSCSA traceability conformance.

Although the drug manufacturer is responsible for product packaging and drug-transaction data accuracy, it is the drug wholesaler that feels the impact of standards nonconformance. As noted, the wholesalers face the daunting task of having to onboard and receive drug traceability information from hundreds of manufacturers.

“A high-percent of the files we see for the first time have EPCIS conformance issues,” says Jeff Denton, VP of Supply Chain at AmerisourceBergen. “Avoidable issues require a significant amount of human resources to identify, communicate, resolve, and retest. It simply isn’t scalable for wholesalers to troubleshoot the standards conformance issues that conformance testing could address ahead of time.”

‘Almost’ compliant?

One EPCIS solution provider wrote us recently “If we are not currently perfectly compliant with GS1 standards, we are extremely close.”

As Ken Traub, an EPCIS visionary and the inspiration for our conformance tools once remarked: “There is no such thing as ‘almost’ standards compliant; it either is or it is not.”

Recognizing the need to establish unambiguous DSCSA conformance, GS1 established a conformance testing certification program to identify non-conformances and improve DSCSA traceability and interoperability. Requirements were developed for a reliable, scalable, and robust testing and certification service.

Rigorous testing benchmarks were established by the GS1 US working group to ensure common assessments of similarly constructed traceability scenarios. A certification program was launched to certify independent companies, like Gateway Checker, as a Conformance Testing Service.

As a result, opinions and creative interpretations can be supplanted with facts and an unambiguous assessment. Unbiased third parties can objectively test and evaluate conformance to GS1 standards for DSCSA traceability.

Conformance testing ensures implementation consistency among trading partners, aligns data structures, enables common data definitions, and avoids deployment delays.

As a supply integrity consultant assisting with the deployment of serialization systems, I see first-hand the time and effort wasted on bridging the standards conformance gaps. With full DSCSA standards compliance, different solution providers could generate or receive EPCIS messages in a “connect compatible” manner. All required elements would be structured correctly. All necessary content requirements would be mutually understood by the parties. The missing element to assure drug supply interoperability is a testing and certification system that can unambiguously assure message conformance to the DSCSA application standards.

In 2017 I assembled a team of traceability experts and industry practitioners to transform the 35,000 words published in the DSCSA Traceability application standards into a conformance assurance system. Our efforts resulted in a rulesbased conformance assessment platform that became known as Gateway Checker. Our conformance assurance service was tested and certified by GS1 as a Conformance Testing Service in 2019. Other conformance testing services are available. [2]

The Gateway Checker conformance testing system relies on hundreds of rules to examine the structure and content of EPCIS messages. Gateway identifies each non-conformance, provides a description of the issue and links to the offended section of the application standard. The system renders an ambiguous response; pass or fail. Passing EPCIS messages can be certified to one of 16 GS1 pharmaceutical traceability scenarios.

With Gateway Checker, proficient analysts can easily selfdiagnose compliance gaps within their submitted EPCIS messages.

“The Gateway Conformance Testing application provides unparalleled insight into traceability requirements,” said Vasudeva Saladi, Solution Architect, AmerisourceBergen. “It productively identified issues and highlighted what was needed to remedy them.”

Late last year, within just a few weeks’ time, Amerisource- Bergen became the first company to become Gateway Certified and attain the industry’s first GS1 Trust Mark.

Cost of nonconformance

Not following standards can result in spectacular failures.

Who can forget the $125 million Mars orbiter crashing into the planet because an engineering team used English measurement standards instead of the metric system?

DSCSA nonconformance costs are not the type of dramatic failure that panics the industry into change. Rather, it is a steady stream of lost time, excessive resource expense, and unnecessary rework that stretches onboarding projects from weeks to months. Custom-coded connectivity maps resist change and hinder adaptability to new technology and evolving regulatory requirements. Aggregate all the wasted time and effort into a bucket and the industry impact is in the millions of dollars.

We know there are significant gaps in drug traceability standards adoption. We have tested more than 100 industry files from different applications and found very few are able to fully conform.

There are substantial benefits from attaining DSCSA Gateway Certification. We have seen first time connections succeed and fully satisfying validation requirements without issue. Imagine the time saved, costs avoided, and confidence established when systems connect and communicate, first time, every time.

We are in this together. US drug traceability will advance when manufacturers, contract packagers, repackagers, regulators, and EPCIS solution providers understand that conformance to standards matters! To this end, Gateway Checker is offering a complimentary readiness assessment of an EPCIS file: go to https://gatewaychecker.com/readinessassessment/ and use the code PharmaComJune20 to begin the process.


TABLE: COMMON EPCIS DATA ERRORS

Based on work Gateway Checker has done to date, here are some common issues with EPCIS implementations

  • Elements missing or improperly structured
  • Events missing elements or contain incorrect attributes
  • Extensions incorrectly structured
  • Inconsistent or improper event time handling
  • Product Master Data missing or incorrect
  • Company Master Data missing or incorrect
  • Source owner/receiver and destination owner/receiver incorrect or missing
  • Events out of event time sequence
  • GS1 item and location identifiers not structured properly or incorrectly
  • Traceability scenarios not structured with required elements

REFERENCES
1. https://oig.hhs.gov/oei/reports/oei-05-17-00460.pdf
2. https://www.gs1us.org/what-we-do/partners/find-gs1- us-solution-partner/find-rx-epcis-conformance-tester


About the Author

Gary Lerner, founder of Gateway Checker, is an accomplished architect of supply integrity solutions. An expert in item-level serialization, Gary has developed successful supply chain and channel integrity solutions for nearly 100 leading brands around the world, serving the needs of pharmaceutical, medical device, packaged food, electronics and apparel manufacturers.

Read Print Article PDF >

EPCIS Data Exchange Issues in Pharma Traceability

GS1 connect logo, 2020

3 EPCIS Data Exchange Issues in Pharma Traceability

Keren Sookne | Healthcare Packaging | Jun 16th, 2020

Conformance testing services have emerged to cut down on wasted back-and-forth between manufacturers and trading partners to get efficient data exchange up and running.

Image depicting the complexity of the pharmaceutical supply chain

Gary Lerner, president at Gateway Checker Corporation, presented at GS1 Connect.

Pharma companies continue to make inroads to meet the DSCSA 2023 requirement for unit-level traceability at each change of ownership between trading partners. “Capturing and exchanging information at this level of specificity requires a common information framework,” explained Gary Lerner, president at Gateway Checker Corporation, at the GS1 Connect: Digital Edition (virtual) conference this week.

“This information framework captures what happens in the physical world with an electronic twin, essentially an information encoded representation of packing and shipping events that can be exchanged with trading partners. What’s needed to accomplish that is a common vocabulary and structure that enables trading partners to then share and exchange essential trading information in a consistent, accurate and interoperable manner,” said Lerner. Without a common standardized approach, there will be considerable waste in time and effort with trading partners negotiating the structure and content in each point of connection.

EPCIS

Lerner pointed to the value of the global GS1 standard EPCIS (Electronic Product Code Information Services), which enables the common information exchange language that can be shared. “However, EPCIS is a general purpose exchange standard. Application-specific standards are therefore necessary to tailor EPCIS to suit a specific industry and application. In 2015, the GS1 US Healthcare working group recruited more than 50 companies representing a cross section of the pharmaceutical industry to adapt EPCIS to address DSCSA specific requirements. And in 2016, the application standards governing DSCSA traceability were published. Adopting these standards therefore helps different businesses within the drug supply chain to more efficiently and effectively connect and share information,” he said.

Read Full Article >


Healthcare Packaging | Jun 16th, 2020

https://www.healthcarepackaging.com/issues/traceability-serialization/article/21137492/3-epcis-data-exchange-issues-in-pharma-traceability