A healthcare referral and a freight booking have almost nothing in common on the surface. Different forms, different regulations, different people, different stakes. But watch what actually goes wrong in each, and you're looking at the same problem wearing different clothes. That resemblance isn't a metaphor — it's the reason ATG's platform was never really about logistics.
The shape underneath the paperwork
Strip away the domain and every multi-party workflow has the same skeleton. There's an initiating party who starts the process. There are one or more parties who have to act on it. There are documents that need to travel. There's a status that everyone keeps calling to check. And there's a hand-off point where the whole thing tends to stall.
A shipment moves that way: a shipper books it, a carrier moves it, and status has to reach everyone with a stake in it. A referral moves the same way. A primary care practice initiates it, a specialist has to receive and schedule it, a payer often has to authorize it, and records have to travel between all three before anyone can act. Same skeleton, different vocabulary. The referral is a load, the authorization is a document reference, the appointment is a delivery milestone.
Where a referral actually breaks
The thing that stalls a referral is almost never medical judgment. It's the gaps between systems. The referring practice works in one record system, the specialist in another, the payer in a third — and none of them reach into the others. So a coordinator prints, faxes, scans, and calls to move facts across a boundary that software was never wired to cross.
The patient waits. Not because care is unavailable, but because the facts about the referral can't move as fast as the decision to make it. The authorization is "pending" in one system and invisible in the next; the records were sent but nobody can confirm they arrived; the appointment can't be booked until a status lands that has no clean path to travel. Every one of those is a data-path problem dressed up as a delay in care.
Why a bigger portal doesn't fix it
The reflex is to build one system everyone logs into. But each party here has a system of record it will not abandon — the practice's EHR, the specialist's scheduling software, the payer's authorization platform. Those systems hold the authoritative version of what happened, and no one is going to run their clinical or commercial operation inside software another organization controls. Consolidation across organizations doesn't happen in healthcare for exactly the reason it doesn't happen in logistics: it asks everyone to give up what they already trust.
So the answer can't be a replacement. It has to be a connection.
The same connective layer, a different vertical
This is where the architecture carries over cleanly. Veritas by ATG doesn't replace anyone's system or pool everyone's records into a shared vault. It moves the facts about a referral between the parties who need them — authorization requested, records attached, decision returned, appointment set — while each side keeps its own archive exactly where it lives. Status, milestones, and document references travel; the records stay home.
Nothing about that description is specific to healthcare. It's the same thing the platform does for a shipment, applied to a workflow that happens to be a referral. The layer stays neutral, each party keeps its system of record, and the coordinator stops being the human relay between systems that were never designed to speak. Order from chaos — the same order, imposed on a different chaos.
Why "beyond logistics" was always the plan
Logistics is ATG's first vertical because the pain there is acute and legible — the gaps are easy to see and expensive to ignore. It is not the company's identity. The connective layer is vertical-agnostic by design, and healthcare referrals are one of the clearest places that design shows through: same skeleton, same failure mode, same fix.
That's also where the consult → build → connect model earns its keep. A referral network doesn't need a logistics tool bent to fit it. It needs a team that can assess the specific hand-offs where its work stalls, build the connections those hand-offs require, and connect them on a proven layer instead of starting from zero. The architecture is the constant. The paperwork is just the part that changes.
If your operation runs across organizations that all keep their own records — in healthcare, logistics, or anywhere the hand-offs stall — that's the gap Veritas and ATG Consulting exist to close, without asking anyone to give up their system of record.
Start a project