A field code is used to identify information in the EDI data stream. During processing, data associated with these field codes is stored as a Keyword Value within OnBase.
OnBase is pre-configured to recognize a number of EDI field codes, but your solution may require you to create additional field codes that OnBase does not identify by default.
For a list of all EDI default field codes, see the Default Field Codes chapter.
To create a custom EDI field code:
-
From the OnBase Configuration module, click Import | EDI Field Configuration. The Choose Processor dialog box is displayed.
-
Click Configure. The EDI Field Configuration dialog box is displayed.
Note:The field codes that are displayed may be different, depending on the type of EDI processor you selected in Step 2.
All EDI field codes for this type of EDI processor, including default field codes and custom field codes that have been previously created, are displayed in the Field Name list. -
Enter a name for the new field code in the Field Name field and click Create. To edit an existing field code, select it in the Field Name list and click Settings.
Note:
Default field codes cannot be edited, although their settings can be viewed for reference purposes.
The EDI Field Configuration dialog box is displayed.
Option
Description
Primary XPath
This field contains the XPath to the primary value to be pulled from the EDI stream.
Secondary XPath
This field contains the XPath to the secondary value to be pulled from the EDI stream.
Date Options
This setting determine the date option for the field code.
Note:Although active by default, these options are only functional when a Date Keyword Value is mapped to the field code.
-
Store entire date range: Stores the entire date range in the configured XPath.
-
Store first date in date range: Stores only the first date in the date range in the configured XPath.
-
Store second date in date range: Stores only the second date in the date range in the configured XPath.
-
Store earliest date in date range: Stores the earliest date in the EDI stream as the Keyword Value. This option is only functional when used with a primary XPath.
Secondary XPath Options
This setting determines the secondary XPath option for the field code.
-
Use only if primary Xpath returns no results: The value in the secondary XPath will only be used if there is no value in the primary XPath.
-
Do not use secondary XPath: The secondary XPath will not be used.
-
Combine set of returned nodes with set obtained from primary XPath: Takes each piece of data returned from a node and creates an instance of a Keyword Value or Keyword Type Group for it.
Note:If this option is used in conjunction with a Single-Instance Keyword Type Group, only the data obtained from the primary XPath will be used.
-
Concatenate single result to single result from primary XPath (No MIKG support): Concatenates the results from both the primary and secondary XPaths into one result.
Note:This option is not supported for use with Multi-Instance Keyword Type Groups.
-
Use in place of primary XPath if PATIENT loop exists: The value in the secondary XPath will be used if the PATIENT loop exists in the EDI stream.
Note:When EDI fields are mapped to OnBase Keyword Types that are part of a Multi-Instance Keyword Type Group, only the field's primary XPath is used, regardless of the field's secondary XPath configuration.
Version Options
Select the check box that corresponds to the version of the EDI 835 processor that you are using.
-