Tag Archives: lot number

The 2 Most Helpful Requirements In The DSCSA

There are lots of impactful requirements in the Drug Supply Chain Security Act (DSCSA), but there are two whose impact will likely increase the safety of patients far more than all of the others.  That is, they are the most helpful requirements.  Do they include serialization?  Verification?  Transaction documentation?  Wholesaler and 3PL licensing?  Not even close.

The two requirements that I believe will have the biggest impact on the safety of drugs in the US supply chain are the requirement to only engage in transactions with authorized trading partners, and the lot number being included in the 2D barcode.  Let me explain. Continue reading The 2 Most Helpful Requirements In The DSCSA

Identification Of Pharma Cases In The U.S.

5 BoxesLast week I discussed controversy over the use of GS1’s Serial Shipping Container Code (SSCC) in the Brazil pharma supply chain to meet regulatory requirements imposed by ANVISA.  But there are different controversies, or at least potential confusion, in the U.S. pharma supply chain surrounding case labels, and some of those are relate to the SSCC and its use.

A case product identification label is the label a manufacturer usually places on each homogeneous case at case-packing time to identify what is inside the corrugated box.  A “homogenous case” is a case that Continue reading Identification Of Pharma Cases In The U.S.

SNI’s Are Not Enough In a Plateau-Based Supply Chain Security Approach

I recently published an essay on RxTrace called “Plateaus of Pharma Supply Chain Security” in which I proposed that a better timeline for the introduction of technology to secure the U.S. pharmaceutical supply chain was one based on plateaus.  Each succeeding plateau would add the adoption of new technology and/or data communications among the participants in the supply chain with the intent of elevating the security over the previous plateau.

In that essay I included illustrative dates for each of the four plateaus that I offered as an example of the concept, but you could easily imagine the overall program having open-ended dates that would allow the supply chain to adopt one plateau at a time and move to the next plateau only if/when a security problem is discovered at the current plateau.  That is, jump to the next plateau only when necessary.  Taking this approach, you may never actually need to get to the later plateaus.

For example, imagine that the first plateau were for manufacturers to serialize all drugs at the pharmacy-saleable package level (what I normally call “unit-level”) with an FDA Standardized Numeric Identifier (SNI) and all supply chain owners of drugs were to read the SNI’s and simply keep records of who they bought them from and who they sold them to.

With no data communications between trading partners that includes the SNI’s it might seem that little
security has been gained over what is done today.  But this small step (“small” compared to a full pedigree or track & trace system) would allow criminal Continue reading SNI’s Are Not Enough In a Plateau-Based Supply Chain Security Approach