← Insights

The same architecture in three regulated verticals

· 7 min read · Dhiraj Chatpar

Operations, healthcare and logistics look unrelated from the outside. From the inside the constraints rhyme.

Three platforms now run in production across three countries: workflow automation for operations, care management for healthcare, and fleet tracking for logistics. Different users, different regulators, different failure modes. The architecture converged anyway.

In all three the first constraint is the same: something must be verified and recorded. A workflow step completed, a caregiver present at a location, a vehicle inside a boundary. The value of the system is not that it performs the action, but that it can prove the action happened.

The second shared constraint is partial failure. A phone loses signal. A carrier rejects a message. A background job times out because the upstream API rate-limited it. Each vertical offered a different way to discover that the expected thing did not occur, and each one required the same response: bounded retry, then escalation, never a silent loop.

The third is access. Healthcare forces the strictest version, where visitor verification and HIPAA-aligned handling are not negotiable. Once that discipline exists, applying it to operations and logistics is comparatively cheap. The reverse direction does not work, which is why the regulated vertical is the useful place to begin.

Three jurisdictions add their own flavour. Data residency in Canada, the UAE and India means physically different handling for what looks like the same record. The architectural answer is to treat the location of data as a property of the data rather than a property of the deployment, so the same code holds in each jurisdiction.