cancel
Showing results for 
Search instead for 
Did you mean: 
Brian_Adams
Content Contributor
Content Contributor

[UPDATE: 02/17/2017] - Epic has re-named Epic 2016 to 2017. The name is the only change; all information below still applies. We will be updating our installers to reflect this change, but in the meantime when installing in an Epic 2017 environment, please choose "Epic 2016" within the installer.

We are happy to announce support for Epic 2016 2017, which was released recently.

OnBase 15 and 16 support is available now, and support for 17 will become available when it is released later this year. The build numbers for the currently released versions are as follows:

16 – 16.0.1.63+
15 – 15.0.3.296+
 
If you are currently running an earlier version of 16 or 15, you will still request the appropriate build listed above. For example, if you are running 15.0.2.174, a 15.0.2.x version will not be available and you will need to request the 15.0.3.x build for Epic 2017 support. This is a supported scenario because it is still within the major version so a database upgrade will not be required. You will need to update the Application Server(s) you use for the Epic Integration, as well as the client modules (including Citrix deployments and EPS server for ROI). All other installations of your OnBase system can safely remain on the 15.02.174 build. Installers are available and your first line of Technical Support will be happy to assist you with getting the necessary software.
 
For those upgrading to OnBase 15+ from an earlier version, or those already on 15 but not using the new Document Update Processor (available starting in 15.0.2.141), we strongly urge you to do so. Used in combination with the new Epic Scan Document Maintenance interface, the Document Update Processor will accept HL7 messages (typically an MDM^T08) from Epic when a change is made to a document within Hyperspace. These messages can be configured to perform a Re-Index in OnBase which can change the document type, update keywords, move the document to a different encounter, and more; and/or push the document into an OnBase Workflow where you can configure more elaborate logic and actions on it.
 
Please see the Special Interest Topic webinar which covers this in more detail, including other use cases such as scanning to appointment and encounter on-the-fly.  For more information, please reach out to your Epic Interface TS, your OnBase first line of support, or post in the Forums.