This week at the Healthcare Distribution Alliance (HDA) Distribution Management Conference and Expo (DMC) the HDA and ValueCentric will provide much more detail around the new master data sharing service they plan to make available in July. The new service—named “Origin”—is intended to provide members of the pharma supply chain with a single directory of master data for all prescription drugs marketed in the United States (see Origin website). That is, it is a database of master data wrapped within a cloud-based service.
Thanks for inviting me to your DSCSA Pilot Party this week. I look forward to visiting you at your Silver Spring home so we can catch up on what’s been happing in our lives recently. I’m glad you are thinking more about the Drug Supply Chain Security Act (DSCSA) lately. I am too.
In fact, I’ve been thinking about how nice it would be if you would fix the broken National Drug Code (NDC) as part of the implementation of the DSCSA. It’s really not very hard to do. You already laid out and tested the path that needs to be followed when you implemented the Unique Device Identification (UDI) numbering system for medical devices a few years ago.
There is a not-so-secret situation that has been festering for years in the internal IT systems of many companies in the U.S. pharma supply chain. In the past, nobody liked to admit it, but most would, because the full extent of the problem was hidden away from public view. It was an internal problem mostly affecting only internal systems.
The problem was that the quality of the local master data was poor. Master data is the data that companies hold in internal databases to describe their trading partners (customers and suppliers), products (their own and those of other companies), contract parameters (pricing, authorization, terms and conditions, etc.), and facilities, etc.
“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,
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.
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.
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.