Universal Connector
The animal-care industry runs on capable systems that cannot talk to each other. A veterinary practice, a shelter, a licensing office, a reference laboratory and a breeder registry each hold part of one animal’s life, in different schemas, different terminology, different units, and under different rules about who may see what. The Universal Connector is the single boundary at which that fragmentation stops.
It is platform infrastructure, not a product. No urSynergy application owns it, and every one of them is a peer consumer through the same layer. That rule exists to stop the ecosystem recreating internally the silos it was built to remove.
Every new pair is another integration
Connect a practice-management system to a laboratory and you have built one integration. Add a shelter platform, a licensing system and an accounting package and you are maintaining ten, each with its own authentication, its own field names, its own retry behaviour and its own copy of the business logic. The burden grows with the pairs, not with the systems, and the logic drifts apart in every copy.
The alternative is one boundary that every system meets. Vendor behaviour stops at an adapter; everything past it speaks canonical objects and canonical events. Connect once, translate once, normalize once, preserve the source, and route only where authorized.
Three questions, three authorities
A datum arriving from outside raises three separate questions, and the connector answers none of them itself. It routes each to the layer that owns it, which is what keeps a second taxonomy and a second unit system from growing at the boundary.
USAT1024
What is this?
The concept registry — 42,318 concepts, and the terms, relationships, jurisdictions and authorities behind them. A vendor's body_weight, patientWeight and Wt resolve to one concept without any of them being overwritten.
USTAT
Who says so?
Row-level attribution: who acted, in what role, under what authority, in which tenant, from which system, how verified. It travels with the value rather than being reconstructed later.
Measurements
What does this number mean?
Units and dimensions, and the refusals. 22.4 lb, 10.16 kg and 10,160 g are one measurement; milligrams per decilitre and millimoles per litre are not interchangeable, and the engine says so.
Normalization is an interpretation layer, never a rewriting of history. The laboratory that produced a result, the clinic that ordered it, the value and unit it actually sent, and the rules used to translate it all survive in the record. urSynergy does not become the authority for a fact merely by transporting it.
A refusal is a result, and it travels
Ask the measurement engine to convert milligrams per decilitre into millimoles per litre and it declines, because that crossing needs the analyte’s molar mass and no general engine can know it. Most integration layers treat that as an error to route around. Here it is a result with a name, carried across the boundary with the value still in its original unit.
The reason is narrow and worth stating. A value that quietly passes through unconverted, wearing the label of the unit it was supposed to be converted into, is indistinguishable from a successful conversion — and it is how a wrong-dimension number enters somebody else’s clinical system looking correct. Values in the wrong unit do not look wrong. They compare wrong.
The same discipline governs identity and authorization. Two records that merely resemble each other are not merged; the ambiguity is returned. Two systems that disagree are not resolved by accepting whichever synchronized last; the conflict is held for adjudication, with both representations intact. And data that cannot be safely mapped is quarantined with its full source payload rather than forced into the canonical record.
Being connected grants nothing
A system that can reach urSynergy is not thereby entitled to what urSynergy knows about an animal. Every protected exchange carries the basis on which it was permitted to move: the acting person, the relationship they hold, the purpose of use, and the grant behind it. Downstream processing cannot detach the information from that basis.
A free-text reference to an authorization is not an authorization. It is a claim, and the connector treats it as one: it is retained for audit and it confers nothing. The grant it points at must resolve, and it must still be in force, or the exchange is refused with a reason somebody can act on.
Deliberate non-goals
Replace systems that work
No clinic, shelter, municipality or breeder is asked to abandon functioning software as a condition of interoperating. A connector exists so that they do not have to.
Erase the original
Source values, units, identifiers and locale are preserved beside the normalized form. An external identifier never becomes the canonical identity of an animal, a person or an organization.
Assume every system is right
A connected system is a source, not an authority. Conflicts are adjudicated with provenance and source authority weighed, not settled by recency.
Promise exactly-once delivery
Across systems urSynergy does not control, delivery is assumed at-least-once and made safe by idempotency. Claiming otherwise would be marketing rather than engineering.
Not open, and this page says so
The Universal Connector is under construction. There is no public API today: no endpoint, no sandbox, no developer credential, no connector registry and no certification programme. A page describing those as though they existed would be a complete-looking front for something that has never run, which is the specific failure this architecture was written to avoid.
What does exist is the boundary itself, in code and under test: the manifest contract and its check against the live terminology registry, the capability model that derives what a connector can actually do rather than trusting what it declares, the authorization context that travels with a protected exchange, and the measurement layer that transports a refusal instead of hiding it. A veterinary practice-management integration framework is built and awaiting its first live practice.
Structurally excluded, not merely unbuilt
Two things will not appear later. Connector access is not a mechanism for selling animal records, and interoperability is not gated behind a commercial licence to the terminology standard the translation depends on. Those are revenue-architecture decisions rather than a stage of the roadmap.
If you build software the animal-care industry runs on and want to be part of the first cohort, get in touch. The useful conversation right now is which records actually need to cross, and under whose authority — not an integration date.