The US Food and Drug Administration (FDA) is calling for comments from the pharmaceutical industry on the interoperability of transaction standards required under a recently passed law intended to strengthen the supply chain against counterfeiters.
In 2013, Congress passed and President Barack Obama signed into law the Drug Quality and Security Act (DQSA). While the law is perhaps better known for its extensive pharmaceutical compounding reform provisions, it also contains another major component formally known as the Drug Supply Chain Security Act (DSCSA).
The core of the DSCSA is meant to establish a nationwide pharmaceutical track and trace system that deters drug counterfeiting. Drug packages would be required to carry a serial number as part of a lot-level tracking system within four years of the law's implementation, with a package-level tracing system coming six years after that.
One of the key components to the track and trace system is its traceability provisions. Each entity in the supply chain, from the original manufacturer to the end distributor, is supposed to keep track of the product coming into and out of its possession, allowing its path to be traced by federal regulators in the event of a problem. FDA could, for example, determine the point at which a counterfeit product entered into a legitimate supply chain, making it easier to bring a company into compliance or track down a counterfeiter.
But as the saying goes, the devil is in the details. And the details of this plan lie in the data each entity must hand off to one another, known as "transaction data."
In a new Federal Register announcement by FDA on 20 February 2014, the agency says it wants to figure out how to make sure all that transaction information, including histories and statements, is interoperable in both paper and electronic formats.
Part of the problem is simply with the scale of the DSCSA, which involves pharmaceutical manufacturers, federal regulators, drug distributors, drug dispensers, and a host of other supply chain companies, all of which need to be able to process and generate transaction data. Each of these entities has unique needs, as well as unique processes already in place for processing transactions.
The other part of the problem, as noted by Dirk Rodgers, an expert on track and trace, is that there are a lot of standards in this area already. Front-runners for data standards to be used in any FDA-mandated system include the Electronic Data Interchange (EDI) Advance Shipment Notice (ASN) standard, GS1 Electronic Product Code Information Service (EPCIS), the National Drug Code (NDC) system, electronic packing lists and invoices, and GS1's Drug Pedigree Messaging Standards (DPMS).
And while EDI is already widely used and a clear front-runner, it's not quite ready for primetime just yet, Rodgers noted.
"EDI is currently designed as a point-to-point data exchange technology that is intended to describe the current shipment," he wrote. "It will be necessary to come up with a way to include previous Advance Ship Notices (ASN) to fulfill the transaction history requirement, and some way to meet the requirements of the transaction statement."
Finding ways to make these standards interoperable will take time, Rodgers added.
And based on the amount of information FDA wants made available in each transaction file-name, strength, NDC, container size, container numbers, lots numbers, transaction date, shipment date, and business information-there's a lot to make interoperable.
For its part, FDA seems intent on getting to interoperability. Its Federal Register notice asks industry to weigh in on current practices, the feasibility of establishing documentation standards, and how information can be exchanged between private industry and regulators.
FDA's notice also contains 13 specific questions related to interoperability, split up into three categories:
Questions related to (1) current practices and suggestions for the interoperable exchange of transaction information, transaction history, and transaction statements and (2) the feasibility of establishing standardized documentation to be used by members of the pharmaceutical distribution supply chain to convey the transaction information, transaction history, and transaction statement to the subsequent purchaser of prescription drugs and to facilitate the exchange of lot level data:
Questions related to (3) current practices and suggestions for the exchange of information between supply chain stakeholders or with FDA to provide, receive, and terminate notifications, respond to requests for verification of suspect product, and respond to requests for information from FDA or other appropriate Federal or State officials in the event of a recall or for the purpose of investigating a suspect or illegitimate product:
Question related to capturing information that has not necessarily been addressed by the previous questions:
We have completed our migration to a new platform and are pleased to introduce the updated site.
What to expect: If you have an existing login, please RESET YOUR PASSWORD before signing in. After you log in for the first time, you will be prompted to confirm your profile preferences, which will be used to personalize content.
We encourage you to explore the new website and visit your updated My RAPS page. If you need assistance, please review our FAQ page.
We welcome your feedback. Please let us know how we can continue to improve your experience.