Posts Tagged ‘SNI’
Anatomy Of An FDA SNI
The U.S. Food and Drug Administration (FDA) published their “Standardized Numerical Identification (SNI) for Prescription Drug Packages – Final Guidance” document almost two years ago (see my essay “FDA Aligns with GS1 SGTIN For SNDC” from back then). The guidance was published as purely non-binding recommendations that reflected the Agency’s current thinking, but in my opinion it is a nice piece of work and can be used as a practical guide, as far as it goes, for implementing drug serialization programs today.
Why is that? It’s because drug manufacturers and repackagers need to serialize all of their prescription drugs that enter the state of California in 2015/2016. Can those companies make use of the FDA’s SNI guidance to comply with the serialization requirements of the California Pedigree Law? I will answer that question in this essay, but first Read the rest of this entry »
Should Regulations Dictate Technology?
In the U.S. pharmaceutical supply chain this question becomes, should regulators—state legislatures, state Boards of Pharmacies, Congress or the FDA—mandate specific technology for serialization, ePedigree and other regulations? This question arises whenever a new regulation is considered by any of these bodies or agencies. It’s an important question now that the FDA is considering standards for ePedigree, Track & Trace and related things and I think there are some natural conclusions that can be drawn from past examples that lead to a potential answer. Let’s review the history first.
EXAMPLE: EXISTING ePEDIGREE LAWS
The language of the U.S. Prescription Drug Marketing Act (PDMA) specified the kind of data that must be in a compliant pedigree but it did not identify any particular technology to carry that information. Of course, compared with today, what kind of technology was available back in 1987 when the PDMA was first introduced in the U.S. House of Representatives? Is it a paper pedigree? Can it be electronic? What is the format? Can GS1’s Drug Pedigree Messaging Standard (DPMS) be used to comply? Read the rest of this entry »
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 Read the rest of this entry »
Plateaus of Pharma Supply Chain Security
One of the most recent improvements that California made to their drug pedigree law was to spread out the compliance dates by supply chain segment. Previously, all segments had to comply with the regulation by January 2011. Now drug manufacturers will need to comply with half of the products (or sales) by January 2015 and the remainder one year later, distributors must comply by mid-2016 and the pharmacies by mid-2017. As I understand it, this spread was intended to help the industry fully prepare for the new requirements in their businesses. Companies would now have time to adjust to the changes implemented by their upstream trading partners according to their earlier deadlines.
This staggered start pleased a lot of people—particularly distributors and pharmacies. However, to me, the staggered start of the current California regulation doesn’t address the issue of complexity very well and a different kind of ramp up to full operation would be more practical and have better odds for success.
I discussed complexity in my last essay, “U.S. Pharma Supply Chain Complexity”. I tried to show what it is about the supply chain that leads to difficulty in the setup and execution of a drug pedigree system. On its own, the U.S. pharma supply chain is naturally complex. A truly workable and protective pedigree system needs to deal with that natural complexity without exploding in its own complexity and cost. As I pointed out in that essay, the problem with the more popular pedigree models (like DPMS and the various distributed pedigree models) is the large number of the point-to-point data connections that are necessary to reflect the natural complexity of the supply chain. That adds a lot of complexity.
THE PLATEAUS OF SECURITY
No matter which model the industry implements, starting it up will have its own complexities. In my view, regulators and industry should Read the rest of this entry »
U.S. Pharma Supply Chain Complexity

© Copyright 2011 Duncan Champney. used with Permission. This image was created with FractalWorks, a high performance fractal renderer for Macintosh computers. FractalWorks is available on the Mac App Store (Click on image).
The debate over pedigree regulatory models in the U.S. pharmaceutical supply chain often centers around how much data for each package of drugs needs to be moved between trading partners as those drugs move down the supply chain from the manufacturer to distributor(s) and ultimately to the pharmacy. The ideal model would minimize the amount of data moved yet always allow each member of the supply chain to check the prior history—the pedigree—of the drugs they are about to buy.
At a superficial level this appears to be all you need to do, but when you take a closer at the details of how the supply chain actually works in the U.S. you will see that there are other characteristics besides data volume per package that need to be considered.
FOUR VIEWS OF THE U.S. SUPPLY CHAIN
In the debates and discussions over pedigree regulatory models we are used to seeing a view of the supply chain that shows one manufacturer, one distributor and one pharmacy. That view masks so much important complexity that if we were to select a regulatory model or solution based on that view it would be far from ideal.
Here is a view of the supply chain where the vertical scale shows something closer to the true proportions between those three segments. Read the rest of this entry »
Partnership For Safe Medicines Interchange 2010
Last Friday I attended the first annual Partnership For Safe Medicines (PSM)Interchange 2010 event. PSM is a coalition of organizations that are committed to the safety of prescription drugs and protecting consumers against unapproved, counterfeit, substandard, mishandled or otherwise unsafe medicines. PSM was started a few years ago to help educate healthcare professionals and the public about the dangers of counterfeit and other illegitimate drugs. It is based in Vienna, VA but focuses on the problem globally. The membership is made up of professional organizations from industry, universities and government.
PSM is led by a distinguished panel of leaders and directors. The leaders are Read the rest of this entry »
February 3, 2012 (9:02)
February 3, 2012 (4:36)
January 24, 2012 (6:42)
January 24, 2012 (3:03)
January 23, 2012 (11:56)