A practical guide for labs that have outgrown their current setup — or want to avoid outgrowing it

‍

Most digital pathology programs don't start with a deliberate infrastructure strategy. They start with a scanner, a shared drive, and the best available workaround for getting images in front of the people who need to review them.

That's not a criticism — it's a pattern. The urgency of getting digital workflows off the ground often outpaces the time available to evaluate long-term infrastructure properly. Labs make pragmatic choices under constraint, and those choices work well enough to delay the harder conversation about what comes next.

But "next" arrives. Slide volumes grow. More users need access. Sponsors ask for image sharing capabilities. A compliance audit surfaces gaps in audit trail documentation. A pathologist flags that it takes too long to download images or navigate from one slide to the next. An IT leader realizes that petabytes of image data are living on unmanaged local drives.

When that moment comes, labs face a decision that's harder to make reactively than proactively: which tier of image management is actually right for where we are — and where we're going?

This article maps the three tiers clearly, names the real tradeoffs at each level, and gives you the framework to make that call with confidence.

The three tiers of image management

Tier 1: File sharing platforms

File sharing platforms — Dropbox, SharePoint, OneDrive, Google Drive, network attached storage — are not image management systems. They are general-purpose file storage and sync tools that labs sometimes press into service as a stopgap when slide volumes are low and workflow demands are minimal.

At small scale, they work. A handful of users downloading a handful of slides occasionally is manageable. But the limitations surface quickly as any one of those variables changes.

The core problem: whole slide images aren't ordinary files.

A single brightfield whole slide image can run from 500MB to several gigabytes. A multiplexed immunofluorescence image can reach tens or hundreds of gigabytes. File sharing platforms require users to download files before viewing them — which means waiting minutes (or longer) for every slide, every session. At any meaningful slide volume, this isn't a minor inconvenience. It's a workflow-stopper.

Beyond file size, the structural limitations of file sharing platforms compound:

• No pathology-specific organization. Files are files. There's no concept of studies, cases, or staining protocols — metadata that pathologists need in context while reviewing. That organization has to be replicated manually in folder structures that become unwieldy and inconsistent.
• No browser-based viewing. Reviewing slides requires downloading them to a local machine, opening a compatible viewer, and working locally. Multi-user simultaneous review is effectively impossible.
• No audit trail. File sharing platforms log access events at a basic level, but they produce nothing approaching the audit trail documentation required for GLP or GCP compliance. There is no record of who reviewed which slides, what annotations were made, or when findings were recorded.
• No access control granularity. Permissions in file sharing platforms are blunt instruments — folder-level read/write access is not the same as role-based, study-level permissioning that CROs and regulated labs require.
• ‍Security risk at scale. Large image libraries on unmanaged shared drives represent a meaningful data governance risk, particularly for labs handling sensitive sponsor data.

‍

Tier 2: IMS-lite platforms

IMS-lite platforms occupy a wide middle ground. The category includes software bundled with whole slide scanners, viewer tools offered as add-ons by analysis platform vendors, and lightweight SaaS products that offer basic image management capabilities without the full enterprise feature set.

This tier represents a genuine improvement over file sharing. Images are streamed rather than downloaded, which resolves the single most painful limitation of Tier 1. Users access slides through a web viewer without local software installation. Basic study organization and metadata management is available. For many labs at early-to-mid stages of digital adoption, this is a meaningful step forward.

But the IMS-lite category has a structural problem that gets harder to ignore as workflows mature: these platforms were not built to be the center of a digital pathology stack. They were built to support a scanner sale, extend an analysis tool's footprint, or serve a more limited use case than enterprise labs eventually need. The gaps that result aren't edge cases — they're predictable limitations of a product designed for a different job.

Where IMS-lite platforms commonly fall short:

• Format and scanner lock-in. Scanner-bundled IMS-lite software is validated for that scanner's proprietary format. Labs that operate multiple scanner brands, or that want to switch scanner vendors, frequently find that their IMS can't ingest images from the new device — or requires a conversion step that adds time and introduces quality risk. Vendor neutrality, in practice, requires an IMS that isn't tied to any particular scanner's ecosystem.
• Limited integration depth. IMS-lite platforms typically offer a viewer and basic storage — but integrations with LIMS platforms, analysis tools, and downstream reporting systems are often shallow, undocumented, or absent. This pushes metadata management and analysis back into manual processes: study information entered twice, results recorded outside the system, handoffs managed by email.
• Compliance gaps. The audit trail, access control, and validation documentation requirements for GLP and GCP workflows are demanding. IMS-lite platforms are generally not built to meet them. Labs that attempt to use these platforms for regulated work often find they're maintaining extensive manual compensating controls to document what the system doesn't capture automatically — an approach that's both operationally costly and fragile under audit.
• Scalability ceilings. IMS-lite platforms are typically designed for modest slide volumes and user counts. Labs that are growing — in scanning throughput, user base, or data volume — frequently hit performance and storage constraints that the platform wasn't designed to accommodate.
• ‍Collaboration limitations. Sharing images with external sponsors, enabling remote review, or supporting multi-site workflows often requires workarounds — if it's possible at all. The collaboration features that CROs and multi-site research teams need are rarely a priority for IMS-lite vendors.

‍

Tier 3: Enterprise IMS

An enterprise IMS is built for the demands of digital pathology at scale. It is not a viewer bundled with a scanner, not a general-purpose file management tool adapted for large images, and not a lightweight SaaS product with a feature list that covers the basics. It is a platform designed from the ground up to be the operational center of a digital pathology workflow — for organizations where that workflow is complex, regulated, high-volume, or all three.

The defining characteristics of an enterprise IMS aren't individual features — they're architectural commitments that shape what the platform can and cannot do:

• Cloud-native, elastically scalable infrastructure. Enterprise image management requires infrastructure specifically built for the size, access patterns, and growth trajectories of WSI data. Cloud-native architecture means storage and compute scale with your needs — you're not provisioning hardware ahead of demand or managing capacity manually.
• Scanner and format agnosticism. A true enterprise IMS ingests images from any scanner, in any format, without requiring conversion or creating a proprietary dependency. Labs can choose scanners based on capability and cost, not software compatibility. This is vendor neutrality in practice.
• Deep, bidirectional integrations. Enterprise IMS platforms connect to LIMS systems, image analysis tools, and downstream reporting infrastructure through documented, validated APIs — not one-off custom integrations. Data flows automatically rather than being moved manually. Pathologists see study context in the viewer. Analysis results return to the IMS. Findings flow to the LIMS for reporting.
• Compliance infrastructure built in. Audit trails that capture every access, annotation, and action. Role-based access controls with study and case-level granularity. Electronic signature workflows. Validation documentation packages for GLP, GCP, and 21 CFR Part 11 requirements. These aren't configurations layered onto a platform that wasn't designed for them — they're architectural features that reflect a deliberate commitment to regulated workflows.
• End-user tools built for pathology work. High-performance browser-based image viewing, efficient navigation for large study sets, annotation and markup tools, figure generation, multi-user collaboration, and reporting — all within a single environment that pathologists and scientists actually want to use.
• ‍External collaboration capabilities. Secure, role-controlled image sharing with sponsors, collaborators, and external reviewers — without requiring local software installation on the recipient's side. For CROs and multi-site research organizations, this is increasingly a table-stakes capability.

‍

Side-by-side: the capabilities that matter

‍

The migration cost argument for getting ahead of the curve

The most common reason labs stay on file sharing or IMS-lite platforms longer than they should is inertia: the current setup is familiar, switching requires effort, and the cost of that effort is visible in a way that the cost of staying isn't.

But migration costs are not fixed. They grow with the data library, the number of users, the complexity of the workflows built around the current platform, and the organizational habits that have formed around it. A migration that would have been straightforward at 50,000 slides is significantly more complex at 500,000.

There's also a compounding productivity argument. Every month spent on a platform that requires manual workarounds, limits collaboration, or slows pathologist navigation is a month of productivity cost that doesn't appear on any invoice. Those costs accumulate silently until the moment a finance or operations leader decides to quantify them — usually during a budget discussion about the migration they're trying to avoid.

The organizations that make the enterprise IMS transition earliest — before the pain is acute — consistently report smoother implementations, faster time to value, and less organizational disruption than those that wait until the current platform becomes untenable.

Making the call: a decision framework for selecting your IMS strategy

If you're trying to determine which tier is right for your organization right now, these questions cut through most of the complexity:

1. Are any of your workflows regulated under GLP, GCP, or 21 CFR Part 11? If yes, the answer is enterprise IMS — full stop. IMS-lite platforms and file sharing cannot meet the audit trail, validation, and data integrity requirements of regulated workflows without compensating controls that are operationally unsustainable.
2. Do you operate or plan to operate scanners from more than one vendor? If yes, scanner-agnostic infrastructure is essential. IMS-lite platforms tied to a specific scanner vendor will create format compatibility problems that grow more expensive to manage as your scanner portfolio expands.
3. Do you share images with external stakeholders — sponsors, collaborators, clients? If yes, you need collaboration capabilities that file sharing and most IMS-lite platforms can't deliver securely or conveniently. Enterprise IMS is the practical answer.
4. Is your scanning volume growing? If yes, model where your volume will be in two to three years and evaluate platforms against that projection, not today's numbers. Migrating at scale is significantly more disruptive than building on the right foundation from the start.
5. ‍Are your pathologists spending time on system friction rather than pathology? If yes, this is the clearest signal that the platform's UX ceiling has been reached. End-user productivity is a legitimate and quantifiable reason to upgrade — and it's often the deciding factor when the operational case for migration is assembled.

The right time to upgrade is before you need to

There's a predictable moment in many digital pathology programs where the accumulated cost of the current platform — in productivity, in compliance risk, in constrained scanner and analysis options — finally exceeds the perceived cost of migrating. That moment is the wrong time to start the evaluation process, because it means the selection decision is being made under pressure, with an urgent need to get off the current platform rather than a clear-eyed assessment of what the next platform needs to do.

The right time to evaluate an enterprise IMS is before the pain is acute. Before the compliance gap becomes a regulatory finding. Before the scanner you want to buy doesn't work with the IMS you have. Before the sponsor asks for image access you can't provide.

The labs that make that call proactively — that treat the IMS decision as the strategic infrastructure choice it is — consistently end up with better outcomes than those that wait.

Curious whether PathcoreFlow is the right fit for where your lab is headed?
Talk to a solutions expert →
Download the IMS Evaluation Checklist →

‍

This article is part of Pathcore's digital pathology resource hub. For related reading, see:

• Everything to Know About an Image Management System (IMS)
• The Complete Digital Pathology Stack: How Scanning, IMS, Image Analysis, and LIMS Work Together
• Why Your IMS Choice Defines Your Digital Pathology Strategy

‍