Use this presentation with Section 2 of the Deployment Workbook. Provisioning Users Use this presentation with Section 2 of the Deployment Workbook. This presentation is provided by Kryptiq. You may wish to customize it for use in your organization. V 4.13 | June 2012
This section of the workbook explains… The difference between staff users of secure messaging and Portal Administrators How to get the staff users into the system How to get additional Portal Administrators into the system How to efficiently set up privileges and other settings for everyone Different roles for staff, administrators and patients
Key Concepts Users of Secure Messaging and the Portal exist in a shared user database Most staff have NO need to be given the role of Portal Admins – their job is to handle inbound secure messages and adding them as users will be enough If staff are patients of their practice, they should have two separate log-ins First uses their work email address (for when they are working) Second uses a personal email address (for when they are a patient using the portal)
Domains Groups Roles Profiles LDAP Roles Profiles
Domains Domains Automatically Assign Secure Messaging Privileges based upon email domain, after the @ symbol i.e. susan@family.coms Two are Built-in Internal – this is where you enter the email domain that assigns the privileges to your staff who have your email domain All – this is where you assign privileges to all other Secure Messaging users such as patients You could create more domains, but probably will not need to
Groups Groups are used to cluster users together to Give a small group of staff additional privileges Organize users into custom address books We will create groups as needed during deployment A few groups are built-in CareCatalyst Administrators (CC is the old name for Patient Portal) ClinicalMessenger Users (CM is the old name for SM Secure Messaging) Gateway Administrators (SM) – this can be ignored Gateway Users (SM) – this can be ignored
Profiles Used to organize outbound message settings and other preferences Profiles for SM message settings and other items Enable Project team to decide and lock down certain settings Other settings can be setup to be user’s choice Two Built-in Profiles Internal – Automatically assigned to members of the Internal Domain i.e. @familydocs.com Default – Assigned to everyone else including patients You could create more Profiles, but probably not needed
How to get Staff Users in the system For small – medium practices, there are 2 account creation methods Manual entry of user names – best for small-medium practices Send a message method – another option but needs to be monitored
For Large Practices LDAP Integration Automatic internal user creation and username/password sync Microsoft Active Directory with Exchange or Novell eDirectory If Exchange is shared with additional practices, LDAP integration is not an option.
Domains Groups Roles Profiles LDAP Roles Profiles