EEGer allows users to export session data from the system in a variety of ways. The most common way to export session data is as a Consultation Export file (ECE). This will allow other EEGer users to download and install the file, creating a copy of the session on their own system.

Consultation Exports allow session data to be reviewed by a mentor or a supervising clinician as if it was run on their own system. Export files are also extremely helpful for troubleshooting purposes. They allow our support staff to review session data and provide suggestions to address possible issues.

Creating an EEGer Consultation Export (Instructions for Sender)

  1. Navigate to Files>Consultation Import/Export>Export Consultation Data from the top toolbar on the main screen of EEGer.
  2. Select the Client ID to view a list of recorded session data by protocol class. Each session should have a Raw and Summary file. It is recommended to select both types of files for a session when creating an export.
  3. Select the sessions to export using the site and date information to identify the correct session files. Selected sessions will display with red text and can be deselected by clicking again.
  4. Once the correct sessions are selected, click OK at the bottom of the screen to create a Consultation Export file.

    Note: If many session files were selected, it can take several seconds for the file to be created.

  5. Once the file is created, EEGer will report where it was saved on the computer. If the export was not successful, EEGer will inform the user and report an error message.

    Note: EEGer is set to export files to the computer’s desktop or C:\EEGer\Exports by default.

  6. Locate the file on the computer. This file can then be attached to an email, moved to a file sharing service, or copied to an external storage device.

By default, EEGer encodes Consultation Export files for compliance purposes. When the export file is created or installed, it will be shown with a series of alphanumeric characters instead of the client’s name. This helps protect confidential client information when sent over the internet or between EEGer users.

When a Consultation Export file is installed, it will create a new Client ID containing all of the transferred session data for review. If the session data is meant to be imported into a matching Client ID and not encoded, the sender must complete these steps before creating an export file:

  1. Navigate to Options>EEGer Configuration Options>HIPAA from the top toolbar of EEGer’s main screen.
  2. Uncheck 6 Encode Client ID on Consultation Export.
  3. Click Close preferences window at the bottom of the window to save and return to EEGer’s main screen.
  4. Create the Consultation Export file as normal.

Installing an EEGer Consultation Export

To begin the installation process, the Consultation Export file most be moved onto the computer. If the file was sent via email or an online file sharing service, it should be downloaded onto the computer before following the instructions below. To make the file easy to find, we recommend placing it on the computer’s desktop.

  1. Ensure that the EEGer Security Dongle is connected to the computer, then open EEGer.
  2. Navigate to Files>Consultation Import/Export>Import Consultation Data from the top toolbar of EEGer’s main screen.
  3. The Windows File Explorer will appear. Navigate to where the export file is saved on the computer and open the file.
  4. Once an export file is opened, a new window will appear listing its contents. Select the files to import by clicking on them. Entries highlighted in red will be selected.

    Note: To quickly select all session data, click the protocol class at the top of the window.

  5. Click OK to begin importing the selected data. After a few moments, EEGer will report whether the installation was successful or not.

  6. To view the imported session data, navigate to the main screen of EEGer and press Select Client. Choose the imported Client ID to load it into the system. Session data can then be reviewed or replayed as normal.
Knowledge Base Article Tags: