Simplified Scanning for Registration - 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

You can configure the Front Office Scanning integration to use two different Epic FOS XML configuration files: one for registration contexts, and one for non-registration contexts. This approach allows you to configure a simpler experience for registration scanning.

To determine whether a user is scanning from a registration context, the Front Office Scanning client checks for a RecordID entry from Epic. If Epic provides a RecordID entry, Front Office Scanning uses the configuration file created for registration contexts. If Epic does not provide a RecordID entry, or if an alternate configuration file is not present, then Front Office Scanning uses the standard configuration file (EPICFOSCONFIG.xml).

To create a separate configuration file for registration:

  1. Copy the EPICFOSCONFIG.xml file.
  2. Append .registration to the name of the new file, keeping the .xml extension.
    For example, if the original file is named EPICFOSCONFIG.xml, then the new file should be named EPICFOSCONFIG.registration.xml.
  3. Make sure both configuration files reside in the same location.

    The Front Office Scanning client first makes sure the EPICFOSCONFIG.xml file exists before checking for EPICFOSCONFIG.registration.xml. The client checks the following locations (in order of precedence):

    • The location specified for the EpicConfigFile registry value. (See Moving EPICFOSCONFIG.xml.)

    • The location of the Front Office Scanning executable.

  4. Modify the new configuration file (EPICFOSCONFIG.registration.xml) as needed for registration contexts.