A PIMS built around the barn, the herd, and the road between them.
We're building OpenVPM around the field day: properties, animals, owners, medicine, and billing in one workflow. Each clinic can shape it to the way its team works.
The workflow should feel like it was built at the barn.
Equine and farm practice is not a species setting inside a small-animal workflow. It starts with the property, understands groups and relationships, and follows the team through the full road day.
- Step 1
6:30 AM
Plan by property
See the barn or farm first, then every patient and owner tied to that stop.
- Step 2
8:00 AM
Work the list once
Review due work, record exams and treatments, and avoid opening the same form twenty times.
- Step 3
11:30 AM
Log medicine where it happens
Capture dose, lot, expiry, controlled-drug details, and withdrawal time before leaving the animal.
- Step 4
2:30 PM
Send the right bill
Separate charges by owner while keeping the property, trainer, and patient history connected.
- Step 5
5:30 PM
Close the road day
Finish notes, imaging follow-up, certificates, and invoices without rebuilding the day from memory after dark.
The goal is not a generic PIMS with an equine template. It is a field-native workspace that can be tuned down to one clinic's language, policies, and way of practicing. The ledger below marks the foundation and the roadmap.
One flexible foundation. A distinctly equine and farm PIMS.
The shared core keeps records, finances, and inventory coherent. The field-practice layer is where ambitious equine and farm teams can help shape what comes next.
The foundation available to preview
Connected individual records
Patient history, allergies, vaccines, vitals, SOAP notes, prescriptions, and treatment plans are available in a reliable browser connection.
Individual estimates and invoices
Connected estimate, invoice, balance, and configured payment workflows can be evaluated one patient at a time.
Inventory with an audit trail
Stock levels, lots, expirations, controlled-substance records, and supported dispense deductions can be inspected.
An open data foundation
The code and schema are public, and supported exports provide a path out of proprietary lock-in.
What we want to build with field teams
Property, barn, herd, and group records
A location-aware model connecting animals, owners, trainers, herds, and the stop itself.
Offline field work
Offline read and write, queued changes, thoughtful conflict handling, and background synchronization.
Route-aware scheduling
Service areas, drive time, stop sequencing, emergency insertion, and live rerouting built into the road day.
Field-specific clinical and billing tools
Withdrawal periods, group treatment, certificates, multi-owner barn billing, and practical lab connections.
What equine & farm changes about the PIMS.
Each practice type gets its own operational model, vocabulary, and defaults. Each clinic can then tune roles, templates, pricing, communications, and policy to the way its team works.
The property is the center of the visit
The farm or barn should open into every animal, owner, trainer, task, and charge tied to that stop. That property-centered model is central to the field-practice roadmap.
One stop can span a herd and five owners
The workflow should move across animals once, preserve the right clinical detail, and separate billing without rebuilding the same visit. Group and multi-owner work belongs in the model.
Field medicine has to survive the field
The record should remain useful under a metal roof or beyond cell coverage, then synchronize safely when the signal returns. We are designing for the reality of field connectivity.
Clinical detail changes with the work
Withdrawal periods, group treatments, certificates, field diagnostics, and species-specific templates belong inside the workflow, not in side spreadsheets.
The workflow belongs to the clinic
A solo equine vet, a mixed-animal team, and a production-medicine practice should share a foundation without sharing the same defaults. Clinic-level configuration is the design principle.
One foundation. Configured for this practice.
Scheduling, records, billing, inventory, and communication share a coherent core. The practice layer determines how those tools are organized, named, and connected for the team using them.
Smart Scheduling
Day and week views, one column per doctor.
See how it worksMedical Records
SOAP, manual labs, Rx, and vaccines on one record.
See how it worksPatient Management
Weight trends, allergy alerts, multi-pet households.
See how it worksBilling & Invoicing
Itemized estimates, invoices, balances, and payments.
See how it worksClient Communications
History, portal, email, and activated SMS workflows.
See how it worksCommon questions
Does OpenVPM work for ambulatory equine practice?
Not as a production-ready equine system today. It can be evaluated in a connected browser, but equine and large-animal workflows require a fit review.
What does a configurable equine and farm PIMS mean?
The product direction is a shared OpenVPM foundation with a field-practice operating model: property-centered visits, connected animals and stakeholders, group work, field medicine, and the road day. Each clinic should then be able to configure its terminology, templates, roles, pricing, communications, and policies without becoming a separate software fork.
Can I use it offline or plan routes?
No. OpenVPM requires a connection and does not provide offline charting, queued synchronization, geographic routing, or travel optimization.
Does it support herd, group, or external lab workflows?
No. Herd and group records, equine-specific workflows, and supported external lab integrations are not available today.
Can a horse's current barn be different from the owner's address?
Not through a dedicated property model today. OpenVPM does not yet connect a patient, owner, trainer, barn, and current field location as separate operational records.
Can I treat or invoice several animals at one stop?
Not through a validated group workflow. Records and invoices are individual today; batch treatment, multi-owner barn billing, withdrawal periods, and group closeout are not supported.
Related reading
Mobile Veterinary Software: A Visit-to-Invoice Demo Checklist
Run a two-animal house call through your next PIMS demo: separate records, one travel fee, unfinished notes, payment choices, and an interrupted connection.
Read moreWho Owns Your Veterinary Practice's Data? (And What Happens When You Try to Leave)
A plain-language guide to veterinary data stewardship, software contracts, export fees, portability, and what open source changes.
Read moreOwn your data: a second PIMS you control
OpenVPM supports reviewed, dry-run CSV imports for selected record types. General live synchronization with an incumbent PIMS is not available today.
Read moreBring us the workflow your current PIMS never understood.
OpenVPM is being built with field teams, from the operating model down to clinic-level vocabulary, templates, roles, and policy. Show us how your day actually works and help shape the PIMS around it.