DSCSA Master Data Hub FAQ: What Spherity’s CARO Customers Ask

Spherity
1 hour ago
2 min read

With the launch of CARO v1.3, Spherity has officially transformed its DSCSA compliance software from a Verification Router Service (VRS) enhancement into a comprehensive Authorized Trading Partner (ATP) master data and communication hub. This upgrade establishes a leading master data layer for the US pharma supply chain, enabling secure, interoperable, and compliance-ready data sharing. It reflects Spherity’s Compliance-as-a-Service (CaaS) vision – automating operational governance to reduce risk and deliver tangible business benefits for pharmaceutical manufacturers, wholesalers, and dispensers.

If you are new to the recent evolution of Spherity’s Master Data hub for DSCSA Compliance, CARO, read our article explaining where CARO is going. Below, we explore the most common four customer questions about Spherity's DSCSA master data and communication hub (and how CARO would respond).

1- How will CARO prevent duplicate records across different supply chain domains?

CARO uses the ATP credential as a unique, VC‑backed identifier to prevent pollution at the source. Records tie back to a single credential when available; for partners without credentials, CARO assigns a unique enterprise ID. Once verified, duplicates are merged with historical associations preserved for DSCSA traceability.

2- How frequently is DSCSA trading partner data updated? Is it near real-time or scheduled?

Credential validation is real‑time against issuer registries (authenticity, revocation). License data refreshes daily or weekly, depending on the issuing body (FDA, state boards, DEA). During any ATP check, CARO cross‑checks cached license data and triggers an immediate recheck or manual verification if stale.

3- Are unverified trading partners records ingested? How are they handled?

Yes. CARO ingests unverified/partially verified records for visibility but segregates and labels them with verification source and timestamp. Unverified ATPs are excluded from DSCSA workflows and automatically rechecked until resolved.

4- Will we get notifications for verification failures or duplicate merges?

Absolutely. CARO provides event‑driven notifications and dashboard visibility for verification failures, duplicate merges, and status changes (e.g., Verified → Revoked). You can initiate workflow actions (request verification/correction via API) and review a full audit trail for regulatory compliance.

Turning Compliance into Competitive Advantage

Compliance is a continuous capability, not a checkbox. Spherity’s Master Data Hub for DSCSA Compliance, CARO, streamlines the process of verifying Authorized Trading Partners (ATP) and monitoring license status. By providing a reliable trading partner master data and communication hub, it enables your supply chain activities to meet both regulatory and business requirements.