Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Bulk importing event codes

Updated on October 9, 2020

New event code configurations can be imported in bulk via an Excel spreadsheet. To import event codes, navigate to Configuration > Event Code on the left side menu and click the “Bulk import” button at the top of the event codes screen.

When the user clicks Bulk import, a new tab opens and the Download Template button is displayed on the top right of the screen. Users can use populate this template with all the needed event code information and then import the Event Codes using the Import event codes button.

The template has a “ReadMe” tab that includes instructions and descriptions of the required data.

  • The downloaded file type is .xslx.
  • Use only first tab (Template) for data entry.
  • Do not delete the second tab (ReadMe) which contains instructions.
  • Do not change the column names.
  • If there are multiple disposition for a single Event Code, enter multiple rows with the same event code metadata. Update disposition information only.
  • After populating the template, the file must be saved in the .csv format before importing (ReadMe tab will be ignored in .csv format).
  • When an event applies to the claim line level the user should populate claim line level resolution actions only; claim level resolution actions will remain blank.
  • When one event code has multiple disposition entries and some are invalid, the event code will be created with correct disposition entries and the invalid ones will not be included.

After populating the template, click the Import event codes button; this opens a new tab. Click the Import codes button.

The user is guided through four steps.

Step 1: Choose a file – navigate to the .csv file and choose it.

Step 2: Map fields – allows users to view and validate existing mapping from the .csv file to SCE. Modifications to the imported mapping may be performed during this step..

Step 3: Import options – users can name the Event code upload case and begin the validation process.

Step 4: Validate and review – SCE runs all the validations and systematically presents the following:

  • Start time: Time the validation process began.
  • Running time: Total time the validation process ran.
  • Valid rows: Total rows in the uploaded excel sheet which are valid and have passed all the validations
  • Invalid rows: Total rows in the uploaded excel sheet which are invalid and did not pass all the validations.

Records with errors are highlighted along with the description of the errors.

Users can choose to correct the errors and reload the event codes or continue the import process. If the user chooses to continue, the system presents a summary of the event code bulk import.

The following statistics are seen:

  • Number of rows in file: This number would show the total number of rows in the file which were processed.
  • Number of valid rows: This number would show the total number of valid rows in the file.
  • Number of invalid rows: This number would show the total number of valid rows in the file.
  • Number of codes imported: This number would show the total number of event codes loaded.
  • For every event code bulk upload, a new case is created in Pending-Approved status. This bulk upload can be approved using the System Manager Work Basket.

  • The errors in the file can always be seen by looking at the attachment and seeing the error file.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us