The mixed practice

A clinic handling horses, cattle and small animals accumulates a particular problem: one animal’s history is split across the veterinarian, the farrier and the trainer, and the split is where things get missed. The hoof abscess noted two months ago and the behavioral change the trainer mentioned are exactly the two facts that would have made this morning’s exam shorter.

What V.E.T.S. carries for this is a patient history typed by clinical service rather than a single free-text log, and the range of services is the part that matters to a mixed practice.

That list includes modalities a small-animal-only system would not bother carrying, and it treats certificates and identification as record types with their own update procedures rather than as notes. Health certificates and identity are regulatory artifacts, and a practice that has ever had to reproduce one under time pressure knows why that distinction is worth having in the schema.

Florence is the minion mapped to medical care, patient history and prescriptions, across 7 page contexts.

Follow one of these calls end to end →

The breeding operation

Breeding decisions rest on lineage, on recorded outcomes, and on the judgment of whoever has been doing it longest. The third of those is the one that does not survive a retirement.

In V.E.T.S. lineage is not a text field. astp_VETS_Animals_PedigreeTreeAddLineageSire and astp_VETS_Animals_PedigreeTreeAddLineageDam are separate, explicit operations against a pedigree tree, with astp_VETS_Animals_PedigreeTreeDeleteLineage to unpick them and astp_VETS_Animals_PedigreeTreeMobile to read the tree standing in front of the horse.

Recording sire and dam as distinct operations against a tree makes the pedigree queryable structure rather than a printed page. The presence of a delete operation alongside the two add operations says something quieter and more useful: the tree is expected to be corrected over time, not merely filled in once.

The reproductive work has its own surfaces too. astp_VETS_PatientHistory_ViewAsGrid_Reproduction and astp_VETS_PatientHistory_ViewAsGrid_Reprobreedingconnection present breeding history as its own grid, with embryo records and ovarian scan handling alongside them. This is the part of veterinary work that is most repetitive measurement, and it is treated as such.

Breeding also has an end that most systems treat as somebody else’s problem. Selling is 27 procedures across 7 tables here: atbl_AnimalSales_isForSale marks availability, atbl_AnimalSales_AuctionBids records bids against the animal itself, atbl_AnimalSales_SalesImages holds the photographs a buyer looks at, and atbl_AnimalSales_ConfigDetailsOwnership carries the ownership detail a transfer depends on. A sale is records against the same animal whose pedigree is described above — not an export to a listing site and a hope the two stay in step.

The farrier

A farrier’s round covers many barns and many horses. Each animal has its own requirements and its own correction history, and that knowledge lives in one person’s head until they are injured, retire, or simply cannot place one horse among hundreds.

The farrier module is the clearest evidence in the system about where this software expected to be used.

Four fifths of the module is built for a phone in a barn aisle rather than a desk afterwards. The evaluation itself is configurable rather than fixed: atbl_Farrier_Eval, atbl_Farrier_EvalItems, atbl_Farrier_EvalOptions and atbl_Farrier_EvalValues let a practice define the assessment structure it actually uses, and astp_Farrier_ChangeEvalResoucesSpeciesRef scopes that structure by species.

A phone still needs a hand, and a farrier holding a hoof has neither to spare. Drive Mode answers that: one tap on the microphone in the minion panel, and you can ask out loud and hear the answer back with the hoof still in your lap. It is conversation, not dictation into the evaluation. How Drive Mode and minion routing work →

Photographs and video attach to the evaluation rather than to a folder somewhere adjacent to it, through atbl_Farrier_EvalFilesImages and atbl_Farrier_EvalFilesVideos. The hoof and the note about the hoof stay together.

None of that is a farrier feature. The same eight tables appear four times over — farrier work, animal performance, riding lesson progress, and clinical detail on a service record — 54 across the platform. What a farrier defines for hoof assessment, a trainer defines for performance and a practice defines for its own clinical questions, on identical machinery. Why configuration lives in rows rather than code →

Two things follow. A substitute picking up the round is a permissions question rather than an act of archaeology. And when the farrier records a concern, the veterinarian sees it against the same animal, because both records were attached to the same animal identity when they were made.

How one barn is shared without sharing the next →

The livestock manager

A commercial cattle operation tracks health events, nutrition, weight and market readiness across thousands of animals at several locations. The usual failure is that each of those lives in a different system and nobody has time to cross-reference them by hand.

In V.E.T.S. the herd is a first-class object rather than a saved filter over a list of animals. It has its own tables for membership, for geographic location, and for ownership.

atbl_VETS_HerdsOwnership is the one worth pausing on. Ownership gets its own table, with add, change and delete operations, because cattle are frequently co-owned and because a herd’s ownership can change without a single animal moving. That is a modeling decision plenty of systems skip, and the operations that skip it end up tracking ownership in a spreadsheet beside the software.

Whole-herd actions exist as actions. astp_VETS_Animals_MoveEntireHerd, astp_VETS_Herd_UpdateLocation, astp_VETS_HerdWeight and astp_VETS_TeamDoc_Tasks_CreateHerdTask mean moving a herd or raising a task against one is a single operation rather than three thousand repetitions of a single-animal one.

Lassie is the minion mapped to herd management and grouping, across 5 page contexts.

Which minion answers on which screen →

The riding school

This one tests the claim at the top of the page, because a lesson barn is not doing veterinary medicine at all. It sells instruction, on animals it owns, by instructors it schedules. If the platform were a veterinary product with extras bolted on, this is where it would run out.

It does not. Lessons are 33 procedures across 12 tables, with atbl_Lessons_Instructors and atbl_Lessons_Lessons carrying the scheduling.

That table is the argument in miniature. Nobody writes it speculatively — the green pony and the sharp gelding are not interchangeable, and neither are the people put on them. Somebody who runs a school asked for it, and it was modeled rather than approximated.

Lesson progress uses the same eight-table evaluation family as the farrier. A school defines its own rubric, and the video of a rider at week two attaches to the assessment that judged it. The machinery does not know it is being used for teaching rather than hoof care, and does not need to.