Expressive RFID data access policies for the Pharmaceuticals supply chain

548 views

Published on

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
548
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
16
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Expressive RFID data access policies for the Pharmaceuticals supply chain

  1. 1. Expressive RFID data access policies for thePharmaceuticals supply chainMiguel Pardal, Mark Harrison, Sanjay Sarma, José Alves MarquesConsulting
  2. 2. Traceability queries
  3. 3. http://trakchain.net/
  4. 4. US Pharma supply chain
  5. 5. Threats• Prevent illegitimate products from enteringthe supply chain• Returns of counterfeit or stolen products inreplacement of legitimate products through awholesaler• Criminal wholesalers orpharmacists/pharmacies.
  6. 6. US Pharma numbers• 1,400 Manufacturers• 70 Distributors– Big 3• 166,000 Pharmacies
  7. 7. DataMatrix & RFID• You can have both 2D barcodes and RFID– GS1 compatibility layer• Industry has chosen barcodes foritem level identification
  8. 8. Point-of-Dispense AuthenticationEuropean model
  9. 9. European Stakeholder Model“ensuring patients have access to safe medicines”
  10. 10. ESM Euro Hub
  11. 11. Document-based electronic Pedigree“US” modelCA, FLDPMS
  12. 12. Network-centric electronic PedigreeEPC IS
  13. 13. Prototype
  14. 14. Data capture screen
  15. 15. Manufacturer viewThe manufacturer can see its own events andthe receiving event of the distributor
  16. 16. Distributor viewThe distributor can see all the history prior toacquisition of the drug and its own events.
  17. 17. Pharmacy viewThe pharmacy sees all the chain-of-custodyevents only for the product they receive
  18. 18. PoD vs DeP vs NeP
  19. 19. Classification
  20. 20. Capture storage
  21. 21. Capture cost
  22. 22. Query cost
  23. 23. DeP required secure connections
  24. 24. PoD and NeP secure connections
  25. 25. Conclusions• PoD is the most lightweight approach– stores less information– limited number of secure connections• DeP stores the most data– partial pedigrees– requires 10 times more secure connections• NeP is a middle ground between PoD and DeP– stores more data than PoD– semi-centralized architecture minimizes secure connections– same infrastructure – EPC IS and the EPC network – can supportmultiple applications– start with PoD and later evolve to full pedigree
  26. 26. Q & AThank you!Miguel.Pardal@ist.utl.ptTrakChain:Quantifying traceability...

×