One of the questions that must be answered is, “how will an ePedigree and track & trace system be funded?”. Who pays, who gets paid, and how much? The answer to these questions are partly determined by which technology model is in use. One reason a distributed model is usually the first model people think of is that the funding is so obvious: it is localized. In that model each company would arrange for their own services. No pooling is needed. That’s simple to understand and quantify because everyone is in control of the services they need.
As I indicated last week, I wanted to write about a specific dialog that occurred at the December 4, 2012 California Board of Pharmacy Enforcement Committee meeting. The important exchange came at the end of the meeting during the catchall agenda item called “General Discussions” when topics that are not on the agenda can be raised by Board members or the general public in attendance.
“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,
Like so many others, I had been patiently awaiting the publication of the U.S. Food and Drug Administration’s (FDA’s) Unique Device Identification (UDI) proposed rules. Now that they are out I’ve been studying them and I think I will have enough to say about them that I will cover the topic in a multi-part series. Today I want to look at just one of the differences between the FDA’s proposed UDI rule for medical devices and their National Drug Code (NDC), the pharmaceutical unique identifier. The NDC structure was first conceived by the FDA back in 1969. For more about the history of the NDC see my essay “Anatomy Of The National Drug Code”.
…a comprehensive exploration of the intersection between healthcare supply chains, track and trace technology, standards and global regulatory compliance
DISCLAIMER: RxTrace contains some of the personal thoughts, ideas and opinions of Dirk Rodgers. The material contained in RxTrace is not legal advice. Dirk Rodgers is not a lawyer. The reader must make their own decisions about the accuracy of the opinions expressed in RxTrace. Readers are encouraged to consult their own legal counsel and trading partners before taking any actions based on information found in RxTrace. RxTrace is not a vehicle for communicating the positions of any company, organization or individual other than Dirk Rodgers.