Summary
Veterinary radiology workflow now involves a choice between bundled systems, where one vendor supplies the DR hardware, the PACS and the AI tools together, and open platforms that accept DICOM from any manufacturer. For a single clinic the bundle can be the simpler purchase. For an independent radiologist reading for several clinics, each bundle is another login, another viewer and another report destination. NewLumen, the cloud-native veterinary DICOM platform from Asteris, takes studies from any DICOM-compliant modality into one worklist.
What Does a Hardware-PACS-AI Bundle Actually Bundle?
IDEXX gave the trend a current example in January 2026, when it launched the ImageVue DR50 Plus digital radiography system alongside IDEXX Web PACS. In IDEXX's own description, the DR system integrates with the cloud-based Web PACS, the Web PACS viewer uses AI to automate hanging protocols and vertebral heart scores, and cases can be submitted directly to IDEXX radiologists for consultation. Acquisition, storage, viewing, AI and the consult service come from one company and are built to work together.
Whoever the vendor is, a bundle has three layers.
Acquisition. The DR unit captures the study and sends it to the same vendor's PACS by default.
Storage and viewing. The PACS and viewer are tuned for studies from that vendor's equipment. A study from another manufacturer's unit usually arrives as standard DICOM, but whether it gets the same hanging protocol support is something to confirm in writing.
AI. The AI features run inside the vendor's viewer. Whether their output leaves with the study, for example as a DICOM Structured Report, varies by vendor and is rarely stated in a brochure.
A practice that acquires, stores and reads everything inside one vendor's system will not notice any of this. The reader who sits across several of those systems will.
Why Do Independent Radiologists Feel It First?
An independent radiologist's caseload is multi-source by definition. Studies arrive from clinics with different DR manufacturers, different ultrasound units and different CT scanners, and the radiologist needs one worklist, one viewer and one reporting screen for all of them.
When two client clinics sit inside two different bundles, the radiologist reads Clinic A's studies in Vendor A's viewer and Clinic B's in Vendor B's, unless each clinic also forwards its studies by DICOM to a neutral system. That means two logins, two sets of keyboard shortcuts, two hanging protocol setups and two places a signed report has to go. Routing rules, worklist filters and priority flags live inside each vendor's platform, so "STAT first" has to be configured, and checked, once per platform.
The cost is paid in small manual steps: forwarding a study, assigning it to the right reader, confirming it landed. In a teleradiology group those steps repeat for every study from every clinic that is not on the group's own system.
What Three Questions Should You Ask Any Vendor Before Signing?
These apply to every vendor, Asteris included. They surface the commitments that will govern your workflow for the length of the contract.
1. Can I send studies from any DICOM-compliant modality to your PACS and get the same hanging protocol support, AI features and worklist routing for all of them? Ask for the answer in writing. If it is "yes, with some exceptions for other manufacturers' hardware," ask for the list of exceptions. That list describes your daily workarounds.
2. If I cancel, can I export every study and every signed report in standard DICOM format, and how long will it take? Export rights and a timeline belong in the contract. A vendor that hesitates here is telling you how hard leaving will be.
3. Do your AI tools run on studies from any manufacturer's hardware, and does their output travel with the study? An AI feature that only works on studies acquired on the vendor's own unit is tied to the hardware purchase, and it stays behind when a study moves to another system. Ask whether outputs are stored with the study, for example as DICOM Structured Reports, or exist only inside the vendor's viewer.
What Does an Open Platform Change?
An open-platform PACS takes DICOM from any manufacturer and puts every study in one worklist, whatever unit acquired it.
NewLumen is built this way. It runs in Chrome or Edge with nothing to install, and it accepts studies from any DICOM-compliant modality: CR, DR, CT, MR, ultrasound and fluoroscopy. A client clinic connects by sending from its existing imaging equipment over DICOM, and its cases start appearing in the radiologist's worklist. The clinic keeps the hardware it already owns. A referring practice with no PACS of its own can send through NewLumen Link.
The NewLumen worklist has five queue views under one login: All Cases, My Queue, Group Queue, Pending Review and Completed Today. Routing rules match on clinic, modality, body area, priority, time of day and day of week, and they are evaluated in order, first match wins. The same rules cover every connected clinic, so a STAT thorax from a clinic with one manufacturer's DR unit and a STAT thorax from a clinic with another's are triaged the same way.
The AI tools are named for what they do. Priority Triage flags urgent studies in the worklist. Report Assist starts each report from a species-specific template. Prior Comparison surfaces the patient's previous studies when a case opens. None of them depends on which manufacturer's unit acquired the study, and the radiologist reviews, edits and signs every report.
Two boundaries are worth knowing before a demo. The hanging protocols that ship with NewLumen are for canine and feline studies. And on question 2: from the worklist a study can be downloaded, shared by link or sent to another DICOM destination, but if you want a full-archive export, ask Asteris for the process and the timeline in writing, as you would any vendor.
Why Does the Open-Platform Question Go Unasked?
A buying checklist that compares bundles with each other asks which package is most complete and which has a single support line. It has no row for whether the PACS treats another manufacturer's studies the same way, what the export terms are, or whether the AI depends on the hardware. A practice working from that checklist never puts those questions to a vendor. Add the three questions above to whichever checklist you are using. The Asteris guide to cloud and on-premise veterinary PACS covers the hosting side of the same decision.
How Do You Run Your Own Workflow Audit First?
Before any demo, list every modality at every clinic you read for: DR units, CT, MRI and ultrasound, with the manufacturer and the DICOM conformance statement if you can get it. Then write down where each modality's studies land today, how they reach your reading queue, and how many manual steps a study from each source takes.
That document is your baseline. In the demo, test the vendor's system against it. Ask them to populate the worklist with a DICOM study from a modality they did not manufacture. Ask what happens when studies from two different DR manufacturers arrive at the same time. Ask to see the export function, and confirm that signed reports leave with the study.
A NewLumen demo runs in the live platform, on your own study. Bring your modality list and your hardest case, and book a demo.
Frequently Asked Questions
What is ecosystem lock-in in veterinary radiology workflow?
It is what happens when one vendor supplies the DR hardware, the PACS and viewer, and the AI tools, and each part works best, or only, with the others. Replacing one layer then means replacing all three. Independent radiologists are the most exposed, because client clinics in different vendor systems cannot share one worklist, and the radiologist ends up keeping a separate reading setup for each.
Can I use a third-party PACS with DR hardware bought in a bundle?
A DR system that outputs standard DICOM can, in principle, send to any DICOM-compliant PACS. Two things need checking. Ask the hardware vendor whether sending to a third-party DICOM destination is supported under your agreement. Ask the PACS vendor whether hanging protocols, AI features and worklist routing work the same for studies from that hardware as for any other.
How does a cloud-native PACS differ from a cloud-accessible PACS?
A cloud-accessible PACS keeps studies on a server you can reach over the internet, but the viewer or workflow tools still need a local install or plugin. A cloud-native PACS, such as NewLumen, opens every study in the browser with nothing installed. For a radiologist who reads from more than one location, that means any computer with Chrome or Edge and a login is a reading station.
What should I ask a veterinary imaging vendor about their AI tools?
Ask for the name of each AI function, the species and modalities it has been validated on, and where that validation is published. Ask whether it works on studies from any manufacturer's hardware. NewLumen names its tools by function, including Priority Triage, Report Assist and Prior Comparison, and the radiologist reviews and signs every report.
What does a teleradiology group need from a PACS when it reads for multiple clinics?
One login that gathers studies from every client clinic, whatever hardware those clinics own, and routing rules that send each study to the right reader without a coordinator assigning it by hand. NewLumen for teleradiology groups is built for this: five queue views in one worklist, rule-based routing, and a connection to any DICOM-compliant modality.