Keyword Mapping File (Recommended) - Integration for Epic - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Essential - Premier - Standard

Integration for Epic
Platform
OnBase
Product
Integration for Epic
Release
Foundation 23.1
License
Essential
Premier
Standard

The third option uses a keyword mapping file. This option is a best practice because keyword names can vary in Epic and OnBase. The keyword mapping file is a good reference on how keywords are mapped between the two systems. It also allows you to set default values for keywords when a document is scanned.

Any keyword not included in the mapping file will still be mapped if there are identical names in both systems or if the hard-coded values are used.

To use keyword mapping:

  1. Open the sample epickeywords.txt file located in the same directory as the Hyland Integration for Epic installer.
    Note:

    When you deploy the Scan Acquisition Server using the installer, this file is copied to the same directory as the Scan Acquisition Server files. Configure the sample file before running the installer to ensure the deployed copy is already configured.

  2. In the file, add a line for each keyword being mapped. Use the following format: 
    Epic Key Name, OnBase Keyword Type Name

    For example:

    Patient External ID, Patient ID
    Patient Name, Patient Full Name
    Note:

    Keyword and Keyword Type names are case-sensitive.

  3. To specify default values for OnBase Keyword Types, see Mapping Default Values. For example, you may want to set a specific Keyword Value on all documents scanned using the Scan Acquisition Server.
  4. To map OnBase Keyword Types to the name of the scanning server or user, see Mapping Keyword Types to Server & User Name Variables.
  5. Save the file to a network share location accessible by all scan stations (recommended) or to a local workstation.
  6. Ensure all scanning users have permissions to read the file.
  7. For each workstation installation, configure the EpicIntegrations.config file so that the FilePath setting in the <Mapping> element contains the full path to the mapping file. See FilePath.