An enterprise imaging archive is the system of record for a health system’s images. When it is healthy, nobody thinks about it. When it is not, the effects reach all the way to the reading room. The good news is that most of what puts an archive at risk is predictable, which means it is preventable.
Across the imaging teams we work with, the same handful of themes account for most of the questions we help with. Here are the five that come up most, and the practical habits that keep each one from turning into downtime.
1. Keep your archive services healthy
The highest-impact incidents usually trace back to a receiving or routing service that stops, or studies that do not reach their destination. The earliest warning sign is almost always a rising failure queue.
Watch service status, failure-queue depth, and server load continuously, and set alert thresholds so a backlog reaches you before it becomes an outage. It also helps to separate the noise from the signal: a large backlog of old, already-understood failures can hide the new failure that actually matters today, so keep the queue worked down and resolve the root cause rather than letting it accumulate. Configuring live alerts, whether through the system event log, an email notification, or your own monitoring tools, turns a silent problem into an early heads-up.
2. Stay ahead of storage and capacity
Full temporary folders, full filegroups, and receiving backlogs are some of the most common ways a quiet issue becomes an outage. Enterprise imaging makes this harder than ordinary systems administration, because study sizes vary enormously: a plain radiograph may be a few megabytes while other modalities run into gigabytes per study.
Monitor storage thresholds and alert well before disks reach capacity, not at one hundred percent. Keep purge and replication healthy and running on schedule. Plan capacity ahead of anticipated growth rather than adding storage reactively, especially if your organization is expanding sites or adding modalities. One easily missed detail: when a new modality comes online, compression settings sometimes get overlooked, which sends far more data across the network and into storage than necessary. A quick configuration check catches it.
3. Keep study export and image exchange flowing
Moving studies to downstream systems and exchange partners depends on healthy destinations and endpoints, and those endpoints can change without notice. Many issues that look like an archive problem are really an endpoint, a certificate, or a configuration that changed somewhere else.
Validate destinations after any configuration or endpoint change, and monitor export and exchange status for stalls. It is also worth knowing the tools you already have: outbound retrieves can apply rules that adjust transfer syntax or tags, routing can be load-balanced across node groups and threads when queues build, and single-association options exist for downstream systems that need them. A documented, tested set of destinations makes any change easy to verify.
4. Stay current on a supported version
Upgrades deliver stability, performance, and security fixes. Running well behind can mean living with an issue that a newer release already solved. In our own analysis, a large majority of reported defects on older versions were already resolved in newer releases.
The key is that the upgrade itself is only one part of the process. The smoother path is to slow down up front: review the release notes and the work plan together, test in a non-production environment first, run a mock upgrade to gauge downtime, and confirm who owns backups, downtime communication, and rollback criteria before the production window. A structured testing plan that defines workflows, owners, and clear pass or fail expectations, followed by a support window after go-live, turns upgrades from disruptive events into routine ones. A steady, predictable release cadence makes it easier to plan and to stay current with less disruption.
5. Get more from worklists and the viewer
A large share of day-to-day questions are really “how do I” questions, and in many cases the capability is already there. Worklists in particular reward a little configuration.
Configure worklists to match each team’s workflow, and standardize filter sets per role so everyone starts from the right view. A few habits go a long way: start broad and then narrow, be deliberate with AND versus OR logic because it can make or break a worklist, and use the built-in criteria-performance check before you save so a heavy query does not tax the system. Well-scoped, specific criteria also return results faster. Behind the scenes, keeping database maintenance jobs running keeps the underlying tables indexed and worklists quick to load.
A few habits that prevent most of it
- Monitor services, failure queues, and load, with alerts set before backlogs build.
- Watch storage thresholds, and keep purge and replication healthy.
- Validate export destinations after any change.
- Stay on a current, supported version, and plan upgrades on your terms.
- Configure worklists and filters to your workflow, and standardize them per role.
None of these are complicated. They simply reward a little planning over waiting for something to break.
More from Mach7
Protecting the archive is one part of a connected set of enterprise imaging capabilities. Mach7’s family spans Enterprise Imaging overall, the Vendor Neutral Archive (VNA), the Communication Workflow Engine (CWE), the eUnity enterprise viewer, and AI enablement, with Flamingo as our next offering. Bringing these together is what keeps images moving from pixel to point of care.
This guidance comes from the Mach7 Customer Success team. We run monthly Office Hours for our customers to share practical tips like these and answer live questions. If you would like to talk through any of the habits above, reach out to your account team or contact us at events@mach7t.com.
eUnity is a diagnostic viewer intended to display medical images and associated clinical reports to aid in diagnosis by trained healthcare professionals. Professional and prescription use only. In the United States only, eUnity supports digital pathology whole-slide imaging (WSI) for reference and referral use and is not intended for primary diagnosis. Mammography and digital breast tomosynthesis are not intended for diagnostic interpretation on mobile devices.