How One Veterinary Network Closed Its PACS Support Gap
How a six-clinic veterinary group fixed orphaned studies, a broken PIMS interface and an untested backup by moving to 24/7 vet PACS support.
Proper vet PACS support rarely gets bought because someone read a brochure. It gets bought after a specific bad week. This is a composite account — assembled from patterns RAD365 sees repeatedly across veterinary environment assessments, with details changed and no real organisation identified — of a six-clinic veterinary group with one specialty referral hospital, roughly 34,000 imaging studies a year, and an imaging operation that everyone assumed was fine until it demonstrably was not.
Scope note: RAD365 operates veterinary imaging infrastructure — connectivity, PIMS integration, archive integrity, uptime and vendor management. We do not read or interpret studies. Nothing below concerns clinical interpretation.
Four failure modes, every time
In RAD365 veterinary assessments the same four problems recur: a PIMS interface that was never fully mapped, manual patient entry at the modality, storage with no headroom plan, and a backup nobody has restore-tested. This group had all four, and had no idea it had any of them.
March: the study that wasn't there
A surgeon at the referral hospital asked for a CT series taken at one of the branch clinics eleven months earlier. It was not in the archive. It was, eventually, found on the modality's local disk, under a patient name spelled two different ways and attached to no owner record at all. The study had never routed. Nobody had noticed, because nothing in the environment was configured to notice.
The practice manager did what practice managers do and asked how many others there were. The answer took a fortnight to establish and came back at just over four hundred — studies present on a modality and absent from the archive, accumulated over roughly three years. Most were routine radiographs of no ongoing consequence. A handful were not.
April: the person, not the system
The group's imaging worked because of one practice manager at the main hospital who had taught herself DICOM out of necessity. She configured new modalities, re-pointed nodes when the network changed, chased the ultrasound vendor when studies stopped sending, and manually re-mapped the PIMS interface after every practice-management upgrade. She had not taken uninterrupted leave in two and a half years, and she had recently started applying for other jobs.
This is the single most common structure we find in veterinary groups, and it is a continuity risk disguised as a success story. Everything she knew existed in her head. There was no asset inventory, no node map, no runbook, no escalation contacts written down anywhere. Documented veterinary IT support exists precisely so that a resignation is an inconvenience rather than an event.
May: the backup that had never been restored
The nightly backup job had reported success for twenty-two consecutive months. When the group finally ran a restore test, the job was found to be backing up the application server and a configuration directory — but not the image archive volume, which had been moved to different storage during a hardware refresh eighteen months earlier and had never been added back to the job definition.
The job was green the whole time. Green is not the same as tested. This is the most consistently under-appreciated risk in small-practice imaging, and the test that reveals it takes an afternoon.
June: doing the arithmetic
The group's finance director worked out what the situation was actually costing, and the numbers changed the conversation.
| Cost line | Before | After 12 months of managed support |
|---|---|---|
| Imaging incidents per month | 9–14, mostly self-reported | 2–4, mostly detected by monitoring |
| Orphaned studies | ~400 backlog, growing | Backlog reconciled; near-zero new |
| Inter-clinic image transfer | Email, USB, phone calls | Shared archive, routed automatically |
| After-hours cover | One manager's mobile | Staffed engineer shift, SLA-bound |
| Restore capability | Untested for 22 months | Quarterly tested, results recorded |
| Cost predictability | Break-fix hourly, variable | Flat monthly fee |
July to September: what the transition actually involved
The group engaged RAD365 for veterinary PACS support across all six locations under a single contract. The work ran in five phases, sequenced site by site so no clinic lost imaging capability during the change.
- Discovery and inventory. Every modality, DICOM node, AE title, interface and archive path across six sites, written down for the first time. Two modalities were found sending to a node that no longer existed.
- Monitoring deployment. Alerting placed on DICOM associations, routing queues, PIMS interface message flow and storage headroom per site, with thresholds tuned to each clinic's actual baseline rather than a generic default.
- Identity and worklist fix. Modality worklist enabled everywhere so technicians select a patient rather than type one. This single change is what stopped new orphaned studies appearing, and it was configured through a managed veterinary DICOM gateway for the two units whose firmware could not query the PIMS directly.
- Archive consolidation and reconciliation. The 400-study backlog matched back to patient records where possible, the remainder documented and quarantined. Backup redefined to include the archive volume and restore-tested before sign-off.
- Runbooks, escalation and SLA start. Per-site runbooks, a named escalation matrix, severity definitions written in clinical terms, then a six-week shadow period alongside the practice manager before formal SLA commencement.
The following March: what changed
The practice manager still runs imaging locally, still knows the modalities better than anyone, and now does it with an inventory, a runbook and a rota behind her. She took two consecutive weeks of leave in February, and the group's imaging ran without her — which is the outcome that actually mattered.
The referral hospital gets prior studies from branch clinics automatically instead of by phone call, which shortened the practical path from booking to comparison more than any software change would have. The overnight emergency caseload has engineer coverage rather than a manager's mobile number. And the reconciliation exercise produced something unexpectedly valuable: a written retention policy, sized storage and a tested restore, none of which existed before. The wider workflow layer sits under veterinary workflow management, which the group adopted in the second year.
What this composite is meant to show
Nothing in this account required a new PACS platform. The group kept its software. What changed was the operating model around it: detection instead of self-reporting, documentation instead of one person's memory, staffed coverage instead of goodwill, and a tested restore instead of a green tick. That is what vet PACS support is, and it is why the diagnosis at most multi-site veterinary groups is the same as the diagnosis here.
Why RAD365 can make this claim
RAD365 is a physician-owned global operations partner running imaging infrastructure for hospitals, imaging centres and veterinary networks. Our veterinary engineers work vendor-agnostically across the modality and PACS platforms in general, specialty, emergency, equine and exotic practice; we staff real engineer shifts overnight, at weekends and on public holidays; and we work on a flat monthly fee against a written SLA. We are an infrastructure team — we keep the imaging environment running and leave every diagnostic judgement to your clinicians.
Vet PACS support: frequently asked questions
Vet PACS support basics
What is vet PACS support and how does it differ from human medical PACS support?
Vet PACS support is the operational management of a veterinary imaging environment: DICOM connectivity from radiography, ultrasound, CT and dental units, integration with practice information management software, archive and storage oversight, backups with restore testing, monitoring and incident response. The engineering is largely the same as the human side; the context differs. Veterinary environments carry species and breed metadata, patient identity is owner-linked, PIMS replaces the hospital RIS/EHR, sites are smaller and rarely have on-site IT, and regulatory framing is state practice-act and contractual rather than HIPAA.
Which companies specialize in PACS support services for veterinary practices?
The field is small. Most PACS support firms are built around hospital environments and treat veterinary work as an adjacent case, which shows up in PIMS integration and in after-hours expectations for emergency and specialty practices. RAD365 runs a dedicated veterinary imaging operations practice covering general, specialty, emergency, equine and exotic settings — infrastructure and connectivity only. We do not interpret studies.
How do I set up and maintain a PACS system in a small veterinary clinic?
Start with the modalities and how each will send: DICOM node configuration, AE titles, and a worklist so patient identity is selected rather than typed. Then decide the archive — cloud or on-premise — and a retention plan sized to real annual growth. Then the PIMS interface, mapped field by field including species, breed and owner linkage. Then a backup with a scheduled, recorded restore test. Then monitoring and a named escalation path. Maintenance is mostly those last two done consistently.
What imaging formats and modalities should vet PACS support systems be compatible with?
At minimum DICOM across digital radiography and CR, ultrasound including cine loops, CT and MR where present, dental and intra-oral units, endoscopy and fluoroscopy where used, plus JPEG and video capture from non-DICOM devices routed through a gateway. Equine practice adds portable and field units with intermittent connectivity. Good support handles the awkward cases — dental sensors and older ultrasound heads are where conformance gaps usually appear.
How can vet PACS support improve diagnostic accuracy and workflow in an animal hospital?
Indirectly but materially, by removing the failure modes that corrupt the record. Worklist-driven patient identity eliminates typed-name mismatches and orphaned studies. Reliable routing means prior studies are present at the point of comparison. Verified archive integrity means a series from two years ago is actually retrievable. Consistent PIMS linkage means the imaging record and the clinical record refer to the same animal. RAD365 improves the conditions for accurate reading; the reading itself is your clinicians' work.
Growth, multi-site, and outgrowing the setup
What are the signs a veterinary practice has outgrown its current PACS setup?
Studies that exist on a modality but not in the archive. A growing folder of orphaned or misnamed studies. Staff emailing or hand-carrying images between locations. Storage warnings that get dismissed rather than planned for. A PIMS interface that someone re-maps manually after every software update. A backup nobody has restored. And the definitive one: a single person who is the only reason imaging works, who has not taken uninterrupted leave in two years.
How does veterinary PACS integrate with practice information management software (PIMS)?
Usually through an HL7 or API interface that pushes patient and visit data into a modality worklist and returns study availability to the PIMS record. The mapping must cover the veterinary-specific fields — species, breed, sex, age, owner linkage and the practice's patient identifier scheme — and it must be re-validated after PIMS upgrades, which is where most silent breakages originate. Where a PIMS offers no interface, a DICOM gateway with a locally maintained worklist is the reliable fallback.
Can veterinary PACS support cover multiple clinic locations under one contract?
Yes, and that is the arrangement that resolves most multi-site pain. One contract, one escalation path, one severity framework, one archive strategy, with site-specific runbooks recording each location's modalities, network and named contacts. The alternative — a separate arrangement per clinic — reproduces exactly the coordination problem that prompted the group to consolidate in the first place.
What should a multi-location veterinary group look for in a PACS support partner?
Genuine multi-site experience rather than one clinic repeated; a single consolidated archive strategy with per-site access control; PIMS integration expertise for the specific product in use; staffed after-hours coverage if any location handles emergencies; documented per-site runbooks; consistent severity handling regardless of site size; a flat fee that scales predictably as clinics are added; and explicit data-ownership and exit terms covering every location.
Should a growing veterinary practice choose cloud or on-premise PACS?
For most growing multi-site groups, cloud or hybrid wins, because a shared archive removes the inter-clinic transfer problem entirely and shifts capacity planning to the provider. On-premise remains defensible where connectivity is unreliable, where very large CT volumes make egress costly, or where a specific PIMS integration demands local proximity. A hybrid — local cache for speed, cloud for archive and disaster recovery — is the common answer for equine and mixed-practice groups.
Downtime, emergencies, and compliance
How much does veterinary PACS downtime cost a specialty or emergency hospital?
The direct number is easy to underestimate and easy to compute for your own practice: multiply average imaging-linked revenue per hour by the hours lost, then add the rescheduled cases that never return. For a busy specialty or emergency hospital the direct figure typically dwarfs the annual cost of proper support after a single significant incident. The indirect costs — deferred diagnostics, referral relationships, staff overtime reconciling records — usually exceed the direct ones.
What after-hours emergency imaging support should a vet PACS provider offer?
If the practice images overnight, the provider must staff overnight: an awake engineer holding the runbook, authority to restore routing or archive access without waiting for business hours, monitoring on DICOM associations and storage rather than a server ping, and a documented escalation path into the modality and PACS vendors. An out-of-hours ticket queue is not emergency support for a hospital that runs emergency cases.
What security and compliance considerations apply to veterinary imaging data?
HIPAA generally does not apply to animal patients, but the obligations do not disappear — they arrive through state veterinary practice acts, client confidentiality duties, contractual terms with referral partners and insurers, payment-data rules where imaging is billed, and privacy law covering the owner's personal information attached to every study. Practically that means role-based access, encryption in transit and at rest, audit logging, controlled remote access for support engineers, and a documented breach-response plan.
How long should veterinary imaging records be retained and archived?
Retention is set by state practice-act requirements, commonly in the three-to-seven year range after the last visit, with longer periods where litigation, insurance or referral obligations apply and separate rules for minors' owners in some jurisdictions. Practically, most groups retain imaging longer than the statutory minimum because prior comparisons have clinical value. What matters operationally is that the retention policy is written, the storage is sized for it, and retrieval from the oldest tier has actually been tested.
Switching providers and pricing
What happens during onboarding when switching veterinary PACS support providers?
Discovery and inventory of every modality, node, interface and archive across all sites. Monitoring deployment with thresholds tuned to each clinic's baseline. Runbook authoring and an agreed escalation matrix. Reconciliation of orphaned and misnamed studies. A verified restore test. Then a shadow period alongside existing staff covering at least one full cycle including an after-hours window, before formal SLA start. Four to eight weeks is typical; multi-site groups run longer and should be sequenced site by site.
What's a fair flat-fee pricing model for veterinary PACS support?
One scoped from real inputs — number of locations, modality count and mix, annual study volume, archive size and location, PIMS product and interface count, and the coverage window required — producing a fixed monthly fee against a written scope and SLA, with change control for anything outside it. Fairness shows in two places: adding a clinic has a known incremental price, and a bad incident month does not generate a surprise invoice.
Get a free PACS assessment
Talk to a RAD365 PACS engineer about coverage, migration, or interim support for your environment. No obligation, no sales pitch.
Get a free PACS assessment →