
At a recent GS1 discussion group meeting one of the moderators acknowledged that they need to create a clear explanation for exactly what EPCIS is. I’ve never been very impressed with GS1’s ability to explain their own standards at a high-level for non-technical readers. They do a great job of explaining them at the minutia-level, but that’s the problem. Non-technical people who must make decisions about GS1 standards probably get bogged down in that minutia and end up not really understanding what it is, why it is significant, and why they should use it. Too much technical documentation exists on how to apply EPCIS, and not enough documentation on the why.
Continue reading EPCIS Explained

Since my last essay about the Russia Crypto-Code (a.k.a., Crypto-Tail) (see “
Over the weekend I skimmed through the many responses the FDA has received for their ‘Product Identifiers Under the Drug Supply Chain Security Act Questions and Answers’ draft guidance (see “
Congratulations, you’ve just connected to the EU Hub and you are authorized to begin uploading production data ahead of the February 9, 2019 deadline. It’s been a long road. Most pharma marketing authorisation holders (MAH) report taking six months from initial onboarding application to authorization. Now what?
Most regulations dictating the application of unique identifiers on drug packages also dictate specific data be encoded into a machine-readable barcode, and human readable text. The purpose of the machine-readable unique identifiers is obvious–to allow computers to read the product’s unique identifier quickly and accurately. The purpose of the human-readable unique identifier is less well-understood. Many believe it is to allow manual entry of the barcode contents when the barcode is unreadable for any reason. Others believe it is
I attended the FDA’s New NDC Format Public Meeting last Monday where I presented my open letter that was last Monday’s RxTrace essay (see “