File formats
The files the Rx Tracking modules write and read, for developers who produce them for the modules or consume them from the modules. Every file the modules write for a record is stored with that record, with its SHA-256, and served unchanged afterwards (Frozen documents and the hash chain).
| File | Direction | Written or read by | Stored on |
|---|---|---|---|
EPCIS 1.2 XML (EPCIS-<document>.xml) | written | the outbound DSCSA document of a delivery or a return to a supplier | dscsa.document (file_ids) |
| EPCIS 1.2 XML from a supplier | read | Import EPCIS on a receipt or purchase order | dscsa.epcis.import, then the inbound dscsa.document |
T3 report PDF (T3-<document>.pdf) | written | the outbound DSCSA document | dscsa.document (file_ids) |
| Package ledger and license register CSV | written | the monthly and on-demand retention exports | dscsa.retention.export |
| Trace response zip | written | Respond on a trace request | dscsa.trace.request |
| Owner export zip | written | the 3PL add-on's owner records export | dscsa.owner.export |
- Outbound EPCISThe EPCIS 1.2 file of a shipment, and the writer's input contract.
- Inbound EPCISWhat a supplier's file has to be, what is refused, and what the reader returns.
- T3 reportThe layout of the T3 PDF.
- CSV exportsThe package ledger and license register, the trace response and the owner export.
Related
- DSCSA documents: the same files as users see them.
- Sample files: a supplier EPCIS file and its DataMatrix scans to try an import.