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: