Preparing the site

If a site has an enterprise LDAP system, we recommend assessing the administration and topology of the directory servers to ensure an efficient configuration of the site. The organization of the LDAP directory must be compared against the logical organization of the PACS users. The key is to determine how well the enterprise LDAP directory matches with the logical organization of users within PACS and if PACS is defined as its own organization. While the PACS user organization and the LDAP directory do not need to match, the LDAP integration is easier if IMPAX models the organization of the hospital's LDAP directory.

Determine the following:

• Do some or all of the PACS users already exist in the enterprise LDAP directory?

• How are users organized within the LDAP directory? Are users departmentalized within LDAP by organizing departments into groups of users in LDAP?

• Are PACS users separated in the LDAP directory from the rest of the enterprise users?

• What groups of users that exist within the hospital enterprise will use IMPAX (such as radiologists, technologists, clinicians, and so on)? How does this match the user organization within the LDAP directory?

• Can the site create new groups within the LDAP directory that would match with the roles in IMPAX, if none exist?

• Is the IT administrator willing to create a group or Organizational Unit (OU) of IMPAX users in the enterprise?

In addition, ensure the following is completed:

• Determine how long the site needs to configure LDAP.

• Request the AgfaAdmin and AgfaUser users (assigned to the corresponding groups) for binding purposes and testing IMPAX default permissions and preferences.

• Have the site provide certificate services (Certificate Authority) on the LDAP server for the Application Server. This is required for the Application Server to communicate to the LDAP over TLS (SSL encrypted channel).