Why document management is moving inside the EHR, and what it takes to get there

Editor’s note: This is the first of three articles, powered by Digital Health Insights and sponsored by Quoris, examining how health systems are modernizing document management, from the strategic case for EHR-native platforms like Epic Gallery to the operational realities of executing a successful legacy DMS migration.

The ancillary chart has a new home

For most of healthcare’s digital era, clinical data lived in two separate worlds. The core EHR handled roughly 75 percent of structured patient information (e.g. orders, results, notes, medications, etc.), while an external layer of document management systems (DMS) housed everything else: scanned paper records, specialist PDFs, historical imaging files, and decades of ancillary clinical content that didn’t fit neatly into discrete data fields. Systems like OnBase and OpenText became the connective tissue of this arrangement, and for a long time, the dual-vendor model was simply how enterprise healthcare IT worked.

That era is closing. The emergence of native EHR content management capabilities, such as Epic Gallery, has made a single-ecosystem document strategy not only possible but also financially and operationally compelling. For the first time, health systems can bring their entire clinical document footprint inside the EHR, eliminating the fragmentation that has defined enterprise content management for two decades. CIOs who once accepted the multi-vendor DMS arrangement as a permanent condition of the landscape are now asking a different question: How do we get there?

The answer is more complex than it first appears. But understanding what the journey requires and what can go wrong is the foundation of successful migration.

The case for native infrastructure

The operational calculus driving this shift is not subtle. Every external DMS represents a separate vendor contract, a distinct hardware or hosting arrangement, a dedicated upgrade and patching cycle, and an interface connection that must be actively maintained. When the third-party server goes down for scheduled maintenance or unexpected reasons, it doesn’t just affect document viewing. Bottlenecks occur across every workflow that touches that system: incoming faxes, active scan beds, lab result routing, patient registration. In an environment wired around real-time care delivery, a single-point-of-failure in the document layer carries disproportionate consequences.

Consolidating into a unified, EHR-integrated content management suite eliminates that vulnerability. Clinicians no longer exit their primary workflow window to launch a separate application and wait for it to initialize before reviewing an external care history. Documents are simply there, inside the EHR. The downstream effects on clinical efficiency are meaningful, but the more immediate win for IT leadership is structural: fewer vendors, fewer contracts, fewer interfaces to maintain, and a document layer that shares the same uptime guarantees as the EHR itself.

There is also a market reality that healthcare IT leaders should understand. Legacy DMS vendors are not actively invested in helping their customers leave. Contractual obligations don’t disappear, but urgency does. Support for migration projects often moves slowly, sometimes through offshore channels, but on the vendor’s timeline rather than the health system’s. Hosted customers may find themselves waiting a year or more for migration while the clock on their legacy contract keeps running. Selecting a specialized data migration partner rather than relying on the incumbent vendor to facilitate its own replacement has become a strategic necessity, not a preference.

What modern data extraction actually requires

Planning a migration to a native EHR multimedia repository involves four strategic dimensions that should inform vendor selection, architecture decisions, and project scoping from the outset.

Velocity and project throughput. Some health systems wait as long as six to eight months just to begin their extract, transform, load (ETL) migration after contract execution. A prolonged extraction timeline is not a neutral inconvenience but carries real financial cost in the form of ongoing legacy licensing, operational drag, and deferred consolidation benefits. Programs that can expedite data exits by processing large backlogs without sacrificing fidelity are a genuine differentiator, and leaders should probe prospective vendors on concrete throughput benchmarks, not projected timelines.

Parallel processing architecture. Perhaps the most common CIO concern in this conversation is operational impact. A migration that throttles live fax ingestion, disrupts active scanning workflows, or degrades real-time provider data access will generate clinical and administrative friction that reverses any goodwill the project was intended to create. The gold standard is an extraction that runs in parallel, isolated from active operations, with continuous monitoring and the ability to dynamically adjust throughput. During a well-executed migration, frontline staff (e.g. providers, clinicians, and IT personnel) should experience nothing. The migration should be transparent to the organization, not a project IT is visibly managing around.

Infrastructure deployment flexibility. Organizations vary considerably in their cloud posture. Some operate in fully hosted environments; others maintain on-premise infrastructure behind local firewalls. The extraction framework should adapt to the client’s environment rather than requiring PHI to be moved into a third-party staging environment before migration begins. A credible partner can operate securely within either deployment model, meeting the health system where it is rather than imposing architectural preconditions.

Security and network containment. In an era of escalating third-party data breaches, the architecture of the extraction itself is a security decision. A zero-egress model, in which every byte of protected health information remains within the customer’s secure environment throughout the migration, should be the baseline expectation. Equally important is the composition of the delivery team. Proprietary, direct native-layer extraction tools backed by a domestic engineering team eliminate the vulnerability surface introduced by third-party software wrappers or offshore data handling.

Beyond lift-and-shift: The intelligent ingestion imperative

The most consequential mistake IT teams make in planning a document management migration is treating it as a file-copy operation. Moving content from a legacy DMS to a native EHR multimedia layer is not a simple matter of transferring files from Server A to Repository B. The architectural differences between the two environments are significant enough that a naive migration can produce an outcome that looks complete on paper but is functionally broken at the point of care.

The central problem is orphaned documents. Legacy DMS platforms accumulate millions of records over decades of continuous operation, files that carry patient metadata but have lost their active encounter or order-level link to the primary EHR. These records exist in the system and carry indexing information, but they simply can’t be found by clinicians at go-live because the native EHR multimedia layer requires discrete order-level mapping to render a document. A blind data dump transfers those files intact but makes them completely invisible.

Intelligent ingestion addresses this directly. Rather than transferring records as-is, a well-designed ETL pipeline programmatically analyzes historical metadata, cross-references multi-point patient identifiers such as name, date of birth, MRN, and reconstructs critical encounter-level links prior to ingestion. Records that were effectively stranded in the legacy system are reconnected to their clinical context before they are written into the new repository. Clinicians can find everything. The historical chart is complete.

A complementary discipline is targeted content pruning. Most legacy DMS environments contain 20 or more years of accumulated content that has no active clinical value: administrative records, supply chain documentation, superseded workflow artifacts. Migrating this material wholesale degrades performance in the new repository and transfers technical debt rather than eliminating it. The more rigorous approach defines a strict active clinical window for native ingestion, routes the remaining compliance footprint to a cost-effective, immutable active archive, and ensures the new EHR-integrated content layer is populated with records that clinicians actually need.

Laying the foundation for what comes next

The consolidation of DMS into native, EHR-integrated content layers is the future of health system IT strategy. Organizations that complete this transition well will eliminate meaningful technical debt, reduce licensing overhead, close a significant business-continuity vulnerability, and deliver a clinical document experience that is seamless within the EHR rather than dependent on a separate application that may or may not be available when a provider needs it.

But getting there requires more than a clear destination. The mechanics of a legacy DMS extraction including the pipeline architecture, data validation protocols, encounter-level reconstruction work, and security model, determine whether a migration delivers on its promise or creates a new category of operational problems at go-live.

In the next article in this series, we step onto the engineering frontlines to deconstruct what a successful extraction and conversion program looks like in practice, from the first query against a legacy index table to the moment the last document renders correctly in the native web BLOB (binary large object) storage layer.

About the author

Max Lyons brings 16+ years of healthcare IT experience, with deep expertise in enterprise content management, intelligent document processing, and large-scale clinical data migrations. At Quoris, he leads the data services portfolio with a consultative approach focused on helping health systems move critical content cleanly, completely, and with confidence.

About the sponsor

Quoris is a global healthcare IT firm with more than 26 years of experience helping health systems get more from their clinical and operational technology. Its FastLane program offers accelerated extraction and conversion services for data headed to Epic Gallery from any environment, hosted or on-premise. FastLane works alongside your Epic team, and is led by Gallery-accredited, veteran DMS professionals who work directly inside your network, with no data leaving your environment and no third-party tools introduced.