Evaluate the open foundation before planning a specialty rollout.
OpenVPM has structured records and a targeted API for selected workflows, but it has not been validated as a production system for specialty or referral hospitals. We start with a fit review and do not promise a cutover or integration until the required workflows are proven.
What must be validated for specialty & referral.
These pages describe the needs we are evaluating. They are not a claim that OpenVPM is ready for production use in this setting.
Referral communication is clunky
Referring-vet portals, bidirectional record exchange, and live synchronization are not currently supported product capabilities.
Records aren't built for complexity
Structured SOAP notes exist, but specialty templates, complex diagnostic workflows, and referral-hospital validation require a fit review.
Integrations are impossible
The public REST API covers selected workflows only. External lab, imaging, equipment, e-prescribing, and accounting integrations are not available today.
Relevant building blocks to inspect.
These product areas exist, but together they do not yet make this practice type production-ready.
Medical Records
SOAP, manual labs, Rx, and vaccines on one record.
See how it worksClient Communications
History, portal, email, and activated SMS workflows.
See how it worksPatient Management
Weight trends, allergy alerts, multi-pet households.
See how it worksReports & Analytics
Revenue, appointments, services, and inventory exports.
See how it worksOperational Controls
Controlled-drug ledger, audit records, and clinic roles.
See how it worksCommon questions
Does OpenVPM work for specialty and referral hospitals?
Not as a production-ready system today. Specialty and referral teams can request a fit review, but should not plan a cutover until their workflows and required integrations have been validated.
Can referring vets get records or live updates?
OpenVPM does not currently provide a validated referring-vet portal, bidirectional record exchange, or live synchronization with another system.
Can we integrate specialty equipment, labs, or e-prescribing?
Not through a supported production integration today. The REST API covers selected workflows, not general diagnostic equipment, external labs, imaging, e-prescribing, or accounting connections.
Related reading
Who Owns Your Veterinary Practice's Data? (And What Happens When You Try to Leave)
The AVMA says your practice owns its data. Most PIMS contracts don't agree. A plain-language guide to exit fees, portability traps, and what open-source changes.
Read moreWhy veterinary software should be open
Every other part of the clinic is built on standards. The software that runs it shouldn't be a locked box you rent forever.
Read moreInspect the product without assuming production fit.
The demo shows existing building blocks. This practice type is not production-ready, and live records should not be entered without a separately approved fit review.