Enter your email address to subscribe to RxTrace and receive notifications of new posts by email. (About one per week on Mondays)

RxTrace Recommends:
Archives
  • 2012 (5)
  • 2011 (25)
  • 2010 (31)
  • 2009 (19)

Posts Tagged ‘distributed pedigree’

Could This Be Your Future Track & Trace/ePedigree Exchange Solution?

In a recent essay I discussed GS1 Healthcare’s proposed Network Centric ePedigree (NCeP) models that are currently available for review and discussion by the industry.  By the way, GS1 is giving everyone until December 15 to respond to a survey to provide them with your thoughts on the various NCeP models.  To review the videos and respond to the survey click on this link.

In a somewhat related news item, Pharmaceutical Commerce recently published an online article by Nick Basta about the Global Healthcare Exchange’s (GHX) project to build a new prototype for a track and trace data exchange hub called “GHX updates progress on a prototype data exchange for track-and-trace“.  That article was an update to a more in-depth article by Nick about the project from last April in the same online magazine called “Healthcare Exchange Bids for Prototyping a Track-and-Trace System“.  Combined, the two very interesting articles describe the prototype that is now complete and ready for piloting.

In fact, the GHX prototype implements Read the rest of this entry »

Why GS1 EPCIS Alone Won’t Work For California Pedigree, Part 2

There are more than one reasons why you shouldn’t expect to use GS1’s EPCIS by itself to comply with the California pedigree law.  Part 1 of this series showed that the traditional distributed network of EPCIS repositories in the U.S. pharma supply chain doesn’t work.  But that analysis assumed the use of the “vanilla” EPCIS standard, without the use of any “extensions”.  That’s not really the way GS1 intended EPCIS to be used.  In this and future essays of this series I will explore some of the approaches that make full use of the extensibility that is built into the standard.

In this Part of the series I want to take a closer look at the work of the Network Centric ePedigree work group of the GS1 Healthcare Traceability group.  I am one of the leaders of that group along with Dr. Mark Harrison of the Cambridge University AutoId Lab, Dr. Ken Traub, Independent Consultant, and Gena Morgan of GS1, along with strong contributions from Janice Kite of GS1 and Dr. Dale Moberg of Axway.  The larger group consists of people who work for companies in the pharmaceutical supply chain, GS1, and solution providers from around the globe, although I think the majority are from the U.S.

The NCeP group published a very interesting recording of a presentation that explains the details of their work.  It is called “NCeP – Technical Analysis Sub-Group, Event Based Pedigree”.  The purpose of this recording is to help people outside of the close-knit NCeP group to learn about the pedigree models developed there, evaluate them and provide feedback to the group about which model(s) should be Read the rest of this entry »

Impact of RxUSA v. HHS On Future Pedigree Legislation

I attended the Partnership for Safe Medicines (PSM) Interchange 2011 conference on October 27 in Washington DC.  (I’ll cover that event more fully in a future essay.)  For me, the event couldn’t have been better, but I measure events like this perhaps a little differently than most people.  The agenda is important and the quality of the speakers is absolutely important, but in my view those are simply the things that lead to the one thing that can transform a merely good conference into a great conference:  the quality of the attendees.

(The quality of the attendees is exactly why I like the HDMA Track and Trace Seminar.  BTW, this year’s HDMA event starts this Thursday).

In the case of this year’s PSM event, I rate the quality of the attendees very high, and that’s because I had a number of great conversations with some very knowledgeable people during the breaks and at the social event the evening before.  That was my interaction with the attendees, not the speakers.  One of the topics of conversation surrounded the question of what exactly it was the led to the successful challenge to the Prescription Drug Marketing Act (PDMA) pedigree provisions in the RxUSA v. HHS court case and appeal and whether or not the same thing might occur with other drug pedigree laws.

AN IMPORTANT QUESTION GOES UNANSWERED

One of the first speakers at the PSM event was U.S. Representative Jim Matheson (D-UT), sponsor of H.R.3026, the “Safeguarding America’s Pharmaceuticals Act of 2011” which was introduced into the House of Representatives on September 22, 2011.  There are some differences, but the core of this new bill is basically the same as Read the rest of this entry »

Inspecting An Electronic Pedigree

Within conversations held during the development of standards for electronic pedigrees it is sometimes common to hear people apply the following test to any pedigree proposal:

“A state inspector arrives at your facility without prior warning, enters the warehouse, picks up any random package of drugs and asks to see ‘the pedigree’ for this package.”

The point being made is that, according to the California Pedigree Law, at the very least, supply chain members will need to be capable of producing a full pedigree for any and every package of drugs in their possession at any time in case of a surprise inspection.

This scenario is an important one when selecting a pedigree model, but it often causes me to think about exactly what the company being inspected would show the inspector, and how they would do that.  Read the rest of this entry »

Why GS1 EPCIS Alone Won’t Work For California Pedigree, Part 1

For the application of unique serial numbers, or Standard Numerical Identifiers (SNIs), to packages as part of compliance with the California Pedigree Law in 2015-2017 , GS1′s Electronic Product Code (EPC), particularly in barcode form, is the clear winning standard.  But there seems to be a very common misconception going around that for pedigree data management, all you need to do to comply with that law is to deploy a system that is based solely on the GS1 Electronic Product Code Information Services (EPCIS) standard.  The  misconception assumes that there is a formula that can be followed to achieve compliance and that EPCIS is the whole formula.

In truth, EPCIS will almost certainly be an important component in the compliance formula but exactly how it fits, and whether there are other necessary components, has not yet been determined.

There are probably several reasons that this misconception persists.  First, GS1 US continues to promote their 2015 “Readiness” Program as if it is that formula.  The program documentation strongly implies that, if you simply follow their program, you will “be ready” to comply with the law; but it stops short of actually saying that you will be compliant.

Second, it seems like people are either able to understand the law well but not the technical standards, or they are able to understand the technical standards well but not the law.  The legal folks are left to trust what the technical people say about EPCIS, and the technical people assume that as long as the data elements identified in the law are present somewhere then EPCIS must comply.

Now I am not a legal expert but I’ve been looking at the text of the California Pedigree Law for a few years now and I think I understand it at a level that allows me to estimate how various technical approaches might fill its requirements.  Let me show you how 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.

© 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 »

About The Author
Dirk Rodgers

Dirk is currently a Sr. Consultant in IT working within the U.S. Pharmaceutical Supply Chain. He is currently co-chair of several technical work groups in GS1 and GS1 US. He was a co-chair of the original GS1 EPCglobal Drug Pedigree Messaging work group that created the DPMS pedigree standard. Dirk holds a BS in Electrical and Computer Engineering from the University of Wisconsin-Madison.