03.01.2014 Views

Pedigree Specification Release Note - GS1

Pedigree Specification Release Note - GS1

Pedigree Specification Release Note - GS1

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

17<br />

18<br />

19<br />

20<br />

21<br />

22<br />

23<br />

24<br />

25<br />

26<br />

27<br />

28<br />

29<br />

1 Usage Guidelines for Creating and Appending Information<br />

to <strong>Pedigree</strong>s (non-normative)<br />

The following usage guidelines provide descriptions of the XML schemas can be used for various<br />

use cases.<br />

1.1 <strong>Pedigree</strong> Flow Initiated by Wholesaler with Product Receipt<br />

Signature<br />

The pedigree flow is described for a sale from a manufacturer to a wholesaler, when no pedigree is<br />

provided by the manufacturer and the wholesaler initiates the pedigree and signs the intial pedigree<br />

for product receipt. The pedigree is then updated for a sale from the wholesaler to a retail<br />

pharmacy DC.<br />

pedigree<br />

shipped<strong>Pedigree</strong> Id=”ShippedPed-2”<br />

documentInfo<br />

serialNumber<br />

version<br />

pedigree<br />

received<strong>Pedigree</strong> Id=” Ped-1”<br />

documentInfo<br />

serialNumber<br />

version<br />

initial<strong>Pedigree</strong><br />

serialNumber<br />

productInfo<br />

itemInfo<br />

transactionInfo<br />

senderInfo<br />

recipientInfo<br />

transactionIdentifier<br />

…<br />

receivingInfo<br />

receivingInfo<br />

dateReceived<br />

signatureInfo<br />

Signature (Wholesaler Signs: Ped-1, Received)<br />

itemInfo<br />

transactionInfo<br />

senderInfo<br />

recipientInfo<br />

transactionIdentifier<br />

…<br />

signatureInfo<br />

Signature (Wholesaler Signs: ShippedPed-2, Certified)<br />

Copyright ©2005-2007 EPCglobal ® , All Rights Reserved. Page 2 of 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!