Security for Secure Conversations

The following are security permissions related to Secure Conversations in the web application and mobile app. The security permissions all default to No/None in all existing security roles.

Two system security roles called Secure Conversations (system) and Secure Conversations Mobile (system) role are available for use. You can also edit an existing role or create a new security role to include these security permissions.

Do one of the following:
- Single community: Billing > Setup > Security Roles.
- Multi-community: Management Console > Standards > Financial Management > Security Roles.

Security Permission	Access Levels
Home Module > Secure Conversations (Parent Header)
My Conversations	Controls access to areas where Secure Conversations are visible in the web application as well as Resident Centric conversations. None = Not able to view Resident Centric messages on My Conversations Pane on Home tab, message bubble, resident header or Care Services Dashboard > All Conversations. R = Can view and response to Resident Centric messages posted on Home > My Conversations, message bubble, resident header and Care Services Dashboard > All Conversations. R/A = Can view, response and create new Resident Centric messages from Home > My Conversations, message bubble, resident header and Care Services Dashboard > All Conversations R/A/E = All of the above in addition to Add Participants and Leave a Resident Centric conversation. R/A/E/D = All of the above in addition to End Resident Centric Conversations.
General Conversations	Controls access to areas where General Conversations are visible in the web application as well as General/Cross-Community Conversation access. None = Gives no access to General Conversations. Read = User can see and respond to General Conversations on Home > My Conversations and message bubble. Read/Add = User can see, respond and created New General Conversations. Read/Add/Edit = All of the above in addition to add participants and Leave General Conversations. Read/Add/Edit/Delete = All of the above in addition to End General Conversations. *Also gives permission to access to Cross-Community Conversation if Cross-Community Access = Yes.
Edit Progress Notes	No = User cannot edit conversation text containing the resident-centric conversation. Yes = Users can edit the Progress Note text containing the resident-centric conversation and any other fields of the Progress Note.
Important Set this security permission in terms of how the community policy views a Text Conversation and belonging in the legal record. Example A: If a community views a text conversation as something that should be a part of the resident record and should not be altered then this security permission should be set to No, in conjunction with ‘Include Secure Conversations Text in a Progress Note’ = checked in Progress Notes Configuration. Example B: If a community views the text conversation as a starting point for the creation of a progress note for easier editing and the nurse can take the text conversation and add on information to create a more narrative styled note then this security permission should be set to Yes, in conjunction with ‘Include Secure Conversations Text in Progress Note’ = checked in Progress Notes Configuration. Example C: If a community views the text conversation as not belonging in the progress note in the form of a text conversation but instead a blank progress note this security permission should be set to Yes, in conjunction with ‘Include Secure Conversations Text in a Progress Note’ = cleared in Progress Notes Configuration.
Cross-Community Access	No = User cannot have cross-community conversations. Yes = Users can have cross-community conversations. *This permission is used in conjunction with General Conversations above. NOTE: For single community organizations, this security does not function regardless of setting.
Include Photos	None = No access to photo functionality. Users do not see a camera icon from conversations, cannot view photos sent by other users or can attach a photo to progress notes or the Misc tab. Read = View photos in a conversation. Users do not see the camera icon from conversation, or can attach a photo to progress notes or the Misc tab. Read/Add = Users can view photos and see the camera icon from a conversation. User cannot attach a photo to progress notes or the Misc tab. Read/Add/Edit = Users can view photos and see the camera icon from the conversation. Users can attach a photo to progress notes or the Misc tab if this permission, as well as access to Misc tab, is at least Read/Add/Edit. Read/Add/Edit/Delete = Same as Read/Add/Edit above.
Bulletin	These permissions are duplicated from the Admin and Clinical module permissions to the Community Bulletin Board on the Home area. Set if required, otherwise existing permissions supersede.
Mobile App Module
Secure Conversations Standalone Mobile Application	No = User cannot access via Secure Conversations mobile app. Yes = User can access via Secure Conversations mobile app.
Clinical Module > Clinical Dashboard (parent header)
All Conversations	No = User cannot see the new dashboard item if it is included in the dashboard view. Yes = Secure Conversations users can see the All Conversations dashboard item if it is included in the dashboard view.
EMC Module > Setup - Cross Community Conversations (parent header)
Cross-Community Conversations Groups Setup	None = User does not see the Cross-Community Conversation Groups Setup link from the Management Console and has no access to Cross-Community Conversation Groups Setup. Read = User has access to the Cross-Community Conversation Groups Setup link from the Management Console and can view the Cross-Community Conversation Groups Setup Screen. User has access to the Printable View button. User cannot create, edit, or delete a group. Read/Add = User has above access in addition to create a New Group. Read/Add/Edit = User has above access in addition to edit a group. Read/Add/Edit/Delete = User has above access in addition to delete a group.
Enable/Disable Cross-Community Conversations	No = User does not see the link to Enable/Disable Cross-Community Conversations for the organization. Yes = User can see and be can Enable/Disable Cross-Community Conversations for the organization.
Admin Module > Setup - Secure Conversations (parent header)
Groups Setup	None = User does not see the Secure Conversation Groups Setup link from the Billing > Setup menu and has no access to Secure Conversation Groups Setup. Read = User has access to the Secure Conversation Groups Setup link from the Billing > Setup menu and can view the Secure Conversation Groups Setup Screen. User has access to the Printable View button. User cannot create, edit, or delete a group. Read/Add = User has above access in addition to create a New Group. Read/Add/Edit = User has above access in addition to edit a group. Read/Add/Edit/Delete = User has above access in addition to delete a group.
Message Lifespan Setup	None = User does not have access to Message Lifespan Setup. Read = User has access to view Message Lifespan Setup. Read/Add = User has access to set Message Lifespan Setup. Read/Add/Edit = s/a Read/Add/Edit/Delete = s/a

Additionally, review these permissions as they impact Secure Conversations functionality.

Clinical Modules > Clinical Tabs (parent header)
Progress Notes	Controls whether users can create progress notes including from Secure Conversations. Users must have at least Read/Add security to create a Progress Note.
Care Provider Access Only	No = User can be involved in any resident-centric conversation. Yes = User can have resident-centric conversations only for residents where they are listed as a Medical Professional under the Profile tab of the chart. If Yes*, must also link Medical Professional to their PointClickCare user login.
Misc	Controls whether users can upload photos to the Misc in conjunction with the Include Photos permission in the Home module. Users must have at least Read/Add to the Miscellaneous tab to upload photos as part of Secure Conversations.

From the Security role, review the security permissions above.
Select security permissions for the role.
Click Save.
If users are not already assigned to the role, click users next to the security role.
Select the users to be assigned to this role.
Click Save.

You can create a new security role, edit an existing role or use the available system roles. Users must be assigned to the security role for security to take effect.
When saving the role, the system takes a few moments to enable Secure Conversations for these users. If the user has Enterprise access to all communities, this enablement may take up to 24hrs to take effect for the system to enable.
Security roles can also be assigned to individual Security Users through the roles link next to the username. There may be a enable SC link next to the security user if enabling Secure Conversations security was not successful. As well, if the user is being provisioned it indicates 'Processing enable SC'.

Secure Conversations must be enabled in the community for the security permissions above to function.

Senior Living Communities

ContentsContents

Security for Secure Conversations

Procedure

Important

Procedure

Hints and Tips

Business Rules