OnBase to Epic Gallery Migration
Fourteen years inside OnBase, and 10 Epic implementations working with Epic HIM for document types, Identity for EMPI, error queues, RightFax integration, 3M and other third-party applications — applied to straightforward and successful Epic Gallery implementations with OnBase document conversions, retention integrity and metadata fidelity intact.
Healthcare organizations running OnBase as their enterprise clinical document management platform are increasingly looking into moving to Epic Gallery. The consolidation promises a simpler stack, better clinical integration, higher efficiency and satisfaction, and reduced licensing overhead — we can make the transition simple by managing both the implementation and the legacy document conversion.
The work we do
Chesapeake Systems has been implementing, customizing, and supporting OnBase environments for Epic, and Epic implementations, for more than fourteen years. That history includes helping design a custom legacy electronic document conversion engine and access to non-converted legacy documents from Epic. We bring clinical document management expertise directly into the Epic Gallery implementation and conversion effort — and we wrap it in the project management rigor that large-scale migrations require: clean governance, disciplined phase gates, transparent status, and the accountability that keeps stakeholders aligned from kickoff through stabilization.
An OnBase-to-Gallery requires a combination of an Epic module implementation and a legacy document conversion to Epic from an OnBase cloud environment. We partner with Epic and your organization to meet all process standards, and bring the expertise needed to be successful.
Who this is for
Health systems actively planning or executing an OnBase-to-Epic-Gallery migration. Organizations in the middle of a stalled migration who need a rescue. IT leaders preparing their OnBase environment for a future migration and wanting to do the cleanup work now. Acquirers inheriting an OnBase installation that needs to be consolidated into an existing Epic environment.
Planning an OnBase to Epic Gallery migration?
Tell us where you are and we'll tell you what a realistic plan looks like — including what usually goes wrong and how to avoid it.
Document conversion isn’t theory for us. It’s a track record.
20M+ documents, one conversion engine
At a five-hospital academic medical center, we corrected a drifting OnBase project to meet four Epic go-live dates — and led the architecture of a legacy document conversion engine that converted over 20 million documents, with a scanned-documents solution that saved the client over $1M.
10 million out of Allscripts
For a three-hospital academic medical center, we corrected the schedule, implemented OnBase on-prem with full business continuity, and converted 10 million documents out of Allscripts for the Epic go-live.
Cloud to cloud, 5 million documents
Managed the conversion of 5 million documents from a legacy OnBase cloud to a new OnBase cloud environment — with HL7 ingestion to Epic — on schedule with a new Epic foundation go-live.
OneContent retired
For a four-hospital system, project-managed the OnBase cloud implementation, the cutover from OneContent, the legacy document conversion, and the integration to Epic.