• Stuart Corby

Track.one & Accenture

Proof of Concept presentation to the Center for Supply Chain Studies on DSCSA & Blockchain

May 1st 2018

Centre For Supply Chain Studies
DSCSA and Blockchain - Johns Hopkins University

Beyond Compliance: DLT Implementation Lessons Learned and Supply Chain Optimization Potential


Stuart Corby, Authentag - CEO / CTO

Rob Torti, Authentag - COO / CFO

Nishant Modi, Accenture - Manager, Supply Chain and Blockchain


Our Proof of Concept demonstrates how an immutable chain of custody and granularity of ownership reshapes logistics. We’ll discuss current advances enabled by FDA led GS1 GTIN and PI labeled unique identification and demonstrate full ‘creation to end use’ traceability through all parties in the supply and use network.

Our presentation will analyze current real usage of FDA Regulated GS1 GTIN + PI uniquely labeled traceability and how full traceability is already being used for more than just FDA compliance. Real examples then illustrate why a distributed ledger and blockchain are necessary and suitable as part of a traceability solution for the Pharma industry.

Team’s vision

An open source, community owned and community governed digital ledger that manages transactions and traceability for all actors within the pharma community, whilst providing isolated data protection and multi-party contracts that can adapt overtime with regulatory and business needs.

Target audience

This presentation is for any interested party that wants to see an existing use of full traceability for product and patient protection, regulatory compliance and financial benefit. It requires no prior technical knowledge as it uses real-life examples to illustrate the compelling reasons distributed ledger technology is a viable solution to fulfill the aims of DSCSA whilst conforming to Anti-Trust regulations,

DSCSA focus

Track.one framework:

Open source: Release to open source the technical, functional and protocol specifications for the pharma community to comply to the DSCSA by connecting through a commonly held distributed ledger, performing full traceability whilst maintaining discrete, protected data pools.

Necessary Technical Services: Build, or commission the building of, the technical services necessary for the distributed ledger to function, including a financial service that will distribute revenues from use of smart contracts on the distributed ledger to those technical service providers, financial backers of the Distributed Ledger Community and the creators of smart contracts used on the Ledger.

Access: Designate audit services companies to control access to the community.

Competence: Designate technical audit services companies to ensure technical competence to join the community.

Implementation: Designate implementation service providers technically competent to assist members who wish to join the community.

Governance structure:

IP: Protecting the intellectual property of smart contract creators and facilitating the payment for smart contracts created for use on the distributed ledger.

Competitive Environment: Allowing the community to replace any of the above community services with suitable alternatives at will.

Innovation: Allowing for the adoption of new smart contracts to address all parts of pharmaceutical track, trace, inventory management, and financing.

Pilot demonstrates:

Full traceability of any standard - including GS1 - uniquely labeled items and how this is already altering the way supply networks are managed. How a chain of custody is created and how the DSCSA regulations already provide for serial, isolated control of that history. How full data isolation and protection is maintained, with usable data always within the confines of the signing counterparties.

Technical Features:

Pilot demonstrates a system that is currently blockchain agnostic as it uses the pre-requisite technological building blocks to be serviced by any underlying immutable ledger technology that can deliver the speed and transaction volumes needed for full-scale multi-purpose implementation.

Full adoption comes in 7 (build, operate, transfer) phases:

Phase 1. Cloud-based instance for testing and integration (allows internal verified returns).

Phase 2. Multiple instances that can be cloud or enterprise hosted depending on the need of community member (allows internal verified returns).

Phase 3. Opening up of routing layer to allow externally verified returns (i.e.: you can build or commision your own connections with the community.

Phase 4. Community technical services fully functional.

Phase 5. Validated Smart Contracts other than verified returns allowed (traceability, tax, invoicing, etc)

Phase 6. Governance and voting structure trial period

Phase 7. Hand over of governance control from Track.one to community