Client IDs are like folders used to store session plans and client data on an individual-basis. This allows for a clinician to easily switch between different Client IDs depending on the person who is receiving neurofeedback training.

Client IDs can be created from EEGer’s main screen while in clinical mode. Home Use systems are not able to create Client IDs, as Home Use files are created by the supervising clinician.

To create a Client ID, follow the instructions below:

  1. Navigate to Client>Create Client ID from the top toolbar of EEGer’s main screen.
  2. Enter a codename for the Client ID. This is a short name that can be used to identify this Client ID within the system.
    • This field does not allow for spaces or punctuation and must be within 1-31 characters.
  3. A window will appear where a full name can be entered for the Client ID.
    • This field can be filled with non-identifiable information such as an encoded name/client number for tracking purposes.
  4. A window will appear where a birthday can be entered for the Client ID.
    • This field can be filled with a random date or simply the date that the Client ID is created.
  5. A biological sex selection window will appear. If desired, Unspecified may be used on this screen.
  6. A window will appear allowing a protocol class to be selected for the Client ID. These are like subfolders for storing different types of sessions. The default is BetaSMR.
  7. A window will appear asking if a custom session plan should be loaded for this Protocol Class.
    • Selecting Yes will take the user through the steps of selecting a custom session plan.
    • Selecting No will load the default session plan for the selected protocol class. The session plan can be edited at any time once the Client ID has been created.
  8. If the user has selected to load a custom session plan, they will be prompted to choose the layout and name associated with the custom session plan. Please note that this will only allow selecting a custom session plan if it was created for the same protocol class chosen in Step 6.
Knowledge Base Article Tags: