Determining additional user profiles in Pre-Visit Management
You can determine who can act as an agent connector or contributor for procedure request cases in the Pre-Visit Management application.
As a user with the admin role, you can create contributor and agent connector profiles with the desired level of access to procedure request cases, case tasks, and other case-related information.
The sn_previsit.contributor and sn_previsit.agent_connector roles installed with the Pre-Visit Management application provide the following user profiles:
Agent connector
An agent connector within the Pre-Visit Management application acts as a fulfiller who can create, update, and close procedure request cases and tasks.
As a user with the admin role, you can determine who can act as an agent connector for the procedure request cases by assigning the sn_previsit.agent_connector role and other agent-specific roles to a group, and then assigning the group to the user with the agent connector profile. To assign roles to a group, see Assign a role to a group.
The following table describes the location agent profile within the Pre-Visit Management application scope that you can refer to as an example for combining the sn_previsit.agent_connector role with the industry data model roles in the CSM application.
Profile |
Description |
Assigned roles |
|---|---|---|
Location agent |
Creates and fulfills procedure request cases in the agent's business location. Note: To
create procedure request cases for a service organization (business location), a user with
the location agent profile must be a member of the service organization and assigned the
Location Consumer Agent responsibility type. The mapping of a
service organization and its members is included in the Service Organization Member
[sn_csm_service_organization_member] table. |
sn_previsit.agent_connector and sn_customerservice.svc_location_consumer_agent |
Contributor
A contributor within the Pre-Visit Management application acts as a requester who can create and read procedure request cases.
As a user with the admin role, you can determine who can act as a contributor to the procedure request cases by assigning the sn_previsit.contributor role and other contributor roles to a group, and then assigning the group to the user with the contributor profile. To assign roles to a group, see Assign a role to a group.
The following table describes different contributor profiles within the Pre-Visit Management application scope that you can refer to as an example for combining the sn_previsit.contributor role with the contributor roles in the CSM application.
Profile |
Description |
Assigned roles |
|---|---|---|
Relationship contributor |
Creates procedure request cases for only those patients with whom a relationship is
established. For more information, see Create relationships. Note: To create procedure requests for a
patient, a user with the relationship contributor profile must have a relationship with
the patient included in the Consumer Team Member [sn_customer_rel_consumer_to_user_list]
table and the Relationship Manager responsibility type. |
sn_previsit.contributor and sn_customerservice.relationship_contributor |
Patient contributor |
Creates procedure request cases for any patients. |
sn_previsit.contributor and sn_customerservice.consumer_contributor |
Location contributor |
Creates procedure request cases for any patients in a particular service organization
(business location) with which the user is associated as a service organization
member. Note: To create procedure request cases for a service organization (business
location), a user with the location contributor profile must be a member of the service
organization and assigned the Location Contributor responsibility
type. The mapping of a service organization and its members is included in the Service
Organization Member [sn_csm_service_organization_member] table. |
sn_previsit.contributor, sn_customerservice.service_organization_contributor, and sn_customerservice.consumer_contributor |