<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: e-Pedigree: Delay, Delay, Delay</title>
	<atom:link href="http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/</link>
	<description>The Business of Pharmaceuticals</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:53:10 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: freesoft32</title>
		<link>http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/comment-page-1/#comment-109489</link>
		<dc:creator>freesoft32</dc:creator>
		<pubDate>Sun, 20 Mar 2011 12:36:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/#comment-109489</guid>
		<description>thanks you very much!!!!</description>
		<content:encoded><![CDATA[<p>thanks you very much!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: engelliler</title>
		<link>http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/comment-page-1/#comment-96642</link>
		<dc:creator>engelliler</dc:creator>
		<pubDate>Wed, 29 Dec 2010 09:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/#comment-96642</guid>
		<description>I actually agree with your comment to the stage of development of different ideas can be created</description>
		<content:encoded><![CDATA[<p>I actually agree with your comment to the stage of development of different ideas can be created</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam J. Fein</title>
		<link>http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/comment-page-1/#comment-574</link>
		<dc:creator>Adam J. Fein</dc:creator>
		<pubDate>Wed, 23 Apr 2008 01:35:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/#comment-574</guid>
		<description>FYI, the CA law may be moot since the introduction of a House bill H.R. 5839 Safeguarding Americaâ€™s Pharmaceuticals Act of 2008, which will establish uniform national standards and preempt the state laws.  I posted an analysis of the bill on my blog:

http://www.drugchannels.net/2008/04/national-standards-its-about-time.html

Adam</description>
		<content:encoded><![CDATA[<p>FYI, the CA law may be moot since the introduction of a House bill H.R. 5839 Safeguarding Americaâ€™s Pharmaceuticals Act of 2008, which will establish uniform national standards and preempt the state laws.  I posted an analysis of the bill on my blog:</p>
<p><a href="http://www.drugchannels.net/2008/04/national-standards-its-about-time.html" rel="nofollow">http://www.drugchannels.net/2008/04/national-standards-its-about-time.html</a></p>
<p>Adam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam J. Fein</title>
		<link>http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/comment-page-1/#comment-491</link>
		<dc:creator>Adam J. Fein</dc:creator>
		<pubDate>Sat, 29 Mar 2008 17:04:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pharmexec.com/2008/03/28/e-pedigree-delay-delay-delay/#comment-491</guid>
		<description>I&#039;m puzzled by the statement that &quot;California law isnâ€™t requiring anything that fancy.&quot;  I think you are minimizing the real-world challenges of this law.

Existing technology can be used to comply with California&#039;s law, but current product identification and supply chain practices are not sufficient for CA e-pedigree.  For example, many products have bar coded UPCs to identify a specific product. Every package of a particular product/size combination can have the same bar code.

In contrast, serialization (under CA law) requires a *unique* identifier on each individual package.  The volume of data is much, much, much greater b/c each specific package gets it own bar code.

Thus, complete serialization with e-pedigree requires affixing a unique number during the packaging process, capturing and managing the data, adding pedigree information as the product moves down the supply chain, and then making these data easily (but securely) accessible. It also requires substantial lead time since serialization must happen during the drug manufacturing process, which can be months (or longer) from the time that the product is dispensed to a patient.  Standards must also be developed and adopted by literally thousands of independent participants in the supply chain â€” manufacturers, wholesalers, pharmacies, and technology providers. The whole system must also be flexible enough to deal with all of the supply chain variations from manufacturer to patient.

As I have noted in my blog, this is (becoming) feasible but neither easy nor cheap. And to put the pharma industry&#039;s challenge in perspective, there were more than 4 billion prescriptions filled in the US 2007. 

Hopefully, the CA Board of Pharmacy can put aside their pharma-bashing and get on with the hard work needed over the next 33 months.

Adam J. Fein
http://www.DrugChannels.net</description>
		<content:encoded><![CDATA[<p>I&#8217;m puzzled by the statement that &#8220;California law isnâ€™t requiring anything that fancy.&#8221;  I think you are minimizing the real-world challenges of this law.</p>
<p>Existing technology can be used to comply with California&#8217;s law, but current product identification and supply chain practices are not sufficient for CA e-pedigree.  For example, many products have bar coded UPCs to identify a specific product. Every package of a particular product/size combination can have the same bar code.</p>
<p>In contrast, serialization (under CA law) requires a *unique* identifier on each individual package.  The volume of data is much, much, much greater b/c each specific package gets it own bar code.</p>
<p>Thus, complete serialization with e-pedigree requires affixing a unique number during the packaging process, capturing and managing the data, adding pedigree information as the product moves down the supply chain, and then making these data easily (but securely) accessible. It also requires substantial lead time since serialization must happen during the drug manufacturing process, which can be months (or longer) from the time that the product is dispensed to a patient.  Standards must also be developed and adopted by literally thousands of independent participants in the supply chain â€” manufacturers, wholesalers, pharmacies, and technology providers. The whole system must also be flexible enough to deal with all of the supply chain variations from manufacturer to patient.</p>
<p>As I have noted in my blog, this is (becoming) feasible but neither easy nor cheap. And to put the pharma industry&#8217;s challenge in perspective, there were more than 4 billion prescriptions filled in the US 2007. </p>
<p>Hopefully, the CA Board of Pharmacy can put aside their pharma-bashing and get on with the hard work needed over the next 33 months.</p>
<p>Adam J. Fein<br />
<a href="http://www.DrugChannels.net" rel="nofollow">http://www.DrugChannels.net</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

