Mapping Environment IDs for Front Office Scanning - Integration for Epic - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Essential - Standard - Premier

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

The Front Office Scanning integration uses environment IDs from Epic to determine the Application Server and data source to use. If Epic passes the integration an invalid or blank environment ID, then the integration displays an error to the user and fails to launch.

The Front Office Scanning integration requires environment IDs to be mapped in EpicIntegrations.config. The EpicIntegrations.config file must reside in the same directory as obepicfosXx.dll.

Note:

EpicIntegrations.config contains many settings. Front Office Scanning uses only the environment ID mappings and these settings: PreventEpicLinks, PreventLinkTypes, and AllowLinkTypes. Front Office Scanning uses the Epic FOS XML configuration file for all other configuration settings.

To map an environment ID to an Application Server and data source, see Front Office Scanning Differences in Epic.

  1. Create the EpicIntegrations.config file using the EpicIntegrations Configuration utility if it does not already exist. See Creating the EpicIntegrations Configuration File.
  2. Copy EpicIntegrations.config to the directory where the obepicfosXx.dll is installed.
  3. Open EpicIntegrations.config and map environment IDs as described in Mapping Environment IDs in the Configuration File.
    Note:

    Do not use XML comments in the EpicIntegrations.config file for Front Office Scanning. Comments interfere with the application's ability to read the file.