Search
Subscribe

Bookmark and Share

About this Blog

As enterprise supply chains and consumer demand chains have beome globalized, they continue to inefficiently share information “one-up/one-down”. Profound "bullwhip effects" in the chains cause managers to scramble with inventory shortages and consumers attempting to understand product recalls, especially food safety recalls. Add to this the increasing usage of personal mobile devices by managers and consumers seeking real-time information about products, materials and ingredient sources. The popularity of mobile devices with consumers is inexorably tugging at enterprise IT departments to shifting to apps and services. But both consumer and enterprise data is a proprietary asset that must be selectively shared to be efficiently shared.

About Steve Holcombe

Unless otherwise noted, all content on this company blog site is authored by Steve Holcombe as President & CEO of Pardalis, Inc. More profile information: View Steve Holcombe's profile on LinkedIn

Follow @WholeChainCom™ at each of its online locations:

« Mostly Invented Somewhere Else | Main | Granularity & Semantic Trust »
Monday
Mar312008

EPCglobal & Prescription Drug Tracking

Andrew Pollack authored an article in the New York Times on March 26, 2008 entitled California Delays Plan to Track Prescription Drugs.

"In a reprieve for the pharmaceutical industry, California regulators agreed on Tuesday to delay by two years a requirement that all prescription drugs be electronically tracked as a means of thwarting counterfeiting.....

The California plan would require that drugs be tracked electronically from the manufacturer through the wholesaler to the pharmacy. Each bottle of pills sold to a pharmacy would have to have a unique serial number, encoded in a bar code or a radio-frequency identification tag.....

Pharmaceutical manufacturers [said that] putting a unique serial number on each container would require changing their packaging lines, which would cost millions of dollars and take years. […] Pharmacies and wholesalers, meanwhile, said they could not install the software and the equipment needed to read the serial numbers until they knew what systems the drug manufacturers would use."

Though not directly identified in Pollack's article, EPCglobal is a leader in establishing standards in the area of drug tracking. EPCglobal is a private, standards setting consortium governed by very large organizations like Cisco Systems, Wal-Mart, Hewlett-Packard, DHL, Dow Chemical Company, Lockheed Martin, Novartis Pharma AG, Johnson & Johnson, Sony Corporation and Proctor & Gamble. EPCglobal is architecting essential, core services for tracking physical products identified by unique electronic product codes (including RFID tags) across and within enterprise systems controlled by large organizations.

I submitted a comment to EPCglobal on January 22, 2008 about EPCglobal's Architecture Framework. You will see that the comment is addressed to Mark Frey who courteously and immediately responded that he had forwarded it to EPCglobal's Architectural Review Committee.

This is a 10 page comment (including exhibits) about broader data ownership issues than just those relating to electronic pedigree documentation for use by pharmaceutical supply chain. But see the first full paragraph on page 5 where I said:

“[W]hile EPCglobal has begun establishing forward-looking standards relative to electronic pedigree documentation for use by pharmaceutical supply chain participants [see EPCglobal Pedigree Ratified Standard Version 1.0 as of January 5, 2007], it has yet to include these standards within the EPCglobal Architecture Diagram.

With this comment I am proposing, by way of an illustrative example, that the methods developed by Pardalis within its IP may be used to derive essential specifications for connecting the current EPCglobal (EPCIS) Architecture with its ePedigree standards for the pharmaceutical industry."

The illustrative example referred to above is a mock Common Point Authoring (CPA) informational object. This illustrative example has a reference point beginning with a granular EPCglobal ePedigree document. The represented CPA informational object is the EPCglobal ePedgiree document that has been further granularized with mock XML tagging containing unique identifiers pointing to a CPA registered data element database.

My point is that EPCglobal has yet to develop standards for ePedigree document exchange that may be efficiently, flexibly and cost-effectively applied to the pharmaceutical supply chains for helping to reduce counterfeiting. Given the players who comprise EPCglobal, it is reasonable to presume that California regulators have essentially backed off enforcing their anti-counterfeiting regulations because EPCglobal has yet to catch up to the California plan. The plan was to take effect January 1, 2009. Now it has been pushed back to 2011.

PrintView Printer Friendly Version

EmailEmail Article to Friend

References (4)

References allow you to track sources for this article, as well as articles that were written in response to this article.
  • Source
    "In a reprieve for the pharmaceutical industry, California regulators agreed on Tuesday to delay by two years a requirement that all prescription drugs be electronically tracked as a means of thwarting counterfeiting."
  • Source
  • Related
    "This document defines and describes the EPCglobal Architecture Framework. The EPCglobal Architecture Framework is a collection of hardware, software, and data standards, together with core services that can be operated by EPCglobal, its delegates or third party providers in the marketplace, all in service of a common goal of enhancing business flows and computer applications through the use of Electronic Product Codes (EPCs)."
  • Related
    "This document and its associated attachments specify an architecture for the maintenance and exchange of electronic pedigree documents for use by pharmaceutical supply chain participants. The architecture is targeted for use in complying with document-based pedigree laws."

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>