TracePharma
Integrations / Pharmacy PMS / ScriptPro

Integrations · Pharmacy PMS

TracePharma + ScriptPro

TracePharma exposes a dispense-check API for ScriptPro. Your PMS calls TracePharma before completing a fill; unverified or failed serials block dispense with a logged reason.

Preset: scriptpro HTTPS REST

ScriptPro remains your pharmacy system of record. TracePharma is the L4 traceability hub—receiving wholesaler EPCIS, running VRS verification, and gating dispense through POST /api/v1/pms/scriptpro/dispense.

Inbound interoperability

  • ScriptPro middleware POSTs dispense-check requests with GTIN, serial, and optional barcode fields.
  • TracePharma validates prior verification state or runs VRS when configured.
  • Blocked dispenses return structured reasons for pharmacist workflow and audit.

Outbound & compliance

  • pms_dispense_events audit trail in Filament with list/view per event.
  • Dispenser scorecard with 30-day PMS blocked-reason trends.
  • GET /api/v1/compliance/dispenser-scorecard and pms-blocked-reason-trends for BI.

Typical cutover steps

  1. 1 Enable PMS dispense integration in Tenant Settings.
  2. 2 Configure optional shared secret (X-ScriptPro-Secret) for ScriptPro.
  3. 3 Point ScriptPro dispense-check middleware at your tenant dispense endpoint.
  4. 4 Test with a verified GTIN+serial before production fills.

Best for

ScriptPro interoperability FAQ

Does TracePharma replace ScriptPro?
No. ScriptPro continues to manage prescriptions and inventory. TracePharma provides DSCSA verification and dispense-check gating via API.
What happens when verification fails?
The dispense-check API returns a blocked response with a reason code. The event is logged for FDA 3911 and dispenser scorecard reporting.

Connect ScriptPro in your tenant

We'll walk through inbound preset setup, test receiving, and ACK monitoring on a profile-tuned demo workspace.

Request a demo