Must I use a Pulse interoperable partner for DSCSA?

Pulse simplifies ATP directory and regulator communications for many trading partners. DSCSA compliance itself is met through interoperable EPCIS exchange with authorized trading partners—whether or not you use Pulse directly.

Can I use TracePharma if my wholesaler mentions Pulse?

Yes. TracePharma ingests wholesaler EPCIS via SFTP, AS2, and HTTPS presets while Pulse directory integration is on our roadmap. Many customers run TracePharma for L4 operations today.

When will TracePharma join the Pulse partner program?

Pulse API certification is planned; we do not publish a go-live date yet. Subscribe to demo updates or contact sales for roadmap briefings.

Integrations / NABP Pulse

Integrations · NABP Pulse

TracePharma and the Pulse interoperable partner ecosystem

NABP Pulse connects regulators and authorized trading partners. Many DSCSA solution providers integrate with Pulse. TracePharma interoperates with those vendors at the EPCIS transport layer while Pulse directory API certification is on our roadmap.

Pulse partner program → Request a demo →

What Pulse provides

→ ATP profile, license verification, and trading partner directory
→ Regulator trace requests and interoperability communications
→ API integrations with 15+ listed solution providers

TracePharma today

→ Not yet listed as a Pulse-certified interoperable partner
→ Interoperates with Pulse-listed vendors via AS2, SFTP, HTTPS EPCIS presets
→ Pulse directory API integration is on the product roadmap

Roadmap · not yet certified

Pulse API certification roadmap

TracePharma is not yet certified as a Pulse interoperable partner. We do not publish a go-live date. Customers can run L4 EPCIS operations today via direct partner transports while we complete Pulse API certification work.

Planned capabilities when certified

→ Pulse trading partner directory lookup from tenant partner authorization workflows
→ ATP license verification against Pulse-sourced credentials before inbound EPCIS acceptance
→ Regulator trace request intake and status sync where Pulse APIs support interoperability communications
→ Optional Pulse-listed vendor handoff metadata on outbound EPCIS for partners expecting directory-backed routing
→ Tenant-visible Pulse connection health on Integration Health (planned—mirrors existing AS2/SFTP monitors)

Until certification ships, use wholesaler presets and Pulse-listed vendor pages for EPCIS-layer cutover today.

Pulse-listed vendors with TracePharma pages

TraceLink → LSPedia → InfiniTrak → Advasur → Gateway Checker → UniTrace (Systech) → Axway → OPTEL → SAP ATTP → rfXcel → TrackTraceRx →

Also see PMS, wholesaler, and compare pages.

NABP Pulse FAQ

Must I use a Pulse interoperable partner for DSCSA?: Pulse simplifies ATP directory and regulator communications for many trading partners. DSCSA compliance itself is met through interoperable EPCIS exchange with authorized trading partners—whether or not you use Pulse directly.
Can I use TracePharma if my wholesaler mentions Pulse?: Yes. TracePharma ingests wholesaler EPCIS via SFTP, AS2, and HTTPS presets while Pulse directory integration is on our roadmap. Many customers run TracePharma for L4 operations today.
When will TracePharma join the Pulse partner program?: Pulse API certification is planned; we do not publish a go-live date yet. Subscribe to demo updates or contact sales for roadmap briefings.

Evaluating Pulse and TracePharma together?

We'll explain EPCIS-layer cutover today and what Pulse certification will add when it ships.

Request a demo