Implementing the DCSA Track & Trace Standard

This is a guide to implementing the DCSA Track & Trace (TNT) standard version 2.2, written for the technical teams of DCSA adopting organizations.

Reference Documentation

To get acquainted with the standard, refer to the introductory Track & Trace standard page.To understand the key concepts, user stories, use cases and data overview of the standard, refer to the Track & Trace documentation page.For an overview of the business processes addressed by the standard, refer to the DCSA Industry Blueprint.To understand the data structures used by the standard and how they can be mapped to your own organization's data types, consult the DCSA Information Model.

Implementing the Standard

To get acquainted with the general principles applicable when implementing any DCSA standard, consult the DCSA API Design and Implementation Principles.To review the reference implementation of the Track & Trace standard, created by DCSA to verify the standard and used for measuring the conformance of adopter implementations, consult the Track & Trace module of the DCSA conformance GitHub repository.
Event Publisher Implementation
To implement the Track & Trace standard API as an event publisher, use your organization's technology stack to implement each endpoint of the DCSA Track & Trace OpenAPI specification page.
Event Consumer Implementation
To consume events published by any provider through the DCSA Track & Trace standard API, use your organization's technology stack to build a backend API client application using the DCSA Track & Trace OpenAPI specification page.You can use a DCSA conformance sandbox as a counterpart in your development, since it allows you to easily test the most relevant scenarios that your application needs to support.As an alternative, you can also use directly the corresponding API specification page of one of the publishing organizations whose events you intend to retrieve through the DCSA standard API.👉Important note: While implementing the standard, run conformance periodically and use the Conformance Tool as a compass to guide the implementation. Don't wait until implementation has been finished and then run Conformance.