Most Warehouse Management Systems (WMS) available on the market today do a fine job of allowing their users to manage inventories in the warehouses of drug manufacturers, distributors and chain drug stores.  A WMS is a software system that may be a part of a larger Enterprise Resource Planning (ERP) system, or it may be a third-party application that is interfaced with the owner’s ERP system.

All WMS systems that I am aware of are intended to be sold into multiple industries, not just in pharma.  That’s so that the WMS vendor can maximize their sales.  The more industries, the more sales and the more profitable it is.  Because some industries have long had serial numbers on some of their products (computers and peripheral equipment, cell phones, electronics, medical equipment, appliances, etc.) WMS vendors have included serial number handling in their software for decades.  In fact, I would bet that a serial number handling feature was included in WMS systems since the very beginning of that category of software.

However, buyers of WMS systems in the pharma supply chain should be very careful not to confuse a “serial number handling” or even “serialization” checkbox on the WMS vendor’s spec sheets with the kind of “serialization” they will need for compliance with modern pharma serialization regulations.  I include the California Pedigree Law, the potential future serialization requirements that may (or may not) be coming from the FDA, and those in the E.U.

THE DIFFERENCE BETWEEN WMS SERIAL NUMBER HANDLING AND PHARMA SERIALIZATION FOR REGULATORY COMPLIANCE

The reason is simple.  Despite the similar (or same) name, serialization in the pharma supply chain leads to significantly different functionality than dealing with serial numbers on products in other supply chains.  For example, think about what would be needed for a personal computer manufacturer.  They would need to keep track of which serial number is applied to which models.  They may want to keep track of who they shipped which serial number to, and they may want to connect their warranty registration, returns, warranty claims and service processes to their serial number database so they can make sure they know exactly which sub-model revision (hardware, firmware and software) they are dealing with and to confirm that the customer is valid (for after-sales service).  All of these serial number tasks can be easily accomplished within the WMS, within an add-on module, or within some module of the ERP system because they normally do not need to communicate with the systems of other companies.  These same kind of capabilities would be needed for all of the types of products I listed above.

But these capabilities are distinctly different from those that members of the pharma supply chain are going to need going forward and so these traditional serial number features of WMS systems are insufficient.  The pharma supply chain needs to use the serial numbers on drug packages to authenticate the supply chain history, either at each stop (California), at the point of dispense (E.U.), or somewhere in between (potential future U.S. FDA regulation).  This requires a different approach.

First, all companies within a given supply chain must follow certain standards to ensure interoperability of the serial numbers themselves and the how they will be handled across all members.  That is, a WMS vendor can’t simply make up their own serial number handling features because they will not interoperate with those from other vendors.  Second, some kind of standardized data exchange related to the serial numbers must occur between trading partners, and third, the management of the data must also be standardized so that the same functionality is made available to all parties in the supply chain.

STANDARDS ENABLE INTEROPERABILITY ACROSS THE SUPPLY CHAIN

In the U.S. and in many other countries around the world, GS1’s Global Trade Item Number (GTIN) plus serial number (or SGTIN) is the standardized serial number that has been chosen (see my essays “FDA Aligns with GS1 SGTIN For SNDC” and “California Enforcement Subcommittee Moves To Require FDA SNI” and also see the GS1 General Specifications).

In California the GS1 Drug Pedigree Messaging Standard (DPMS) is known to be usable for compliance and would fulfill the necessary standard format for data exchange and data management.  However, the industry has more recently been interested in the use of GS1’s Electronic Product Code Information Services (EPCIS) standard as the basis for the standardized data exchange and data management.  Personally I don’t think anyone has shown satisfactorily that it will comply with the current California law but it appears that companies who are members of GS1 U.S. Healthcare Traceability group are hoping that it will.  (See my essays “Why GS1 EPCIS Alone Won’t Work For California Pedigree, Part 1” and “…Part 2”.)  If the California Board of Pharmacy is willing to accept it, then it can be used for compliance, but until we know that, I think it’s risky to deploy systems that are only based on EPCIS.

We won’t know which standard will fulfill the needs of whatever federal pedigree regulation, if any, may be on the horizon until the regulation is published by the FDA down the road.  So far it is probably a good bet that EPCIS will play an important role and it is very unlikely that DPMS will play any role.  We’ll see…

Ignoring the debate over which GS1 standard would be used in the U.S., the point is, the existing serial number handling features of today’s WMSs will not be sufficient because they are intended for something else.  The key characteristic that both DPMS and EPCIS have that is missing from those existing WMS features is that they are able to document supply chain events that occur to GS1 serial numbers and therefore to the products associated with those serial numbers.  This includes Commissioning, Aggregation, Shipping and Receiving, among others.  When you include the fact that they are both standards that all solution developers can follow, which results in interoperability between their solutions, DPMS and EPCIS are the only ways to address the needs of these modern requirements in the pharma supply chain.

WMS AND SERIALIZED EVENT REPOSITORIES

I once thought that WMS and Pharmacy Management System (PMS) vendors would see the difference and perhaps would add at least the standard EPCIS interfaces to their products (see my essay “The Future of Traceability Repositories and Inventory Management Systems”), but as far as I know that hasn’t happened.  Perhaps they have concluded that a WMS isn’t really the place to store supply chain events.

The whole point of a WMS is for managing inventory and warehouse processes.  Serialized supply chain events are related to things that pass through the inventories, but the life of those events could extend well beyond the life of the typical data element a WMS needs to deal with today.  The data communications and management needs of serialized supply chain events is also beyond the traditional scope of a WMS.  It now seems to make more sense to have a separate repository just for those events and maintain minimal connection between that repository and the WMS.  Perhaps the only connection would be related to the time that the serialized products are present in the inventory that the WMS is managing.

Figure 1.

That might require some interface(s) between the two systems since the serialized event repository is an inventory system of a sort.  For each product code the WMS will likely maintain an inventory count and the event repository will likely maintain a list of serial numbers in the same inventory.

If you are shopping for a new WMS and you know you will need to comply with a pharma serialization regulation, make sure you fully understand the limits of the serial number handling capability of the products from each vendor you are considering.  Don’t assume that you will be covered just because the spec sheet has a check box for “serialization”.

Dirk.

Any company wishing to make use of GS1 standards—including their barcodes, identifiers and data exchange standards—must first obtain a GS1 Company Prefix, or “GCP”.  Normally you would obtain a GCP by applying to the GS1 Member Organization (M.O.) in the country where your company headquarters resides, but if you are a pharmaceutical company that makes drugs for the U.S. market, regardless of where you are located, you will need to obtain a special GCP from GS1 US, the GS1 M.O. in the United States.

That’s because currently, drugs sold into the U.S. market must contain a linear barcode that encodes your U.S. Food and Drug Administration (FDA) National Drug Code (NDC).  To properly encode that NDC into a GS1 barcode symbol, you must register with GS1 US the GS1 GCP that matches the FDA-assigned Labeler Code that is a part of every NDC.  Only GS1 US can assign/register a GCP that matches your FDA-assigned Labeler Code.  I explain all of this in more detail in my essay “Anatomy Of The National Drug Code”.

Companies may end up with more than one GCP over time for several reasons.  For example, if a drug company is based in Switzerland, merged with another pharmaceutical company in France a few years ago and sells pharmaceuticals globally, they may end up with the following GCPs:

• One issued by the Swiss GS1 M.O. obtained originally by the parent company
• One issued by the France GS1 M.O. obtained through the merger
• One issued by the U.S. GS1 M.O. registered by the parent company for use in identifying drugs sold into the U.S. market
• One issued by the U.S. GS1 M.O. obtained through the merger for use in identifying drugs made by the subsidiary in France and sold into the U.S. market

All of these GCPs have value for the parent company and to maximize that value, the parent company should view these GCPs as enterprise resources and manage them that way.  Number allocation based on these GCPs should be managed centrally using a strategy that is designed to maximize the benefit to the whole organization rather than to silos within the company.

WHAT IS A GCP USED FOR?

A GS1 Company Prefix is at the core of “The GS1 System”, a set of standards used globally for identification of products, services, assets, relationships and even documents.  These entities are identified in the GS1 System at the class level or at the serialized unit level through numeric “keys”.  All GS1 keys use the GCP as their foundation so that each key is uniquely specific to the owner of the GCP on a global basis.  Once a company is given the right to use a GCP they are free to define any key using that GCP without fear that they will clash with anyone else’s key, and without additional cost.  The remainder of each key is used to hold additional information to identify the target entity.  Refer to the GS1 General Specifications for full details (check with your GS1 M.O. or just search for a downloadable copy on the internet).

The GCP can vary between six and ten digits in length in the U.S. and may have a different variation depending on the M.O. making the assignment.  The following diagram is just a generalized depiction of that.

Here is a list of GS1 keys that are based on the GCP:

• GTIN (Global Trade Item Number) in 8, 12, 13 and 14 digit flavors, and the serial numbers associated with them when forming an SGTIN;
• GLN (Global Location Number) 13 digits;
• SSCC (Serial Shipping Container Code) 18 digits;
• GRAI (Global Returnable Asset Identifier) 14 digits, first digit is always a zero plus optional serial number up to 16 additional characters;
• GIAI (Global Individual Asset Identifier) up to 30 characters;
• GSRN (Global Service Relation Number) 18 digits;
• GDTI (Global Document Type Identifier) 13 digits plus optional serial number up to 17 additional digits;
• GINC (Global Identification Number for Consignment) up to 30 characters;
• GSIN (Global Shipment Identification Number) 17 digits.

Each type of GS1 key includes a numeric value that is combined with the GCP to form a specific instance of the key.  It is the assignment of these numeric values that must be managed in some way.  The total length of the key minus the length of the GCP determines how many digits are available to the owner to assign specific instances of the key.  These digits represent the “key space” for a given key.  The shorter the GCP, the larger the key spaces of each key type will be.

(NOTE:  As George Wright rightly points out in his comment below my off-hand formula for calculating the available digits in the key space leaves out the check digit in some keys as well as certain other individual digits in other keys.  Please refer to the GS1 General Specifications for the full calculation for each individual key type.)

CENTRAL MANAGEMENT OF GCPs AND GS1 KEYS

Companies of any size will benefit by managing all of their GCPs and GS1 keys in a single location and perhaps through a single database and application.  It enables the enforcement of a single corporate strategy for number assignment within each key space and ensures that duplicate values will not be generated and number ranges will not be wasted.

It is not necessary for the central GCP management authority to assign every single value for all of the keys to maintain control.  This is particularly true for high frequency assignment keys.  For example, the responsibility for assigning specific SSCC values may be delegated to remote systems.  Even then, the remote systems should be designed to acquire number ranges from the central system so that the enterprise strategy is maintained.  Once a number range is acquired by the remote system it can perform its own assignment of the SSCCs within the allocated range as necessary.  When it gets close to exhausting the current range of values it can request the next range from the central authority.  For small companies this could be done manually, but for mid to large companies, this should be automated.

Keys that are assigned at low frequencies, like GLN—which would only need a new assignment when a new location is established—or GTIN—which would only need a new assignment when a new product or new variation is introduced—could be done manually even in larger companies.  Whether manual or automated, central management of lower frequency keys is even more important than the high frequency keys in my view, to ensure that used numbers are properly kept track of.

Central management of all GCPs owned by a company allows the central authority to minimize the need to acquire new GCPs by maximizing those that are already under their control.  A central authority can ensure that the key spaces of each key are fully utilized before either reusing previous values (do so very carefully) or acquiring a new GCP.  In most cases these decisions should not be left up to remote business units or you might find that the enterprise possesses many more GCPs than are actually necessary.

Central management of serial numbers associated with GTINs–to form GTIN plus serial number, or SGTINs–should also be controlled centrally whether done individually or through number ranges.  This allows the enterprise to make use of a single serial number assignment strategy, including some form of randomization, if desired, like the kind offered by RxTrace advertiser Kezzler.

The introduction of a new GCP through a central authority can be much cleaner and much more efficient than if done otherwise.  Remote systems should not make any assumptions about the GCPs within the GS1 keys they are provided, whether individually or within ranges.  That way the central GCP authority can introduce the use of new GCPs at any time necessary.

Very large enterprises that make heavy use of GS1 keys might have a group that is dedicated to managing their GCPs and GS1 keys, but most companies will be able to make it fit within a group that is responsible for other data-related activities.  Good candidates for the GCP management responsibility within an enterprise are the Master Data Management (MDM) group or some other existing data management group.

Regardless what group the responsibility ultimately falls, central management of your GCPs and associated GS1 keys is a good idea.  If your company does not currently have central management, I suggest you start asking questions to find out:

• How many GCPs does your company control?
• Who manages the key spaces of each one?
• Does anyone know exactly which key values have been consumed within each key space of each GCP?
• Who has the authority to acquire a new GCP and for what reasons?

You might be surprised at what you find.

Dirk.

It has been almost two years since I published “RFID is DEAD…at Unit-Level in Pharma” and we are approaching a pivotal decision by the Food and Drug Administration (FDA) that will determine whether or not RFID will be acceptable for identifying drugs in the U.S. supply chain.  Last Thursday was the scheduled final closing of the recent request for comment issued by the FDA formally known as “Bar Code Technologies for Drugs and Biological Products; Retrospective Review Under Executive Order 13563; Request for Comments, 76 Fed. Reg. 66,235” (Oct. 26, 2011) [Docket No. FDA-2011-N-0719].

The closing of this request for comment (RFC) means that it is now time for the FDA to figure out what they might do with the original questions.  That is, should they change the requirement for all packages of prescription drugs and many over-the-counter (OTC) drugs in the U.S. to contain the National Drug Code (NDC) encoded into a linear barcode?  And if so, what should they replace it with?  The RFC doesn’t give any hints about how far they might go and simply asks a series of questions of the industry and interested parties, letting the respondents propose whatever they think the agency should do.

I have spent my Sunday afternoon reading (OK, in some instances, skimming) through all of the responses.  They are available for anyone to read (or skim) at http://www.regulations.gov (search for FDA-2011-N-0719).  Considering that the input received from this RFC may influence the FDA’s decision about what to replace the linear barcode requirement with, I think the responses are particularly pertinent to RxTrace readers.

GENERAL THEMES

My reading has taken so long that I no longer have enough time left over to cover the responses in detail (consider yourself lucky), but there are a number of general themes that emerged from them in aggregate.

“Linear barcodes are so 2004″
Nearly all of the responses that answered the FDA’s specific questions indicated that it is time to move away from the use of linear barcodes.  I think all of the responses were submitted prior to the publication of my essay “Why NOW Is The Time To Move Away From Linear Barcodes” so to them I was simply restating the obvious.

“Don’t mess with ISBT-128“
The members of the blood, tissue and organ supply chain were well represented in the responses with comments that were very similar, like this one from Pat Distler of the ICCBBA.

“…we strongly encourage FDA NOT to require NDC be bar coded on licensed products requiring biovigilance (e.g., cells, tissue, tissue derived products, organs for transplant, medical devices for which donor to recipient traceability is needed).  Instead, FDA should expand the guidance given in Securing the Drug Supply Chain-Standardized Numerical Identification for Drug Packages to include all biologics such that the SNI for these products would be the unique identification number created for each package under ISBT 128 or other recognized standards.”

“Don’t restrict our choices”
Many of the respondents do not want the FDA to simply replace the word “linear” with some other specific symbology or technology.  Here is a comment that is representative of this theme:

“…we do not believe FDA should restrict the type of machine readable technology within the regulation.  The regulation should only state that machine readable information needed for traceability (unique identifier and product code) should be required.”

I was pretty surprised at how many respondents said that they wanted manufacturers to each decide which carrier technology to encode their NDC and other data in.  This is exactly counter to my thoughts as expressed in the essay “Should Regulations Dictate Technology?” where I argued,

“It is the movement by the industry in unison that is the real benefit of carefully mandating a single technology for identifying drugs in the supply chain.  It is the key to maintaining and even improving supply chain efficiencies.”

My concern is that, if every manufacturer can use whatever machine readable technology they think is best, then within a short time we will see every conceivable carrier technology in use within the supply chain at the same time.  Every barcode symbology and every flavor of RFID—and there are some other pretty weird technologies out there.  I think that’s a recipe for the degradation of interoperability.

Fortunately some of the responses in this category are simply concerned about the ease with which the FDA could change their regulations and so they didn’t think a full regulation should identify a specific technology.  They think the FDA should issue less formal guidance documents to specify the acceptable technologies.

“The type of machine readable information (linear bar code, 2-D bar code, RFID, etc.) should be provided only in easily-changed guidance documents.”

DataMatrix…DataMatrix…DataMatrix…DataMatrix…
For those responses that weren’t in the “Don’t restrict our choices” camp (and even including some of those) the most common recommendation was to replace “linear” with “DataMatrix”, one even providing additional technical detail, “DataMatrix  ECC 200”.  A representative example,

“GEHC recommends use of the GS1 Datamatrix as an alternative to the linear bar code.”

“Let GS1 decide”
Quite a few respondents recommended that the FDA turn over the choice of technology variously to GS1, GS1 US, GS1 Healthcare, or “the user community”, which is a euphemism for “companies who are members of GS1”.  John Robert of GS1 US explains it this way.

“It is also recommended that the FDA should select one standards system; specifically, the GS1 System.”

…

“In order to accommodate a variety of environments and applications, the GS1 System supports six barcodes that industry partners can work with to support their supply chain needs.  In addition, the GS1 System also supports two RFID data carriers…”

…

“Thus, it is recommended that the FDA not specify a proprietary data carrier, or any particular type of data carrier or technology.  Instead, it is recommended that the FDA only specify automatic identification standards that can be used.  Selection of data carriers must consider the constraints of the application.  The best way to determine the right data carrier for the product/package is to embrace a user driven, global process where data carrier selections are based on the operational, regulatory, business and practical considerations of the trading partners and the drugs themselves.  Therefore, the Bar Code Rule should not be based on a specific technology or a specific symbology.  Rather, it is only necessary to embrace unique identification based on global standards, and leave the selection of symbology and technology to the user community.”

“Require Lot and Expiration Date”
Quite a few responses note that the new FDA carrier technology, whatever it turns out to be, will be able to accommodate additional data with ease and that leads them to support the requirement that the drug’s Lot and Expiration Date be included along with its NDC.  Typical of these:

“PhRMA believes that both the product lot number and the product expiration date should be included in the barcode, along with the NDC number.  This information is included in the 2D barcodes that manufacturers have begun to adopt and FDA’s rules should allow for the inclusion of these data elements in the product bar code.  The inclusion of this information should be optional until 2016 and required after 2016.”

HEY, WHAT ABOUT RFID?

I know, I know, I promised you something about RFID, so here it is.  Quite a few of the responses that didn’t want the industry to be restricted explicitly listed linear barcodes, 2D barcodes and RFID as examples of technologies that should be acceptable.  Many of those would include any future technology so as not to stifle innovation (I shudder to think how many different kinds of readers we would all need to invest in!).

The only response that pushed hard for RFID over everything else was submitted by my old friend Randy Stigall of UPM RFID, an RFID tag manufacturer.  Randy’s response was an essay called “Powerful drivers for RFID pharmaceutical serialization”, apparently a reprint of his article from a pharmaceutical magazine.  In it he makes the case for the adoption of the latest High Frequency (HF) RFID standard from the International Organization for Standardization (ISO) and GS1, ISO 18000-3m3.  It is interesting reading, but I don’t think it’s likely to sway the FDA to replace “linear” with “ISO 18000-3m3 HF RFID” (sorry Randy…hey, give me a call sometime).

On the other hand, if either the “Don’t restrict our choices” or “Let GS1 decide” arguments prevail and one of them is adopted by the FDA, maybe one or two drugs identified by ISO 18000-3m3 HF RFID will show up in your drug shipments sometime soon.  What’s that?  Your linear/2D/UHF RFID combo device can’t read ISO 18000-3m3 HF RFID?  Quick.  Time for an upgrade!

Didn’t submit a comment in response to the FDA RFC?  That’s all right.  Submit one to RxTrace below.

Dirk.

In recent essays I have covered the “Anatomy of an NDC”, the “Anatomy of a GTIN” and the “Updated HDMA Bar Code Guidance: A Must Read“.  Now let’s put them all together.  Why would we need to do that?  Because the U.S. FDA requires many Over-The-Counter (OTC) and all prescription drugs marketed in the United States to have their National Drug Code (NDC) presented in the form of a linear barcode on the package.  Pure and simple.  To do that in a way that your trading partners can understand—that is, to do it interoperably—you need to follow a standard.  You have two realistic choices for standard approaches to this problem:  HIBCC or GS1.

The use of HIBCC standards is fairly common in the U.S. medical surgical devices supply chain but in the pharmaceutical supply chain it is very rare.  Most companies choose GS1’s barcode standards so that’s all I’m going to focus on in this essay.  If you want more information about how to do this with a HIBCC barcode find it here.

OVER-THE-COUNTER DRUGS:  GTIN-12

If your drug is sold over the counter (OTC), like aspirin and cold medications, the barcode on your packages will need to be scanned at point of sale (POS) terminals in the same way that any other consumer good is.  For that reason you need to put your National Drug Code (NDC) into a Universal Product Code (UPC) barcode in the United States.  A UPC-A barcode symbol contains a GS1 GTIN-12 data structure.  Here is what you need to do to convert your NDC into a GS1 GTIN-12:

1. Register your FDA Labeler Code with GS1 US who will convert it into a GS1 Company Prefix (GCP) and grant you the right to use it
   Recall from my previous essays that your FDA Labeler Code is either 4 or 5 digits long and a GCP can be anywhere from 6 to 10 digits depending on the fee you pay GS1 US when you register it.  In the case of FDA-regulated pharmaceuticals GS1 US will register a 4-digit FDA Labeler Code as a 6-digit GCP and a 5-digit FDA Labeler Code as a 7-digit GCP.  The reason is that they need to synchronize the length of the Item Reference portion of the resulting GTINs with the combined length of the Product Code and Package Size fields of your NDC.  This is to ensure that you are able to generate valid GTIN-based barcodes for every possible NDC that your Labeler Code enables you to generate.  You only need to register your FDA Labeler Code with GS1 US once as long as you keep up with the annual subscription fees so for subsequent drugs that use a Labeler Code that is already registered you can skip this step.  If you have multiple FDA Labeler Codes you need to register each one with GS1 US once.
   
   GS1 US has reserved GCPs that start with “03″ for owners of FDA Labeler Codes as shown in the following table.
   

   Click images to enlarge

2. From your new GS1 Company Prefix construct your U.P.C. Company Prefix
   Ah ha!  This is an esoteric step.  It is necessary because of the way GS1 merged the formerly North American-only Uniform Code Council’s (UCC) Universal Product Code (UPC) company prefixes with the European Article Numbering Association’s (EAN) European Article Number (EAN) company prefixes and made the whole combined scheme suitable for global company prefixes and yet retained backward compatibility with the UPC and EAN.  But you don’t have to follow any of that.  Here’s what you do.
   
   You take the GCP that GS1 US assigned you and you strip off the leftmost digit.  That digit is always going to end up being a zero because we are dealing with an FDA regulated pharmaceutical and GS1 US will make sure that it is a zero on your behalf.  The remaining digits make up your new U.P.C. Company Prefix, usable only for generating UPC-A barcodes  and a few other less common things (see the GS1 General Specification for what else you can do with a U.P.C. Company Prefix).  For an NDC that has a 4-digit Labeler Code your U.P.C. Company Prefix will now start with a “3” and it will be 5 total digits long.  For an NDC that has a 5-digit Labeler Code your U.P.C. Company Prefix will now start with a “3” and it will be 6 total digits long as shown below.
   

   Click images to enlarge

3. Combine your U.P.C. Company Prefix with the Product Code and Package Size fields from your NDC
   For an NDC that has a 4-digit Labeler Code your Product Code and Package Size fields will be a total of 6 digits long.  Combine them with the GS1 U.P.C Company Prefix by placing them to the right of the prefix.  For an NDC that has a 5-digit Labeler Code your Product Code and Package Size fields will be a total of 5 digits long.  Combine them with the GS1 U.P.C. Company Prefix by placing them to the right of the prefix.  You should now have a total of 11 digits regardless of the length of your Labeler Code as shown in the table below.
   

   Click images to enlarge

4. Calculate the Check Digit and add it to complete your GTIN-12
   GS1 provides an algorithm to calculate the Check Digit in section 7.2.7 of the GS1 General Specification.  They also provide a handy calculator at this webpage(although where they say to enter the “Item Reference”, they really mean for you to enter the full prefix and item reference together).  Add check digit to the right of the code constructed in step 3.  You should now have a 12-digit code as shown below.  This is the GTIN-12 that can be encoded into a UPC-A barcode and printed on your product.
   

   Click images to enlarge

If you look closely at the table above you may see a short-cut that would get you directly to your GTIN-12.  All you need to do is take your 10-digit NDC and put a “3” in front of it and put a calculated check digit at the end as shown in the following table.

Click on images to enlarge

It is true that you can get there this way but then you might be tempted to skip step #1 and not obtain your official GCP.  As I understand it, since GS1 owns a copyright on the UPC family of barcode symbologies they could make a claim against your company if you encode your NDC into the copyrighted UPC-A symbology without first registering your FDA Labeler Code with them and paying whatever fee they place on that.  Talk to GS1 US to get the full story for your particular situation.  On the other hand, if you have already registered your Labeler Code with GS1 US then this short-cut should always produce your GTIN-12 for subsequent products that share the same FDA Labeler Code.

PRESCRIPTION DRUGS:  GTIN-14

Any drug distributed in the U.S. that is regulated by the FDA as a prescription drug must be dispensed by a registered pharmacist.  In that case it will not be scanned at a retail POS station.  For that reason you do not need to encode your NDC within a GTIN-12 but should encode it into a full GTIN-14.  GTIN-14s should also be used on all case labels whether OTC or prescription (see the HDMA Bar Code Guidance for details).  You can render a GS1 GTIN-14 identifier into a GS1-128, GS1 DataMatrix, or GS1 DataBar symbology depending on the application.

Here is what you need to do to properly convert your NDC into a GS1 GTIN-14 data structure:

1. Register your FDA Labeler Code with GS1 US who will convert it into a GS1 Company Prefix (GCP) and grant you the right to use it
   This is the same as step #1 for GTIN-12 above.
   
   
2. Combine your GS1 Company Prefix with the Product Code and Package Size fields from your NDC
   For an NDC that has a 4-digit Labeler Code your Product Code and Package Size fields will be a total of 6 digits long.  Combine them with the GS1 Company Prefix by placing them to the right of the prefix.  For an NDC that has a 5-digit Labeler Code your Product Code and Package Size fields will be a total of 5 digits long.  Combine them with the GS1 Company Prefix by placing them to the right of the prefix.
   
   
3. Add your Indicator Digit
   Next you need to add the single digit “Indicator digit” to the left of the GS1 Company Prefix.  Refer to my previous essay, “Anatomy of a GTIN” to learn what this digit is for.  For a unit of use package, use the value “0″.  You should now have a total of 13 digits regardless of the length of your Labeler Code.
   
   
4. Calculate the Check Digit and add it to complete your GTIN-14
   GS1 provides an algorithm to calculate the Check Digit in section 7.2.7 of the GS1 General Specification.  They also provide a handy calculator at this webpage.  Add check digit to the right of the code constructed in step 2.  You should now have a 14-digit code.  This is the GTIN-14 that can be encoded into a GS1 Code-128, GS1 DataMatrix, or DataBar barcode and printed on your product or case.  (NOTE:  DataBar should only be used on packages that are too small to accept one of the other symbologies.  See the HDMA Bar Code Guidelines for details.)

Finally, if you have already registered your Labeler Code with GS1 US you can use the following short-cut to construct your subsequent GTIN-14s.

Click image to enlarge

The following figure summarizes the contents of all forms of the NDC for both GTIN-12 and GTIN-14 data structures.

Click images to enlarge

IMPLICATIONS

There is an important implication stemming from the use of GS1 identifiers and barcodes to encode and render your NDC that I think needs to be explained.  This applies to any company that already possesses a GCP that does not match their FDA Labeler Code.  I can think of two ways that this might happen:

1. Any company in the U.S. that distributes non-drug products and already obtained a GCP from GS1 US for those products,
2. Any drug manufacturer that is based outside of the United States and that already possesses a GCP that was issued by their local, non-U.S. GS1 Member Organization.

Neither of these types of GCP’s can be used to encode an NDC for distribution within the U.S.  That’s because these GCPs do not match your FDA issued Labeler Code.  Only GS1 US, the U.S.-based GS1 Member Organization, can issue you a GCP that is properly based on your Labeler Code.  So these companies should contact GS1 US to register their Labeler Code, whether the company is based in the U.S. or not.

Systems and their associated databases should always be designed to accommodate the full GTIN-14 even when the application may seem to only need to deal with GTIN-12′s.  See GS1′s position paper on this topic for more explanation.

There are a few more “Anatomy of…” essays I want to write including the FDA’s Standardized Numeric Identifier (SNI), and GS-128 in the U.S. Pharma supply chain.  Watch for those essays in the near future.

Dirk.

2012 is the year of the GTIN in the U.S. healthcare supply chains as christened by the largest hospital group purchasing organizations (GPOs) in their so-called “Sunrise 2012″ program.  They have asked all of their suppliers to switch from proprietary product codes to GS1’s Global Trade Item Number (GTIN) standard in catalogs, B2B communications and shipment labeling by the end of this year.  They did the same thing with GS1’s Global Location Number (GLN) back in 2010 (“Sunrise 2010″) but so far it appears to have had only a small (but still growing) impact.

The GTIN can be a mysterious concept.  I received an email recently from a sales person who wanted to know what this “G-ten” thing was that her customer kept claiming was so important to her future business with them.  I’ve also sometimes had difficulty convincing people that GTIN adoption is important.  “We don’t need another product identifier.  We already have the NDC!”

I hope to pull back the veil just a little bit and explain not only the anatomy of the GTIN but also why it is so important to all supply chains in all regions of the world.

WHAT EXACTLY IS A GTIN?

GS1 explains the GTIN this way:

“As the name implies, the GTIN helps automate the trading process – basically buying and selling.  GTINs are therefore assigned to any item (product or service) that may be priced, or ordered, or invoiced at any point in any supply chain.  The GTIN is then used to retrieve pre-defined information about the item.  The key benefit is that information about the item can be retrieved about the product from the GTIN whether it is read in a GS1 BarCodes symbol, exchanged via a GS1 eCom message or accessed from the Global Data Synchronisation Network.”

Hmmm…Let me try.  First, a “Trade Item” is any product or service that may be manufactured, priced, advertised, bought, sold, traded, invoiced, returned or consumed within a commercial supply chain.  GTIN (Global Trade Item Number) is a GS1 standard that defines the structure and usage rules for a numeric identifier that can be assigned to a very specific, idealized description of a “trade item” and which can then be used in any part of the world to refer to instances of trade items that conform to that description.

For another attempt at a definition, see the one on Wikipedia here.

In everyday usage “a GTIN” is the number that is encoded into the product barcodes found on pretty much every product you can find in any store.  In the U.S. you know it as the UPC, or Universal Product Code, a 12-digit number (and technically known as a GTIN-12).  In the E.U. you know it as the EAN, or European Article Number, a 13-digit number (and technically known as a GTIN-13).  The GTIN-12 and GTIN-13 are “retail” GTINs.  That is, these are the GTINs placed on products that are typically sold through a retail Point of Sale (POS) station (a store checkout counter).  This includes most over the counter (OTC), non-prescription drugs.

Today, nearly all OTC drugs and many prescription drugs in the U.S. supply chain are marked with a National Drug Code (NDC) or a Universal Product Code (U.P.C.) that is encoded in a GTIN-12 data structure and rendered on the package in a UPC-A barcode.  Non-retail products like those that are typically sold only B2B (business to business) (GS1 refers to these as “Trade Items Intended for General Distribution Scanning Only”)—including prescription pharmaceuticals—should be assigned a 14-digit GTIN (technically known as a GTIN-14).

You may yawn, but this is powerful stuff if you can get everyone on the bandwagon.  The GPOs in the U.S. and GS1 plan to do just that.

The most important aspect of the GTIN standard is that when one is properly assigned to a given product or service it is globally unique.  That means that no other product or service anywhere in the world can ever be assigned that same GTIN so that number can be used anywhere and everywhere to refer to that specific type of product or service.  This eliminates product code ambiguity globally.

Another important feature is that the GTIN standard is applied in the same way regardless of product type, service type or supply chain.  The same rules apply to all GTIN identifiers.  These rules are defined in GS1’s General Specification—the specification of “The GS1 System”, of which GTIN is just one part.  See also “GS1 GTIN Allocation Rules for Healthcare” for some of these rules in a healthcare context.  (For a great non-technical explanation of “The GS1 System” of standards, check out this great PDF:  “The Value and Benefits of the GS1 System of Standards”.)

ANATOMY OF A GTIN-14

I mentioned above that a GTIN can take form in 12, 13 or 14 digits (it can also take the form of an 8-digit value but that’s very rare in healthcare), but since my focus is primarily in the B2B healthcare supply chains I’m only going to concentrate on the 14-digit form in this essay.  This is the only form that will fit into barcodes that make use of GS1 Application Identifiers (AI) (like GS1-128 linear barcodes and GS1 DataMatrix 2D barcodes) although the other forms can always be converted into the 14-digit form (by padding with zero[s] on the left).  Note that OTC drugs at the unit-level cannot make use of the GTIN-14 structure, AIs or the barcodes that carry them because they need to be scanned at POS.

There are four components that make up a GTIN-14 and they appear in this order:

• Indicator Digit
  This digit only appears in the GTIN-14 and is primarily used to indicate standard groupings (inner pack, case, pallet, etc.) of packages of the same GTIN using values 1 through 9.  A zero indicates that the GTIN is representing a single unit.  For products where the actual units sold can be a variable measure (weight, size, volume, etc.) the indicator digit should be set to 9.  Indicator values 1 through 8 have no specific standard meaning other than that they indicate a grouping.  That is, there are no standard groupings that values 1 through 8 may indicate so you can’t assume any particular value means an inner pack, a case, a pallet or anything else.  Each company is free to choose any of these values to indicate any grouping they wish.
  
  
• GS1 Company Prefix (GCP)
  This is the variable length number that is assigned by the local GS1 Member Organization (MO) to the company that manufactures, packages or repackages the product that the GTIN represents.  This is the number that those companies must apply to GS1 for assignment.  In the U.S. the GCP ranges in length between 6 and 10 digits and the length partially determines its cost.  Shorter company prefixes cost more than longer ones (see Item Reference below for why this is so).
  
  Pharmaceutical companies who already possess an FDA Labeler Code (see my previous essay, “Anatomy Of The National Drug Code” for more on this) just need to register that code with GS1 US (the local GS1 MO in the United States) to obtain a license to use that same code as the basis for their GCP within the context of GS1’s copyrighted barcode, RFID, EDI, pedigree and track & trace standards.
  
  The GS1 Company Prefix is itself composed of a 1 to 3 digit GS1 Prefix which is assigned by the GS1 Global Office to each GS1 MO to ensure global uniqueness of all GCP-based GS1 keys (GS1 keys include GTIN, GLN, SSCC, GRAI, any EPC, GSRN, GIAI, GDTI, GSIN, etc.).  This prefix is sometimes incorrectly referred to as a “country code” although because MOs are fairly country-specific this is not too far off.  The remainder of the GCP—known as a Company Number—is assigned by the Local MO.  See the GS1 General Specification for more details.
  
  When a company is assigned a GCP by GS1 they are granted exclusive rights to use that prefix to construct any of the GS1 keys (see the list in the paragraph above) and use them in any way they see fit as long as it is within the rules established in the GS1 General Specification.  GS1 keys generated by the owner of the GCP do not need to be authorized, approved or registered with GS1.  There is no additional cost to generate new GS1 keys once a company obtains a GCP.
  
  GCPs are a company asset that should be addressed in any merger or divestiture strategy (see this topic in the GS1 General Specification).  GCP usage within a given company should ideally be controlled at a single point within an organization.  This generally isn’t an issue for smaller companies but multinational corporations should ensure that they have a strategy for centrally assigning and distributing GCP-based GS1 keys to their operations to ensure uniqueness and to ensure that the GCP resource is used to its maximum potential.
  
  Companies may obtain multiple GCPs from their local GS1 MO if they use up the available reference values in one or more GS1 keys.  They may also obtain additional GCPs (partly “used”) as the result of a merger with another company.
  
  Neither GS1 nor the MOs police adherence to any of their standards, but they carefully control the assignment of GCPs to always maintain global uniqueness.  As long as the GCP assignments are all globally unique, all of the keys generated by the owners of all GCPs will also be globally unique.  This is a very important design feature of the entire GS1 System.
  
  
• Item Reference
  The Item Reference is a variable length number that must be chosen by the owner of the GS1 Company Prefix and assigned to the specific description of a single product class.  This specific description must remain unchanged for the life of the GTIN (see the GS1 General Specifications for details and exceptions).  The combination of the owner’s GCP and the Item Reference must be exactly equal to 12 digits.  Since the length of the GCP is determined when it is obtained from the local MO, the length of the Item Reference must take up the remainder of the 12 digit space.
  
  For example, if company A obtains a 6-digit GCP, the Item Reference field within their GTIN-14′s must be 6 digits long (12 – 6 = 6).  If company B obtains a 10-digit GCP, their GTIN-14 Item References must be only 2 digits long (12 – 10 = 2).  From these two examples you can see that company A can identify up to 1,000,000 unique products or services but company B can only identify 100.
  
  There is a comparable limitation in the other GS1 keys.  Shorter GCPs result in more digit space available in the reference portion of the key which results in vastly more usable unique numbers (each extra digit represents an order of magnitude more unique values the owner can assign).  This is why GS1 charges more for the shorter GCPs than they do for longer ones and this provides a measure of affordability to smaller companies who will likely never need more than a small number of unique GTINs or other keys.
  
  
• Check Digit
  The Check Digit is a single digit that is mathematically calculated based on the contents of all of the other digits in the GTIN-14.  The purpose of the Check Digit is to help barcode readers and applications detect data entry errors.  See Section 7.10 of the GS1 General Specification for the algorithm.

EXAMPLE GTIN

Here is an example of a GTIN-14 that I found on an inner-pack of Epinephrine injectors.

Click image to enlarge. Image Copyright RxTrace 2012.

An “inner-pack” is a grouping of trade items and so we see the Indicator Digit is set to “1″, a valid value for a grouping.  We can’t tell by looking at this example exactly how long the GCP is because it could be anywhere from 6 digits to 10 digits long.  Fortunately GS1 provides a service they call Global Electronic Party Information Registry, or GEPIR.  If we select “Search by GTIN”, enter ’10304094921348′ and click “Search”, we are told that this GTIN contains a 6-digit GCP of ’030409′ and it is registered to Hospira, Inc. in Lake Forest, Illinois.  Now we know that the Item Reference that Hospira happened to choose for this GTIN must be ’492134′.  The Check Digit is calculated based on all of the previous digits as “8″.

This particular inner-pack contained about 10 or 12 unit-level packages that were shrink-wrapped together and labeled with the GTIN-14 above.  Each of the units contained a barcode with the unit-level GTIN-14 encoded in it.  It was exactly the same GTIN as the inner-pack except for the Indicator Digit, which was correctly set to zero, and the check digit which changed because of the change in the Indicator Digit.  These were unit dose injectors.  There are probably about 4 inner-packs per casepack but I didn’t note that information.  The case GTIN would be exactly the same as the inner-pack and units except for the Indicator Digit which would have been been a value in the range of 2 to 8 to reflect that it is a standard grouping that is different than the inner-pack.

Normally we don’t need to deconstruct GTINs like this.  In fact the whole point of a GTIN is to use it as a single whole identifier and not to break it down into its constituent parts like we have done here but I wanted to show you how this one was intelligently constructed by Hospira, the owner of this particular GCP.

BENEFITS OF THE GTIN

The benefits of GTIN adoption by a supply chain are different between manufacturers and non-manufacturers (distributors, pharmacies and retailers).

Manufacturers gain because they can potentially use the same standard product/service identifier in multiple markets/countries.  Well, as long as the packaging doesn’t vary (same language, etc.) and there aren’t any regulatory reasons for using a different identifier (national numbering like the U.S FDA NDC, different units for the unit of measure, etc.).  Even when a different identifier is necessary for different markets/countries the manufacturer benefits from the use of a standardized identifier because modern Manufacturing Execution Systems (MES), Warehouse Management Systems (WMS),  Electronic Data Interchange (EDI) systems and Enterprise Resource Planning (ERP) systems should come with full GS1 System support built in (admittedly not all do yet).  This includes enforcement of many of the GS1 rules for dealing with GTINs and the other pertinent GCP-based identifiers.

Like manufacturers, non-manufacturers in the supply chain make use of WMS, EDI and ERP systems in addition to pharmacy management systems and  Hospital Materials Management Inventory Systems (HMMIS) that ought to have standardized GS1 System support built in.  These companies also benefit because they can trust that GTINs are globally unique and all product identifiers used by all of their suppliers refer to the same product or service and those identifiers are constructed using the same format.  This allows them to eliminate their own internal product codes for each manufacturer’s products and services, simplifying inventory management, sales, purchasing, order fulfillment, shipping, receiving and dispensing and thus reducing errors that generate waste and in the healthcare supply chain can cause injury or even death.  This is why the GPOs are so hot to make 2012 the year of the GTIN.

ADOPTION OF THE GTIN

Manufacturers of products or services can decide to unilaterally adopt the GS1 GTIN standard for all of their products and they can reap some small internal benefits from that decision as I’ve outlined above.  That may not offer enough of a gain to offset the cost of conversion from proprietary product identifiers.  The problem is, for the downstream trading partners to benefit from GTIN use, more than just one manufacturer has to switch to GTINs.  In fact, the benefits don’t start accruing to those companies until a significant number of manufacturers switch to GTINs, and until all manufacturers in a given supply chain switch to them the benefits do not reach their maximum potential.  For this reason, GTINs should be adopted by a supply chain as a whole and not just one company here and there.

How do you trigger a switch within an entire supply chain like that?  The GPOs may have it figured out.  Like Walmart in the fast-moving consumer goods (FMCG) supply chain and the big automakers in their supply chain, they have to start dictating the switch and they have to be hard-nosed about it.  Can the GPOs fill the role of the “800-pound gorilla” like Walmart and the automakers?  We’ll see.

There are some encouraging signs and some discouraging signs in the recently released results of a survey in a document called “GS1 Data Standards Adoption Survey, Progress toward Global Trade Item Numbers (GTINs), December 2011” conducted by the University of Arkansas Center for Innovation in Healthcare Logistics (CIHL) on behalf of the Healthcare Supply Chain Association (HSCA) (the industry association of GPOs, formerly HIGPA) and the Healthcare Industry Supply Chain Institute (HISCI).  I’ll have more to say about this paper and the results it documents in a future essay.

I’ll stop here for now.  Watch for future related essays on “Depicting an NDC Within a GTIN”, and “Anatomy of an SNI”.

I am going to attend the 2012 National Pharmacy Forum in Tampa on February 9th.  The full conference runs from the 8th through 10th and is co-hosted by HCSA and HISCI.  If you run into me there please introduce yourself and tell me what you like and don’t like about RxTrace.

Dirk.

The U.S. Food and Drug Administration (FDA) created the concept of the National Drug Code (NDC) in 1969 to “…provide an identification system in computer language to permit automated processing of drug data by Government agencies, drug manufacturers and distributors, hospitals, and insurance companies” (from 34 FR 11157, July 2, 1969).  (I can’t find a copy online of the original Federal Register article from 1969 so I’m relying on a more recent article that references it.)   Those of us in the U.S. pharma supply chain make use of NDC’s every day, but very few of us know the history of their development, exactly how the numbers are composed and what they mean.  I’ll try to explain all of that and provide sources for further reading.

HISTORY OF THE NDC

The NDC was initially a voluntary identifier (see references at the end of this essay).  We all know how that would have turned out (for more on that thought, see my recent essay “Should Regulations Dictate Technology?“) so in 1972 the FDA made the NDC mandatory for all prescription and over-the-counter (OTC) drugs.  Manufacturers were required to obtain a “Labeler Code” from the FDA, construct their NDC’s using that code as the base and print the NDC number on drug packages.  Barcodes were not required by the FDA back then.

From the quote in the first paragraph above you can see that the FDA intended the NDC to be used among the full spectrum of users who needed to unambiguously refer to specific drugs.  I can’t imagine how inefficient it must have been to refer to a specific form, size and concentration of a particular drug in every step between manufacturer, patient and insurer before the advent of the NDC.  Even from the very start the FDA intended the NDC to help with automation using computers.  Computer automation leads to greater efficiencies and much greater data accuracy–just what was needed for the drug industry and supply chain to grow in the coming decades.

The FDA recognized in the early 1970′s the automation value of encoding the NDC into barcodes, but as I said, they didn’t require them.   However, barcodes were making a big splash in the grocery industry and soon after in the consumer products goods industry around that time because of the great gains experienced in checkout efficiency and inventory control.  The Uniform Grocery Code Council (UGCC) introduced the 12-digit Universal Product Code (UPC) identifier and barcode symbology in 1974 and it quickly became the standard for all products sold at checkout counters.  Chain stores of all kinds started putting maximum pressure on manufacturers to put a UPC barcode on every product they sold.

This led to an interesting collision of mandates.  The FDA had already mandated that OTC drugs be identified by their NDC.  The UGCC mandated that the “Company Prefix” portion of the Universal Product Code that was encoded in UPC barcodes be assigned by the UGCC.  Since OTC drugs were one of the products that were being sold by chain stores, pressure was put on the UGCC to find a way to accommodate the 10-digit NDC within the 12-digit UPC.

UGCC technical experts quickly came up with a way to do it.  They came up with the scheme of pre-pending the NDC with the digit ’3′ and then adding the standard UPC checksum at the end.  The UGCC had to commit to reserving all UPC’s with a ’3′ as the first digit for drug companies and they agreed to reserve the Company Prefixes for drug companies so that they matched the FDA’s Labeler Code.  OTC drug manufacturers now had a way to satisfy both mandates and many years later that approach continued to be used as manufacturers started to apply barcodes to non-OTC drug packages.

Around that time the UGCC became the Uniform Product Code Council (UPCC), then the Uniform Code Council (UCC) in 1984, and finally became GS1 U.S. in 2005.  All along the organization has been a privately held, non-profit, tax-exempt corporation.

While the printing of the human readable NDC on drug packages was mandatory the printing of a barcode on drugs was voluntary until only relatively recently.  The FDA published a final rule  in 2004 that mandated all drug packages have a linear barcode printed on them starting in 2006.  By 2004 roughly 90% of drug packages in the supply chain already had linear barcodes on them voluntarily.  It seems odd that it took the FDA so long to mandate such a valuable automation element when it seems like it could have mandated it much earlier with little justifiable complaint from the industry.  The final rule document contains a significant amount of discussion, explanation and documentation about the benefits of barcodes on drug packages, particularly around the benefits to patient safety.

THE ANATOMY OF THE NDC

The NDC is composed of three semi-fixed-length data fields:

• FDA Labeler Code
  This is a code that is assigned by the FDA to the manufacturer, packager (“labeler”) or repackager of the drug as part of an application process.
• Product Code
  This is a code that is selected by the owner of the FDA Labeler Code.  It represents the unique combination of the drug, the dosage form and strength that will be packaged by that owner.  While the code is assigned by the owner of the Labeler Code it must be registered with the FDA.
• Package Size
  This is a code that represents the package size or package grouping of the drug.

For a short time the NDC started out in 1969 as a 9-digit code.  Initially the Labeler Code was defined as 3 alphanumeric characters long–a fixed length–but was soon changed to 4 numeric digits bringing the full code to the full 10-digits we know today.  The product code was defined as a fixed 4 digits long and the package size took up the remaining 2 digits.  But Labeler Code assignment requests came it at an alarming rate and it apparently wasn’t slowing down as they started to approach 999 sequential code assignments.

A decision had to be made.  If they crossed the border and assigned Labeler Code 1000, the NDC would forever be limited to 4 digits with a maximum of 9,999 codes and they might run out someday.  They were already approaching 10% of that number.  But if they made the fields of the NDC semi-fixed length at either 4 or 5 digits, they could continue assigning codes until a theoretical maximum of 99,999 codes.

The FDA didn’t want to expand the NDC to 11 digits so they decided to remove one digit from either the Product Code or the Package Size fields.  Rather than picking one or the other they decided to leave that choice up to each owner of the new 5 digit Labeler Codes.  Those companies could choose to have only 3 digits for the Product Code and 2 for the Package Size (written as 5-3-2), or they could choose to have 4 digits for the Product Code and only one digit for the Package Size (written 5-4-1).  The decision is made by the owner and they must register their choice and stick with it for the life of the Labeler Code.

But there is a problem with this approach.  Given a 10-digit NDC that might have a 4-digit or a 5-digit Labeler Code there could be conflicts between the NDC’s of two different companies.  Two companies might end up generating the identical NDC for two different products.  To eliminate this potential problem they decided to never assign labeler codes 1000 through 9999 (actually there is no explicit rule published that the FDA is following this technical requirement but it appears that this is what they are doing for most new Labeler Codes).  This makes the actual maximum number of Labeler Codes available equal to 90,999…not a bad compromise.

This solution provides a well-defined rule that allows systems to easily figure out the length of the Labeler Code within a given 10-digit NDC number.  All NDCs assigned by companies who own a 4-digit Labeler Code will always have a zero in their leftmost position and all NDC’s assigned by companies who own a 5-digit Labeler Code always have a non-zero digit in their leftmost position.  But there is no easy way to figure out if the owner of a 5-digit Labeler Code is using the 5-3-2 form or the 5-4-1 form without looking it up in a database.

The Package Size field is an important field used to differentiate not only the various dosage form sizes of the packages that the manufacturer or repackager produces (i.e. 30-count, 60-count, 90-count), but also the casepack quantities of each of that same set of packages.  There are no standard values for the Package Size field so the values used for one manufacturer cannot be compared with those of another.  They are simply used to differentiate package sizes and groupings within a single product type causing considerable confusion to those who wish to make use of this field.

For example, Company A might choose to use the values ’30′, ’60′ and ’90′ to represent the Package Size codes for their 30, 60 and 90 count bottles of a given drug, and the values ’31′, 61′ and ’91′ to represent a single casepack quantity of 48 bottles for the 30 pill bottle, and 24 bottles for the 60 and 90 pill bottles.  Company B might have chosen the 5-4-1 form of the NDC so they are left with only a single digit to represent their Package Sizes and groupings.  They might choose values ’1′, ’2′, and ’3′ for their 30, 60 and 90 count bottles of a given drug, and the values ’6′, ’7′ and ’8′ to represent the single casepack quantity of 96 bottles of their 30-count bottle, 48 bottles of their 60-count bottle and 24 of their 90-count bottle.  Confused yet?

So what use is this Package Size field if there isn’t any standard?  It simply allows manufacturers and repackagers to create unique NDCs for each dosage form size and casepacks so that interested parties can use it to look up the other information in a database.  You can’t just look at an NDC and know exactly what it stands for unless you have some prior knowledge about the choices the manufacturer or repackager has made for that product.  A database lookup doesn’t care what values are chosen for each packaging level or grouping as long as they are each unique.

NCPDP STEPS IN TO REDUCE AMBIGUITY

The current design of the NDC results in a number of ambiguities that stem from the fact that the length of each of the three fields can be one of two values.  The National Council for Prescription Drug Programs (NCPDP) decided to fix the ambiguity to increase the accuracy of claims submission.  They saw that all you have to do to return to a fixed length set of fields is to add an eleventh digit.  The goal was to always end up with a 5-4-2 format for all NDC’s.  To all 4-digit labeler codes (4-4-2) they added a ’0′ on the left.  To any 3-digit Product Code fields (5-3-2) they added a ’0′ on the left.  To any 1 digit Package Size (5-4-1) they added a ’0′ on the left.  All of these resulted in a 5-4-2 format (11 total digits).

For their purposes I’m sure this works great.  But it introduces its own ambiguity when an 11-digit “pseudo-ndc” is offered where a 10-digit true NDC is needed.  Which zero is the extra zero?  You can’t always tell unless you know for a given NDC.  Incidentally, the FDA apparently doesn’t recognize the NCPDP 11-digit format so it is not a real NDC.  That’s why I’ve called it a “pseudo-ndc”.

UNIT DOSE/UNIT-OF-USE NDCs

There is one more thing I want to say about NDCs.  I think the FDA made a significant error in not defining the NDC in a way that requires all pharma manufacturers and repackagers to clearly identify which NDC is a unit dose or unit-of-use for each drug.  The NDC appears to have been conceived as a way for a manufacturer to assign a unique code for each type of package they make for a given drug.  Since most manufacturers currently do not produce packages that contain a single unit dose or unit-of-use there is theoretically no need for them to define an NDC for that level.  I am told that some manufacturers do define and register an NDC for this level even if they don’t package at that level, and the rest do not.

I imagine that this has caused serious heartburn for insurers and Pharmacy Benefit Managers (PBMs) who are probably given the NDC for the original manufacturer’s bottle that a prescription was filled from.  What does it mean for a pharmacist to claim that they filled a prescription with ’1′ of NDC 9999988882 (psuedo-ndc 99999888802 for claims submission) where that NDC describes a 30-count bottle?  Did the patient receive one 30-count bottle or did they receive a single pill that the pharmacist pulled from a 30-count bottle?  There must be some convention for limiting the ambiguity that this introduces.  Perhaps someone can leave a comment to explain what happens in this instance.

In my view all manufacturers and repackagers should always generate and register an NDC for a unit dose or unit-of-use.  Ideally you’d like to think that the Package Size values of either ’00′ or ’0′ would be reserved to indicate the unit dose or unit-of-use, but since it wasn’t defined that way you will probably have lots of drugs that assign those values to some multi-dose/-use package or even a casepack.  It would be too disruptive to force that kind of change on the industry now.

REFERENCES

Normally I provide links to all my references, but there are a couple of sources that I drew from for lots of this content and so I’d like to list them here:

• George Wright IV, Vice-president, PIPS / Product Identification & Processing Systems, Inc.
• “HDMA Guidelines for Bar Coding in the Pharmaceutical Products Supply Chain”, Healthcare Distribution Management Association (HDMA), 2005
• “History of the UPC Bar Code and The Uniform Code Council, Inc.“, by Rob Cummings, Cummings Design
• George Laurer, Inventor of the UPC

Please submit a comment if you have additional information, clarifications or corrections.

Dirk.

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 the text of the law compares to the capabilities of the EPCIS standard.  From that analysis I think you will either be able to see that EPCIS by itself is insufficient to comply with the law, or you may see some flaw in my logic.  In that latter case, please leave a comment below to point out the flaw.  My intent is not to provide you with legal advice but to explain how the EPCIS technical standard would likely be applied when using it in an attempt to comply with the law.  Decide for yourself what you think will or won’t comply.

THE CALIFORNIA PEDIGREE LAW

The California Pedigree Law is now part of the California Business and Professions Code.  There are a number of resources that the California Board of Pharmacy provides to help you study and interpret the code.  Unfortunately all of the material on their website is a little out-of-date, but it still has some value.

• A page containing a copy of the pertinent text from the California Business and Professions Code.  The text on this page is the way the regulations were prior to the most recent modification of the law that pushed the effective date out to 2015-1017.  Most of it is still accurate.
• A draft of a PDF called “Questions and Answers Relating to the Electronic Prescription Drug Pedigree Law”.  Dated January 2008 please note that this document was written for the regulation as it existed prior to the last modification that pushed the effective date out to 2015-2017.  It is still a useful guide to the Board of Pharmacy’s interpretation of the law except when related to the effective dates and perhaps some of the exceptions to the law;
• A PDF called “Background and Summary of the California ePedigree Law”.  The document doesn’t have a date but it is obviously describing the law as it was prior to the latest revision that pushed the effective date to 2015-2017.  It is still useful because it provides some of the history leading up to that revision.

It would be nice if the Board would update these resources now that people are beginning to pay more attention to the current deadlines and are preparing for compliance.

To read the actual text of the current California Business and Professions Code click here and then search for the word “pedigree”, then click on the sections where your search finds that word.  That should take you to the actual text of those sections of the Code.  Now search for key words related to pedigrees.

I have written about the California Pedigree Law in the past.  You might find these essays of interest.  Click here for a list of RxTrace essays that contain references to it.  Dr. Adam Fein of Pembroke Consulting has written frequently about pedigree in general including the California Pedigree Law over the last 5 years or so.  Click here for a list of his DrugChannels blog essays about Pedigree.

THE CALIFORNIA CODE THAT IS PERTINENT TO THE TECHNICAL IMPLEMENTATION AIMED AT COMPLIANCE

First, what constitutes “a pedigree” under California Law?

Section 4034.

(a) “Pedigree” means a record, in electronic form, containing information regarding each transaction resulting in a change of ownership of a given dangerous drug, from sale by a manufacturer, through acquisition and sale by one or more wholesalers, manufacturers, repackagers, or pharmacies, until final sale to a pharmacy or other person furnishing, administering, or dispensing the dangerous drug. The pedigree shall be created and maintained in an interoperable electronic system, ensuring compatibility throughout all stages of distribution.

(b) A pedigree shall include all of the following information:

(1) The source of the dangerous drug, including the name, the federal manufacturer’s registration number or a state license number as determined by the board, and principal address of the source.

(2) The trade or generic name of the dangerous drug, the quantity of the dangerous drug, its dosage form and strength, the date of the transaction, the sales invoice number or, if not immediately available, a customer-specific shipping reference number linked to the sales invoice number, the container size, the number of containers, the expiration dates, and the lot numbers.

(3) The business name, address, and the federal manufacturer’s registration number or a state license number as determined by the board, of each owner of the dangerous drug,  and the dangerous drug shipping information, including the name and address of each person certifying delivery or receipt of the dangerous drug.

(4) A certification under penalty of perjury from a responsible party of the source of the dangerous drug that the information contained in the pedigree is true and accurate.

(5) The unique identification number described in subdivision (i).

(c) A single pedigree shall include every change of ownership of a given dangerous drug from its initial manufacture through to its final transaction to a pharmacy or other person for furnishing, administering, or dispensing the drug, regardless of repackaging or assignment of another National Drug Code (NDC) Directory number.

Dangerous drugs that are repackaged shall be serialized by the repackager and a pedigree shall be provided that references the pedigree of the original package or packages provided by the manufacturer.

[…]

The key to my argument is that all of this information (I’ve highlighted it for you above) must be present in “a record” or it isn’t a valid “Pedigree” according to this part of the Code.  A “single pedigree” must include information about every change of ownership of a given drug or it’s not a valid pedigree.

We only need parts of one more section to be able to determine why EPCIS by itself won’t work for California pedigree.  That’s section 4163.  I’m leaving out parts that aren’t needed for my argument, including the exceptions, so feel free to review the entire section to convince yourself that I haven’t bent anything to benefit my case:

Section 4163.

[…]

(c) […] commencing on July 1, 2016, a wholesaler or repackager may not sell, trade, or transfer a dangerous drug at wholesale without providing a pedigree.

(d) […] commencing on July 1, 2016, a wholesaler or repackager may not acquire a dangerous drug without receiving a pedigree.

(e) […] commencing on July 1, 2017, a pharmacy may not sell, trade, or transfer a dangerous drug at wholesale without providing a pedigree.

(f) […] commencing on July 1, 2017, a pharmacy may not acquire a dangerous drug without receiving a pedigree.

(g) […] commencing on July 1, 2017, a pharmacy warehouse may not acquire a dangerous drug without receiving a pedigree.

[…]

So once the law goes into effect, wholesalers, repackagers and pharmacies cannot sell, trade or transfer a drug without providing the buyer with “a pedigree”, and, separately, wholesalers, repackagers and pharmacies cannot buy a drug without receiving “a pedigree” from the seller.  Notice that this obligates both the buyer and seller independently.  If “a pedigree” isn’t provided with the transaction, both buyer and seller are breaking the law.

HOW EPCIS WAS DESIGNED TO WORK

EPCIS was designed to be used to implement a distributed network of repositories that each contain records describing the WHO, WHAT, WHEN and WHY of supply chain events that occur as serialized products move through a supply chain.  The original vision of EPCIS as applied to the U.S. pharmaceutical supply chain would expect each pharma manufacturer, each distributor and each pharmacy to have their own event repository that conforms to the EPCIS specification.

In their repositories, these companies would save records—or, events—that describe all of the serial number-based events that would occur while the drugs were under their control.  That is, the manufacturer’s repository would hold all of the events related to each drug package that occurred during manufacturing through shipment to the their customer, but it would not hold any of the events that occurred on the properties of downstream owners of those drugs.  Likewise, the distributor who bought the drugs from the manufacturer would typically hold only the events for those drugs from the point of receipt from the manufacturer through their own shipment to their customer.  And so on down the supply chain.

APPLYING BASIC EPCIS TO THE BASIC PEDIGREE PROBLEM

To get a full “trace”, or “supply chain history”, of a given package of a drug you would need to query each of the EPCIS repositories of all previous owners back to and including the manufacturer.  This “trace report” that would result would be a good example of a “chain of custody” report, but it would fall short of what California calls “a pedigree”.  It may be a valid pedigree in other jurisdictions under different laws but in California it would be missing the following necessary data elements from their definition:

• “Name”, “registration number or a state license number and principle address of the source”
  These data elements would be missing because, by definition, EPCIS makes use of Supply Chain Master Data (SCMD) references to save space.  Instead of the explicit information called out in the law the trace records produced by EPCIS queries would contain GS1 Global Location Numbers (GLNs) which are 13-digit numbers that are supposed to represent most of this data.  That representation is defined by the owner of the GLN and they are under no obligation to maintain it or to ensure that the data has a single, fixed association with the GLN.
• “Trade or generic name”, “dosage form”, “strength”, and “container size”
  These data elements would be missing because, like its use of GLN’s, EPCIS is designed to also use SCMD references for product data to save space.  In place of this data, each event would include only a GS1 Global Trade Item Number (GTIN) which is a 14-digit number that is supposed to represent most of that product data.  The manufacturer of the drug owns the relationship between the GTIN and the associated product data, but they are under no obligation to ensure there is only one, unchanging set of product data associated with that number.
• “Business name”, “address”, “federal manufacturer’s registration number or a state license number”…”of each owner” of the drug, including the “name” and “address of each person certifying delivery or receipt” of the drug
  Again, EPCIS events would hold a representation of this information as a set of GLN’s to save space.  The actual data would only be implied.
• “A certification under penalty of perjury from a responsible party of the source of the dangerous drug that the information contained in the pedigree is true and accurate”
  The EPCIS standard doesn’t define anything like this kind of data.
• “A single pedigree shall include every change of ownership…”
  The chain of custody report that is built as the result of the set of queries mentioned above would be a set of records that would need to be interpreted and the information combined into a single record.  But this would only be possible if the current owner knows who to query and then only if all of the previous owners of the drug were willing and technically able to reply at that particular moment with their contribution of the events they hold about that particular drug.

That’s a lot of missing information.  It may seem like the EPCIS standard is so far away from what the law calls for that it is hopeless to expect it to ever work.  Not quite.  EPCIS has an important feature that is intended to allow users to extend its operation in multiple ways.  This feature allows EPCIS to be shaped into solutions that can fit problems much more flexibly than previous general purpose systems might have in the past.  Can this extensibility feature address all of the missing information in some way and turn the chain of custody report into a compliant pedigree?  Perhaps.  I will consider that possibility in future essays in this series.  But first…

ENTER THE GS1 US HEALTHCARE 2015 READINESS PROGRAM

GS1 US saw these problems with EPCIS a number of years ago.  Since that time their Healthcare Traceability group has been working on potential solutions to some of the problems I listed above.  I can’t write about exactly how they propose to do that because they have policies that prevent the disclosure of that kind of internal information.  However, it appears that GS1 US is just about to make that kind of information public themselves in the next few weeks.  As soon as they do I will pick up this topic again and explain how their ideas might or might not address this list of deficiencies.

WHAT ABOUT GS1 (GLOBAL) HEALTHCARE?

That’s a good question.  That organization has been busy working on pedigree-related ideas as well, though at a global level, and, not coincidentally, they too are about to make public their latest thoughts on how to use the EPCIS standard for network-centric ePedigree applications.  Although their work is intentionally not aimed at meeting the exact requirements of the California law (because it is a global effort), their work does beg for an explanation of how it might fit if those ideas were applied in that State Law.  This release of information will probably occur in the next few weeks as well.  So we will shortly have lots of ideas in the public domain that we can discuss and analyze.  In fact, I hope we are not overwhelmed!

WILL ANY OF THIS MAKE ANY DIFFERENCE AT ALL?

Another great question.  In fact, it may all become moot, because a new federal pedigree bill was apparently introduced into the U.S. Congress a couple of weeks ago by Representative Jim Matheson [D-UT].  If that bill, or some modified version of it eventually makes it out of committee and then passes both Houses of Congress and then if the President signs it, it would almost certainly pre-empt the California Pedigree Law.  In that case, we will all shift our attention to the peculiarities of the Federal regulation and the likely FDA guidance that would certainly follow.

However, it is very hard to estimate the likelihood that this, or other bills like it in the future, will pass.  Similar bills introduced in past sessions have not made it out of committee.  So until one of these bills make it through the entire process, it makes the most sense to keep our eyes on the realities of the California requirements.

Stay tuned for Part 2 as soon as the GS1 US and GS1 (global) documents are made public.

Dirk.

For Part 2 in this series, see “Why GS1 EPCIS Alone Won’t Work For California Pedigree, Part 2“.

For the first time in over two years the topic of pedigree appears on the agenda of the California Board of Pharmacy for their upcoming meeting on September 7.  Earlier this year in a presentation at the FDA Track & Trace Workshop Board Executive Office Virginia Herald mentioned that the Board would take up the topics of inference, drop shipments, decommissioning and linkage between shipping orders and invoices at a future meeting in 2011.  It’s hard to tell if those will be the actual topics discussed in next week’s meeting because they aren’t called out explicitly.  Here is the item as it actually appears on the agenda:

Discussion on the Implementation of California’s Electronic Pedigree Requirements for Prescription Drugs
a. Overview of the Law
b. Comments of the FDA
c. Presentations and Questions from the Pharmaceutical Supply Chain
d. General Discussion

Perhaps the only new thing about this discussion will center around “b. Comments from the FDA” and the other topics might be covered more directly at a later meeting.  We’ll see.  Keep in mind that the Board is made up of members today who were not on the Board when they last dealt with the pedigree regulation.  The current members will probably need a good introduction to the law and the current state of the standards and the industry before they tackle the intricacies of things like inference, drop shipments and decommissioning.

Those are topics that the Board needs to provide some guidance on, but there are some other very important questions that need to be answered before companies are likely to fully invest in pedigree solutions.  Here I’m referring to both solution providers and companies within the supply chain.

Back in 2007 a subset of the Board analyzed the GS1 Drug Pedigree Messaging Standard (DPMS) to see if companies might be able to use it to comply with the law.  Generally the Board members present at that meeting felt that the standard appeared to include features that the industry could use to comply with the law.  Of course, use of DPMS does not automatically guarantee compliance, but the takeaway by those present (myself included) was that DPMS could be used to comply with the law if you applied it appropriately as specified in the law.

Since that time, nothing has really changed with DPMS, but there have been efforts within GS1 Healthcare and GS1 US Healthcare to come up with an alternative way to comply with the law using GS1’s Electronic Product Code Information Services (EPCIS) standard.  What is needed is for the Board to analyze those approaches in a similar way to see if they too might be used by supply chain participants to comply with the law.  Without that kind of analysis by the Board it would be risky for companies to invest in solutions that are based solely on EPCIS.

A FEW QUESTIONS

There are a number of novel ideas for producing a wide-spread pedigree system based on the EPCIS standard, but which ones would allow end-users to comply?  It would help to know the answers to the following questions.

Consider a hypothetical transaction where a hospital pharmacy is in desperate need of some cancer treatment drug that is on the FDA shortage list.  In a stroke of “good luck” the pharmacy finally finds a source through a fax they recently received from a newly licensed distributor in their area.  The drug is delivered by a courier who hands the pharmacy manager a USB thumb drive that contains a pedigree file that contains the  following information in a single EPCIS Shipping event:

WHO:  a 13-digit number
WHAT:  a 14-digit number representing the Serialized Global Trade Item Number (SGTIN) of the case that was delivered
WHEN:  a timestamp representing the date and time of the shipment
WHY:  “shipping”
SHIP TO:  a different 13-digit number recognizable as the hospital’s GS1 Global Location Number (GLN)
SOURCE EPCIS:  an internet address (URL)
CERTIFICATION:  a digital signature that spans the above information

Some of the questions are:

1. Has the seller fulfilled their requirement to provide a pedigree to the buyer?
2. Has the hospital fulfilled their requirement to receive a pedigree from the seller?
3. Has the seller provided the necessary certifications?
4. What if the file were transmitted to the hospital through a more conventional EPCIS-to-EPCIS connection?
5. What if the buyer is able to use the case SGTIN contained in the “WHAT” field and the URL contained in the “SOURCE EPCIS” field to find and collect the Aggregation event that includes the SGTIN’s of all of the units inside the case and then collects the Supply Chain Master Data (SCMD) that describes the drug for those units through some separate mechanism like GS1’s Global Data Synchronization Network (GDSN), and they are also able to find and collect the Commission events of the units that contain the lots and expiration dates of the units in the case?
6. What if the buyer is able to use the contents of the “WHO” field of every one of the events obtained in question 5 above to find and collect the SCMD that describes the seller and all previous owners through another separate mechanism like GS1 US’s GLN Registry for Healthcare?
7. What if, instead of the steps in questions 5 and 6 the buyer was able to supply the entire shipping event received from the buyer to a certified third-party service that performed all of the data collection described in questions 5 and 6 and simply returned a list of the unit level SGTIN’s contained in the case, each with a pass/fail flag to indicate the status of their pedigrees, but the buyer routinely never actually receives or sees all of the information unless a separate request is made for the entire supply chain history for those units?

Lots of companies seem to want to use EPCIS to comply with pedigree regulations but there are so many ways the standard could be applied it is hard to know which way to go unless they know that the results will allow them to comply.  And they need to know soon to allow time for standards organizations to draw up standards and/or guidelines and solution providers to produce applications in time for supply chain companies to evaluate, buy, deploy and test them.   Now that the California Board of Pharmacy is about to begin to discuss their pedigree regulation again, maybe now is the time.

Dirk.

At the end of my last essay I said I had recently concluded that the jump to a fully automated pharma supply chain upstream visibility system is too big and complex to be achievable by every company in the U.S. supply chain by the California dates.  I want to explain that statement in a future essay (soon), but before I do I want to explore some of the track and trace models that are being considered by both GS1 and the FDA.  I particularly want to look at the viability of each model because I think we will find that some just aren’t (viable), and that will help narrow the search.

I’ll look at the three basic models that the FDA mentioned in their recent workshop:  Centralized, Semi-Centralized and Distributed (or Decentralized as the FDA called it).  There are others, but it seems that they can all be either based on, or reduced to, one of these three basic models.

In this essay I am looking at track & trace models from a global viewpoint, which is something that GS1 is doing but the FDA may not.  Attacks on the pharma supply chain are a global problem and global problems demand global solutions or gaps will be left for criminals to exploit.

GS1′s goal is to develop standards that apply globally as much as possible and the FDA will likely find that global manufacturers are more willing to implement something that is the same–or similar to–something they are already deploying elsewhere in the world.  It’s a good idea because any approach that has been demonstrated to be viable elsewhere in the world is probably more likely to be viable here…though that’s not guaranteed.

THE CENTRALIZED TRACK & TRACE MODEL

I would draw a Centralized track & trace model with a single, central track & trace repository (or at least a single system) for the entire world.  That’s what centralized means.  (Click on the drawings to enlarge them.)

Figure 1. Global Centralized Track & Trace Model. Not viable!

Most people probably don’t think of the Centralized model as requiring a single repository/system for the entire world but if you have more than one, you are talking about a “Semi-Centralized” model.  That’s a different model, which I will talk about below.

In my view, the concept of a Centralized track and trace model depicted in Figure 1 above is not viable at all.  For something like this to work you would probably need some kind of central global government that mandates its use, or at least a global law enforcement agency.  I don’t think we’ll see that any time soon.  Until then, this model is not viable.

THE DISTRIBUTED TRACK & TRACE MODEL

The Distributed track & trace model is one where each trading partner communicates with their immediate upstream and downstream trading partners under normal circumstances, and with other companies in the supply chain who may not be direct trading partners when necessary for certain applications.  ePedigree is one of the applications that would most often require a company to need to communicate with another company in the supply chain that is not an immediate trading partner.  The method for finding these other companies is one of the things that differentiates various flavors of the Distributed track & trace model.

The concept being followed in GS1 US Healthcare‘s EPCIS-based ”2015 Readiness Program“ is a Distributed track & trace system.  Some flavors of the Distributed model make use of GS1′s future Discovery Services standard and some do not.

Regular readers of RxTrace already know that I am not a fan of distributed models for implementing ePedigree in the U.S. pharma supply chain.  I have several problems with the concept.

The California Pedigree Law requires that each drug sold in the supply chain be accompanied by a valid and complete ePedigree.  If a seller can’t supply one, then they can’t sell the drug.  That means that the value of their inventory is totally dependent on their ability to supply ePedigrees.

In a Distributed model, the seller’s ability to supply a valid ePedigree is totally dependent on each of the previous owner’s ability to respond with their part of the ePedigree at the time of the sale.  The value of the drug can be completely destroyed if any one of them can’t respond.  In my view, that will introduce a level of risk that companies will find very distasteful at best and unworkable at worst.

For more on my concerns about the Distributed track & trace model, see the RxTrace essays in this list.

But when you consider how the Distributed model would fit into the current global situation, with several countries already having adopted their own central repositories, you realize that any adoption of a Distributed model in the U.S. would result in a very mixed model globally.  If the E.U. adopts a Point of Dispense (POD) authentication model it would be even more mixed.

Here is my depiction of that situation.

Figure 2. Global Mixed Track & Trace Models. Problematic for global manufacturers. Is it viable?

I’m showing a single manufacturer (blue) and a few distributors (red) and some of their pharmacy customers (black) in the U.S. using a distributed model, and that same manufacturer with a similar mix of distributors and pharmacies in the E.U. using a POD Authentication model.  The drawing shows the same manufacturer communicating with the national repositories of China, Brazil, Turkey and Italy.

This diversity of models around the globe could be problematic for global manufacturers because it will force them to use different approaches and different systems to deal with each model.  Note that U.S. distributors and pharmacies won’t be affected by the different approaches used in other regions.  This is only an issue for the many manufacturers that sell their products globally.

Is the Distributed model viable?  I don’t think it is if you assume it would have to be deployed in every country, thus making it truely global.  Is the mixed global track and trace model of Figure 2 viable?  That’s a question for global manufacturers to answer.  If you focus only on the U.S., a Distributed model would necessitate less rigid regulatory requirements than we currently have in California for it to be viable.

THE SEMI-CENTRALIZED TRACK & TRACE MODEL

The Semi-Centralized model is characterized by multiple “central” repositories of track & trace data around the globe.  What data is stored in each repository, and which repository must be used for a given transaction, is determined by local regulations and/or by the businesses involved.

The national track & trace repositories of China, Turkey, Brazil and Italy fit into this model like a glove.  The track & trace data for any drug that is distributed within those countries would be easy to find…it’s in that nation’s repository.

But in free-market countries where the model would be adopted without national repositories there are a number of ways you could design the implementation.  Most likely, solution providers would enter the business of providing repositories that conform to the regional regulatory requirements.  To solve the problem of a growing number of repositories that each end-user company would need to deal with, other solution providers (or the same ones) would likely offer connection services.

Here is one way a global Semi-Centralized track & trace model might look if there were three companies in the business of offering free-market repository services and six companies offering free-market connection services:

Figure 3. A Global Semi-Centralized Track & Trace Model. Notice that national repositories, free-market repositories and even POD Authentication fit nicely into this model.

The particular depiction shown in Figure 3 is the version of this model that I originally described in “A Semi-Centralized, Semi-Distributed Pedigree System Idea“, but with more details.  The Free-Market Repositories shown in this example would each contain all of the supply chain history of every serialized instance of specific GTIN’s as determined by contracts with the manufacturers (blue).  Therefore, each manufacturer only needs to connect to that one repository.  This would include GTIN’s that are labeled for sale in any “free-market” region.

For drugs labeled for sale in the U.S., distributors and pharmacies would find the supply chain history in a known location for each manufacturer’s product, but because they would buy and sell the products for all manufacturers, they would each need to connect with all of the free-market repositories.  They would obtain assistance in doing that from one of the free-market connection service providers shown.

In the E.U., POD Authentication would be done by querying the free-market repository that contains the information for that specific GTIN, through one of the free-market connection services.

The complete ePedigree (as defined by local regulations) for a single serialized drug package would always be held in a single repository, whether free-market or national, no matter where the product was distributed in the world.

In this model, global manufacturers would need to connect to a small, fixed number of repositories and could easily fulfill their free-market regulatory obligations, including ePedigree and POD Authentication, through contracts with their chosen repository service provider.  U.S. distributors and pharmacies could count on the availability of ePedigrees to fulfill local regulations like the California Pedigree Law without fear of loss of inventory value.

The Semi-Centralized track & trace model seems particularly viable to me because it solves so many of the problems for global pharma manufacturers without the added expense of GS1′s future Discovery Services.

Interestingly, certain implementations of the Distributed model could actually collapse slowly over time, into a distorted Semi-Centralized model.  This would happen if individual companies get tired of dealing with responding to queries from upstream trading partners and decide to turn that responsibility over to a service provider.  As that service provider increases the number of trading partners they are servicing, the model starts looking more “semi-centralized”.

I’d also like to point out how the Semi-Centralized model can be built over time in stages that each enable some supply chain security and other benefits.  For example, manufacturers could begin by posting only their EPCIS Commission events to their contracted repository service provider and that could enable a number of low cost serial number authentication technologies (cell phone, web page, web services) before the industry moves to the next stage–perhaps POD Authentication.  I’ll talk more about these stages, or “security plateaus” in a future essay.

Which of these global track & trace models is your favorite and why?

Dirk.

In this essay, I’m not going to discuss the attributes of a track & trace system from a regulator’s point of view.  I’m not going to discuss input into the FDA’s Track & Trace workshop that occurs this week and I’m not going to speculate on the outcome of that meeting.  Instead, I’m going to talk about the attributes of a track & trace application from the viewpoint of any global pharma manufacturer who is facing the regulatory mandates for serialization and traceability in a growing list of countries around the world, and from the viewpoint of any solution provider who is thinking about what they need to include in their solution offering so that those global pharma companies find it attractive enough to buy.  

To those kinds of companies, the potential for new non-binding guidance from the U.S. is important, but perhaps less so than an increasing number of binding regulations from around the world.  Whatever the FDA—and especially the U.S. Congress—may do in the future will be important when selecting a track & trace solution, but the U.S. is only one of the countries in the world and pharma companies that do business in those other countries do not have time to wait for the U.S. to figure out their approach before making investments. 

The goal is to make investments today that will be flexible enough to accommodate existing laws around the globe and whatever ultimately might or might not happen in the U.S., the E.U. and elsewhere.  To accomplish that, “flexibility” is the key word and the key attribute.  The application you invest in should not be only targeted at a single regulation but should be designed to provide building-blocks of functionality which can be applied differently to the same products that will be shipped into many different regulatory environments around the world. 

Companies looking to buy a solution should look for a provider that has already made their own investments in understanding the specific regulations around the world.  You need a partner to help you understand and meet the specific requirements in Turkey, Brazil, Italy, India, China, South Korea and others that might pop up in the future.  Look for a solution provider who knows the existing global regulations and also knows exactly how to apply their solution in a way that will meet each one. 

THE ATTRIBUTES 

Here is a list of attributes to look for in a global track and trace solution. 

Interoperability.  In a phrase, “Standards-Based”.  Reject all proprietary solutions or you will find that your solution does not work with those selected by your trading partners.  It’s surprising how often I receive an email from a solution provider who thinks the world will be so much better off once their proprietary solution is deployed by everyone in the world.  In fact, no approach to track and trace will work if it is only supplied by a single company.  Interoperability demands a standards-based approach so that multiple companies can offer solutions that are fully compatible with each other.  That way pharma company A can invest in the solution from solution provider A’, and pharma company B can invest in the solution from solution provider B’, and wholesaler C can invest in the solution from solution provider C’, and so on, and they all work together without any special patching.  That’s interoperability. 

Today, the safest bet is to deploy solutions that are based on GS1 standards.  There are two major reasons for that.  First, several countries, notably Brazil, India and South Korea, have apparently explicitly named GS1 identification standards in their regulations or in their guidance.  (Be careful.  GS1 has a lot of standards.  This doesn’t mean that these countries require you to use every single standard that GS1 publishes so study the regulations carefully to learn exactly which GS1 standards are actually mandated.)  

Second, there is a lot of pharma industry activity in GS1’s end-user organizations including GS1 Healthcare (global) and GS1 US Healthcare.  This activity offers an indispensible source of adoption examples and experience.  No matter what, it’s dangerous jumping onto the cutting edge when you are forced to adopt new technology while regulations are still evolving, but at least it feels less dangerous when you are in a crowd of other companies who are forced to do the same thing.  

Don’t be lulled into thinking that GS1 or GS1 US knows what they are doing either.  Be prepared to interpret the regulations for yourself, but expect to deploy a solution that makes use of some GS1 standards.  Just because GS1 identification standards are usable today and are the most likely candidates for pharmaceuticals that are packaged for sale in certain markets doesn’t mean necessarily that GS1’s data exchange standards like DPMS or EPCIS will apply to those same markets.  GS1 isn’t done developing standards for pharmaceutical track and trace so we can’t yet tell which of their standards provide the right mix of interoperability and compliance.  That makes it tough to figure out today what the right choice is and that may lead to less efficiency than companies would like.  All the more reason to select a solution provider who is willing and able to respond to changes in regulations, and to evolving standards as well. 

Serial Number Management.  This feature of a track & trace application doesn’t need to be standardized across all industry deployments, although it must work with both standard and country-specific identifiers.  In fact, this is going to be one of the key differentiating features of the products that you will need to select between.  Serial number management is a set of functionality that will allow you to securely and accurately control and keep track of the serial numbers that you apply to your pharmaceutical products.  Again, flexibility will be crucial.  You need a single, centralized (within the corporation) place where serial numbers of all types will be allocated and then distributed to the remote facilities where the actual commissioning (association of a serial number to a physical thing) occurs.  In GS1 parlance, this includes SGTIN’s (Serialized Global Trade Item Numbers), SSCC’s (Serial Shipping Container Codes), GIAI’s (Global Individual Asset Identifiers) and GRAI’s (Global Returnable Asset Identifiers). All of these standard identifiers need to be managed by the proprietary serial number management module of your track and trace solution. 

This management must also work well for regions of the world where the local government defines the serial numbers and provides them to you, either in data form (as appears to be the case in China) or as pre-printed stickers (as appears to be the case in Italy and Brazil).  Even when the government gives you these numbers you still need to keep track of them.  Because these numbers may not always conform to GS1 standards, your solution will need to be able to deal with non-standard identifiers and serial numbers as well.  Exactly how that is done ought to be a big differentiating factor in your selection process. 

Certifications.  A certification is a way to attach individual or corporate assertions of truthfulness to the track and trace data in order to fulfill specific requirements to do so.  It’s a feature of some regulations that is intended to make it easier to prosecute criminals—one of the more important reasons for the existence of track & trace regulations.  Not all country regulations require you to include a certification within your track and trace data but your track & trace solution needs to be able to include them if you expect to use it in California after January 1, 2015.  That’s when their pedigree regulation goes into effect for the first 50% of each manufacturer’s product.  This ought to be another big differentiating factor in your solution selection process if your products end up there.  Any solution provider who has this figured out is well on the way to deserving your business. 

Pedigree Reporting.  This is a catchall term I am using here to cover any and all reporting requirements that each track & trace regulation includes.  If a regulation specifies it, your solution needs to supply it.  The problem here is that many of the global requirements are not well defined and you could easily find that the regulatory agency that oversees the regulation comes up with the need for a particular report that is not clearly spelled out in the regulation.  You need a technology partner who is going to monitor these agencies around the world on behalf of their customers so that they will be the first to know about the new reporting requirement and they will already be working on its implementation when you first become aware of its need.  

RFID and Barcode Data Capture.  Finally, the track & trace solution you select should be capable of easily handling serialization data capture from both RFID and Barcode data carriers.  Even if you don’t plan to make use of one or the other today, you may find that certain jurisdictions mandate one or the other.  For example, I understand that South Korea has, or will, mandate the use of RFID on pharmaceuticals sold there.  If I understand that right, and if you package drugs for sale in that market, then you may be faced with applying RFID tags to those units. 

These attributes may eliminate some solution providers from consideration.  Watch out for any solution provider that doesn’t have one or more people dedicated to monitoring global regulations.  If they are only in business to sell you a solution to today’s static “regulatory problem” then they aren’t worth your time.  That’s because we are in a very dynamic regulatory situation today when it comes to global pharmaceutical track and trace regulations.  You should be looking for a technology partner who has a long-term interest in meeting the shifting pharma track & trace demands of all the world’s governments.  That’s a tall order, and one that demands flexibility and constant attention.