Last week the US FDA Center for Drug Evaluation and Research (CDER) published an update to their guidance agenda for calendar 2016. Originally published in January, this is the mid-year update, when the CDER has a shorter window to think about and, presumably, can be more accurate. What has changed since January? The number of Drug Supply Chain Security Act (DSCSA)-related draft guidance they expect to publish by year end remains the same, as reported by our friends at the Regulatory Affairs Professionals Society (RAPS).
In fact, according to RAPS, those
same six draft guidances were Continue reading FDA Plans Busy Second Half of 2016 With Six DSCSA Draft Guidances Expected
This week I am posting one of my favorite essays from last fall because at this moment, I am in the middle of moving my home and office from one side of the Chicago metro area to the other to be closer to our kids. Also at this moment, the FDA is almost eight months late in publishing the grandfathering guidance that was mandated by the DSCSA. Here it is again.
Regulations often make use of a concept known as “
grandfathering” to soften a given deadline so that it is easier for companies to meet. When allowed, grandfathering allows Continue reading Will Manufacturers Be Able To Grandfather Products In Their DC And 3PL? Again
Drug manufacturers, contract manufacturers (CMOs) and contract packagers (CPOs) are all working hard right now preparing to meet the November 27, 2017 deadline when all prescription drugs entering the U.S. market must contain the new machine- and human-readable product identifier defined in the Drug Supply Chain Security Act (DSCSA) (see “ The DSCSA Product Identifier On Drug Packages“). The date for repackagers is one year later (see “ Who Is A DSCSA Repackager?”). From what I hear around the industry, some companies are going to make that date, but some will not. What will happen next for those how are not ready? I discussed this from a regulator perspective last year in one of my personal favorite essays, “ An Open Letter To The FDA, EMA and ANVISA, RE: Who Are You Going To Punish?”, but what about from the perspective of those who will be late? Continue reading How Will The DSCSA Serialization Mandate Be Enforced After 2017?
Last week, Connie Jung, RPh, PhD, Acting Associate Director for Policy and Communications, Office of Drug Security, Integrity, & Recalls, U.S. Food and Drug Administration, spoke about the Drug Supply Chain Security Act (DSCSA) at the GS1 US Connect event in Washington DC. This was our latest opportunity to get a glimpse of what the FDA is thinking and what they are doing. Dr. Jung spoke for about 50 minutes and then answered questions from the audience. Continue reading FDA Speaks At GS1 Connect
A few months ago the FDA opened two “dockets”, or Requests for Comments (RFC) to collect ideas and experiences about technology pilots related to the Drug Supply Chain Security Act (DSCSA). The first docket was associated with the FDA Public Meeting held on April 5 and 6 (see “ The 2016 FDA Pilots Workshop”). The second docket was opened shortly after the Public Meeting to continue collecting the same kind of information from anyone who had already conducted their own pilots or was planning future pilots. Both dockets are now closed so here is a look at the responses. Continue reading HDMA Responds To FDA Pilots RFC
of this essay provided a wealth of hyperlinks into the Part 1 Code of Federal Regulations (CFR) and FDA guidance documents with content related to placing the National Drug Code in human- and machine-readable form onto drug packages prior to November 27, 2017 (see “ Is A GS1 GTIN Really Usable As An NDC For DSCSA Compliance? Part 1”). In Part 2, we will look at how the Drug Supply Chain Security Act (DSCSA) will change, or add-to, the requirements found in those earlier specifications. And finally, we will be able to answer the question in the essay title.
HOW THE DSCSA CHANGES THE NDC AND BARCODE REQUIREMENTS FOR DRUG PACKAGES
First of all, the DSCSA does not change anything
Continue reading Is A GS1 GTIN Really Usable As An NDC For DSCSA Compliance? Part 2
After November 27, 2017 the U.S. Drug Supply Chain Security Act (DSCSA) requires drug manufacturers (2018 for repackagers) to affix a DSCSA “product identifier” to all drug packages entering the supply chain (see “ The DSCSA Product Identifier On Drug Packages”). According to the DSCSA, that product identifier must be present in both human-readable and 2D Data Matrix barcode forms. Part of that product identifier is what is known as a Standardized Numerical Identifier (SNI). The SNI is composed of the drug’s National Drug Code (NDC) and a serial number (see “ DSCSA ‘Serial Numbers’”) that is unique on every individual package of that drug (see “ FDA Aligns with GS1 SGTIN For SNDC” and “ Anatomy Of An FDA SNI”).
Lately, I’ve heard people in the industry claim that it is acceptable to use a GS1
Global Trade Item Number (GTIN) that encapsulates an NDC (see “ Depicting An NDC Within A GTIN”) to satisfy the NDC part of this DSCSA requirement to affix the product identifier on a drug package. I’m not so sure about that. Let me explain. Continue reading Is A GS1 GTIN Really Usable As An NDC For DSCSA Compliance? Part 1
Almost everyone agrees that GS1’s Electronic Product Code Information Services (EPCIS) standard will be used by drug manufacturers and the large wholesale distributors in the United States for compliance with the serialization requirement of the Drug Supply Chain Security Act (DSCSA). Even I think that (see “ Will EPCIS Event Exchange Replace EDI ASNs for DSCSA Someday?”). But there is a problem that could kill its use beyond the internal uses of today, keeping it from being used for data exchange or the data repositories that will eventually become the way data is “exchanged” in 2023 as part of the Enhanced Drug Distribution Security (EDDS) phase of the DSCSA.
The problem is, EPCIS defaults to the use of a single location identifier, the GS1
Global Location Number (GLN). So what? Why is that a problem? Let me explain. Continue reading GLN: The Lowly Identifier That Could Kill The Use Of EPCIS For Pharma Regulatory Compliance
DISCLAIMER: RxTrace contains some of the personal thoughts, ideas and opinions of
Dirk Rodgers. The material contained in RxTrace is not legal advice. Dirk Rodgers is not a lawyer. The reader must make their own decisions about the accuracy of the opinions expressed in RxTrace. Readers are encouraged to consult their own legal counsel and trading partners before taking any actions based on information found in RxTrace. RxTrace is not a vehicle for communicating the positions of any company, organization or individual other than Dirk Rodgers.
RxTrace, a comprehensive exploration of the intersection between healthcare supply chains, track and trace technology, standards and global regulatory compliance.
Contact Us | Privacy Statement Copyright © 2009-2017 Dirk Rodgers Consulting, LLC. All Rights Reserved. RxTrace is a registered trademark of Dirk Rodgers Consulting, LLC
L, A, S, C