After creating your role hierarchy, you can then populate it with individual users.
If an external LDAP system stores the site’s user information, map users or groups of users from that system to IMPAX. If you are mapping a single user, you must first create an IMPAX user to map to. (If you are mapping groups of users from the enterprise LDAP system, IMPAX automatically creates these users when they log into IMPAX for the first time.)
 | Note: You cannot add more than 1500 users to one role. For situations in which one role must have more than 1500 users, create sub-roles to divide the users into. The sub-roles could, for example, be alphabetical groupings of user names. |
To create a user
From the Configure drawer menu
, select Users and Roles.In the navigation pane, right-click the role to add the user to and select Add User.
A user is created and selected. The role is the user’s primary role.
In the details pane, under the User bar, switch to the Information tab.
Type the Name of the user.
Do not include the following special characters in user names, particularly if planning to map the user from the enterprise LDAP server: = , + < > # ; \ @
Type the Login ID for the user.
Do not include slash (/) or backslash (\) characters in the Login ID. If planning to map the user from the enterprise LDAP server, this login is temporary. If integrating with IMPAX RIS, ensure the login ID is the same as that used for IMPAX RIS.
Type a Password for the user.
Note:
All passwords must meet the password policy criteria established by the system administrator.
Type the Alternate Names for the user.
Enter the DICOM-formatted family name, given name, middle name, name prefix, or name suffix, to be used for matching against Requesting, Referring, or Performing Physician names. Enter one name per line.
Type the Email address for the user.
If required, type the Company, Address, and Phone Number for the user.
The user is defined and inherits the preferences from its parent role. You can also define specific preferences for the new user, if required. The changes are saved automatically when you switch context.
You can now create a default study access rule to restrict user access to his or her own studies.