Making proprietary systems agree
Most of my platform work comes down to one problem: many parties, each running its own system, in several countries, needing one contract they can all trust.
The US standard
At Adents I designed the blueprint for the Verification Router Service within the Healthcare Distribution Alliance (HDA) workgroup, alongside SAP, TraceLink and rfxcel. It became the adopted industry standard for product verification interoperability, used by the entire US pharma supply chain and implemented by every solution provider. Almost the whole story is interoperability: making many proprietary systems answer the same question the same way.
A whole country
At LSPedia I designed and delivered the national traceability platform for Bahrain. It is live in production and used by the country's entire pharmaceutical supply chain. The customer is the state; the users are a whole industry, from manufacturers to the pharmacies at the end of the chain.
Connectors, everywhere
The same problem followed me through every platform. Adents Prodigi depended on connectors into customers' systems. At Optel I built Skybridge, the connector-management module for the Verify platform. At LSPedia I designed OneScan integrations with SAP, MS Dynamics, Epic, HubSpot, QuickBooks, TraceLink and rfxcel, plus trading-partner verification through the NABP and MedPro APIs.
Many regulators at once
At Optel the Verify platform ran on five continents under several regulatory regimes at the same time, and I doubled its compliance scope to cover India, Bahrain and China.
What keeps me in this work is making products work together despite everything that stands in the way. In regulated supply chains, those synergies end up protecting people.
- Adopted industry standard
- Live nationwide
- HDA workgroup
- Connector platforms
- 5 continents