A PIMS built for the road, not adapted to it.
We're building OpenVPM around the road day: routes, households, medicine, billing, and communication in one workflow. Each clinic can shape it to the way its team works.
The workflow should feel like it was designed from the passenger seat.
Mobile practice is not a smaller version of a hospital. It starts with the route, treats the household as the stop, and keeps the clinical, financial, and communication work moving with the vet.
- Step 1
6:00 AM
Before the first driveway
Confirm the address and arrival window, then review the record before the engine starts.
- Step 2
8:30 AM
At the front door
One household can mean three patients, handling notes, and a pet who has disappeared under the bed.
- Step 3
11:45 AM
At the kitchen table
Finish the SOAP, estimate, invoice, and follow-up while the visit is still fresh.
- Step 4
2:30 PM
Between stops
Return messages, track samples and referrals, and know what medication is left in the vehicle.
- Step 5
7:00 PM
After the last call
The goal is a closed chart, a sent invoice, and no second shift at the laptop.
The goal is not a generic PIMS that happens to fit on a phone. It is a mobile-native workspace that can be tuned down to one clinic's service area, language, policies, and way of practicing. The ledger below marks the foundation and the roadmap.
One flexible foundation. A distinctly mobile PIMS.
The shared core keeps records, finances, and inventory coherent. The mobile-practice layer is where ambitious house-call teams can help shape what comes next.
The foundation available to preview
One household, every patient
Multi-pet client and patient records keep history, allergies, vaccines, and weight trends connected.
Chart while the visit is fresh
Responsive SOAP notes, vitals, prescriptions, manual labs, and treatment plans work in a connected browser.
Close the financial loop
Estimates, invoices, balances, and configured payment workflows can be evaluated before leaving the visit.
Know what was dispensed
Inventory levels, lots, expirations, and supported dispense deductions are available, with physical reconciliation still required.
What we want to build with mobile vets
A schedule that understands geography
Service zones, drive time, arrival windows, route sequencing, and live rerouting built into the day.
A workflow that survives dead zones
Offline read and write, queued changes, thoughtful conflict handling, and background synchronization.
Communication from the road
Automated en-route updates, client arrival tracking, and practical communication between stops.
The tools around the PIMS
A practical ecosystem for labs, e-prescribing, accounting, payments, and the tools a mobile practice chooses.
What mobile & house-call 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 day starts with a route, not a waiting room
The schedule should understand service areas, drive time, arrival windows, and the best order for the day. That geographic model is central to the mobile-practice roadmap.
The household is the appointment
One stop may mean three patients, one shared conversation, and separate clinical plans. The workflow should preserve that context without turning the visit into duplicate data entry.
The visit should close before the engine starts
Chart, plan, invoice, collect, and send follow-up while the medicine is fresh. Connected workflows support that loop today, with resilient field work as the next layer.
The vehicle is a treatment room and pharmacy
Stock, lots, expirations, dispensing, and restocking should follow the vehicle. Practice inventory exists today; vehicle-level tracking is part of the mobile roadmap.
The workflow belongs to the clinic
A solo house-call vet and a multi-vehicle team 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 worksBilling & Invoicing
Itemized estimates, invoices, balances, and payments.
See how it worksPatient Management
Weight trends, allergy alerts, multi-pet households.
See how it worksClient Communications
History, portal, email, and activated SMS workflows.
See how it worksUse OpenVPM your way.
Self-host the full open-source PIMS for free, or let us run it for you. Same software, your choice.
Run OpenVPM on your own infrastructure. You operate security, backups, email, messaging, payments, model providers, and production validation.
- Full source under the AGPLv3 license
- All source modules and the documented API
- Docker or Vercel deployment paths
- Bring your own database, email, SMS, and AI keys
Common questions
Is OpenVPM ready for a solo mobile vet?
OpenVPM is available as a controlled pilot for connected house-call workflows. Records, scheduling, estimates and invoices, and inventory can be evaluated from a responsive browser after a fit review.
What does a configurable mobile PIMS mean?
The product direction is a shared OpenVPM foundation with a mobile-practice operating model: routes and service areas, household visits, field charting, mobile billing, communication from the road, and vehicle inventory. Each clinic should then be able to configure its terminology, templates, roles, pricing, communications, and policies without becoming a separate software fork.
Can I work offline or optimize my route?
No. OpenVPM requires a reliable connection and does not provide offline charting, queued synchronization, route planning, or travel optimization.
Can I bring my own tools?
Self-hosters can configure their own infrastructure, email provider, and optional model key. That does not mean every tool connects today: external labs, e-prescribing, accounting, and arbitrary integrations are not included by default.
Can I keep a multi-pet household together?
Yes. One client record can connect multiple patients, with each patient's history, allergies, vaccines, weight, and clinical records kept separately. Route-aware household scheduling is not available.
Can I invoice and take payment before I leave?
Estimates and invoices can be completed in the connected browser. Configured online card payment workflows require Stripe Connect; offline payment capture and automatic synchronization are not available.
Does inventory track what is on each vehicle?
Not yet. OpenVPM tracks practice inventory, lots, expirations, and supported dispense deductions, but it does not maintain separate vehicle stock or route-based restocking.
Related reading
Veterinary Client Communication: Test the Whole Follow-up Workflow
Follow one fictional client request from intake to a resolved reply. Test contact preferences, review, delivery failures, ownership, and duplicate sends before choosing a shared inbox.
Read moreMobile 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 moreOpen-Source vs. Closed Veterinary Practice Software: What You Need to Know
A plain-language guide for practice owners: what open-source veterinary PIMS actually means, how managed hosting changes the cost equation, and who it's for.
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 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.