Tag Archives: GS1

Should GS1 Continue Developing ePedigree Standards?

Photo by immrchris

Important Notice To Readers of This Essay On November 27, 2013, President Barack Obama signed the Drug Quality and Security Act of 2013 into law. That act has many provisions, but one is to pre-empt all existing and future state serialization and pedigree laws like those that previously existed in California and Florida. Some or all of the information contained in this essay is about some aspect of one or more of those state laws and so that information is now obsolete. It is left here only for historical purposes for those wishing to understand those old laws and the industry’s response to them.For the first time since GS1 produced the Drug Pedigree Messaging Standard (DPMS) standard in 2005, GS1 has just published a call-to-action for the formation of a new standards development group to focus on a new pedigree-related standard.  The new group will be called the “Pedigree Security, Choreography and Checking Service (PSCCS) Mission Specific Work Group (MSWG)”.  According to the call-to-action:

“This group will develop standards to allow pharmaceutical supply chain parties striving to meet pedigree regulation requirements, by gathering and checking pedigree event data.  Standards will also address data confidentiality and security.  This MSWG will create

        A) standard for security framework applicable to EPCIS and,

        B) pedigree checking services.”

This group’s output will not be a self-contained pedigree standard, per se, but Continue reading Should GS1 Continue Developing ePedigree Standards?

FDA Proposed UDI: AIDC Requirements

 

Mental Telepathy AIDC.
Photo by Nadya Smolskaya

Linear barcodes2D barcodesRFIDManipulated DNA stands?  Microscopic pattern recognition?  Mental telepathy?  Which Automatic Identification / Data Capture (AIDC) technology(ies) can you expect on the medical devices you buy in the U.S. supply chain in the future?  This is the second in a multi-part series of essays examining various aspects of the recently proposed Unique Device Identification (UDI) rule by the U.S. Food and Drug Administration (FDA) (see last week’s essay, “FDA Proposed UDI: A Revolution In Number Assignment”.

The proposed FDA UDI rule requires the use of human readable and at least one AIDC technology to carry the new standardized identifier on all non-exempt devices and/or their packages.  An AIDC technology is a way of Continue reading FDA Proposed UDI: AIDC Requirements

Standards and Guidance For U.S. Pharma Supply Chain Technology

[This essay is one of two long lost essays that have now been restored on RxTrace.  It was originally published on November 22, 2010.  See “Return Of Two Classics” for an explanation.]

In my last essay, “Who Will Decide Which Pedigree Model You Will Invest In?” I pointed out how easy it is to get confused about pedigree technology because of varying claims made by certain companies who have interests that don’t align well with yours.  So where can you get better information?  I can provide you with a few good sources, and I will also tell you about a missing ingredient that I see in the current guidance landscape that will need to be addressed in the next couple of years. Continue reading Standards and Guidance For U.S. Pharma Supply Chain Technology

Before You Sign Up For GDSN, Get Your Data In Order With A Data Quality Program

Last week I published an essay that gave GS1 some advice on how to trigger interest in adoption of their Global Data Synchronization Network (GDSN).  Those of you who read that essay in the first two days read my snarky comments about GS1 seemingly attempting to commandeer the term “Data Quality” to include the need for GDSN.  That was based on a mis-interpretation of their marketing materials for their “Data Quality Framework” and as soon as I discovered my mistake I removed that part of the essay, leaving the core point of the essay intact (see “An Open Letter to GS1, RE: GDSN Marketing”).

In fact, GS1 is saying exactly the opposite of what I originally thought regarding Data Quality and GDSN.  That is, before you start publishing your supply chain master data (SCMD) through GDSN you should ensure that the quality of your data is high.  As GS1 points out, “Good quality data is foundational to collaborative commerce and global data synchronisation.”  I couldn’t agree more.

The GS1 Data Quality program is centered on the “Data Quality Framework”, which is Continue reading Before You Sign Up For GDSN, Get Your Data In Order With A Data Quality Program

An Open Letter to GS1, RE: GDSN Marketing

Dear GS1,

How have you been?  I’ve been fine, done a bit of writing since we last met and gotten a little greyer.  How are the kids?  My two kids are doing great but I have to admit, after raising two I don’t know how you do it with 125 kids, or whatever the number of M.O.s there are today.

The reason I’m writing to you today is to offer you my thoughts on your Global Data Synchronization Network (GDSN) Marketing campaign.  That campaign would be more effective if it focused on demonstrating the distinction between internal master data (and programs associated with improving its quality), and externally shared master data (and the significantly different kinds of programs needed to improve its quality).  And especially to show that many (most?) of company master data is, in reality, externally shared master data, either incoming or outgoing.  That’s the step that I see missing from your campaign.

Companies who are already familiar with the kind of programs that are designed to improve their internal master data need to be taught to see the special characteristics of Continue reading An Open Letter to GS1, RE: GDSN Marketing

The Serial Number Handling In Your WMS Probably Isn’t Sufficient For Pharma Serialization

Important Notice To Readers of This Essay On November 27, 2013, President Barack Obama signed the Drug Quality and Security Act of 2013 into law. That act has many provisions, but one is to pre-empt all existing and future state serialization and pedigree laws like those that previously existed in California and Florida. Some or all of the information contained in this essay is about some aspect of one or more of those state laws and so that information is now obsolete. It is left here only for historical purposes for those wishing to understand those old laws and the industry’s response to them.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 Continue reading The Serial Number Handling In Your WMS Probably Isn’t Sufficient For Pharma Serialization

Your GS1 Company Prefix: An Enterprise Resource

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 Continue reading Your GS1 Company Prefix: An Enterprise Resource

Should FDA Cede All Standards Development To GS1?

Back in 2007 the U.S. Congress passed the Food and Drug Administration Amendments Act (FDAAA) and it was signed into law by President Bush.  One of the provisions of that law was an instruction to the FDA to “…develop standards and identify and validate effective technologies for the purpose of securing the drug supply chain against counterfeit, diverted, subpotent, substandard, adulterated, misbranded, or expired drugs”, and “…develop standards for the identification, validation, authentication, and tracking and tracing of prescription drugs.”

The FDA fulfilled these instructions for one of the specific standards that the law identified when the agency published their Standardized Numerical Identifier (SNI) standard back in 2010.  That standard was fairly high level and for the vast majority of drugs, use of GS1’s Serialized Global Trade Item Number (SGTIN) (or “GTIN plus serial number”) for drug package identification would comply with it.  The text of the FDA’s standard says as much.

By defining the SNI in this way did the FDA surrender the development of the real SNI standard to GS1 (at least the sNDC portion of it)?  I don’t think so.  In my essay about the SNI standard I described it as the FDA “aligning” with GS1’s SGTIN (see my essay “FDA Aligns with GS1 SGTIN For SNDC”).  Alignment shouldn’t be confused with surrender.  The choice of alignment with SGTIN was good for the FDA, good for patients and good for the industry.

WHAT WE GOT WHEN THE FDA ALIGNED THEIR SNI STANDARD WITH GS1’S SGTIN TECHNICAL STANDARD

In the case of the SNI aligning with GS1’s SGTIN we got the following things: Continue reading Should FDA Cede All Standards Development To GS1?