---
sourceDocument: Yokohama Healthcare and Life Sciences
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/healthcare-life-sciences

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Healthcare and Life Sciences

ft:clusterId :

    - hcls

bundleId :

    - hcls

workflow :

    - Customer and Industry


---

# Components installed with Pre-Visit Management

# Components installed with Pre-Visit Management {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Components installed with Pre-Visit Management

The Pre-Visit Management application in ServiceNow Yokohama release installs several key components including tables, user roles, ServiceNow Store applications, scheduled jobs, and business rules.
This application supports managing procedure request cases within healthcare settings.
Important to note, starting with the Yokohama release, Pre-Visit Management is being prepared for future deprecation; it will be hidden and no longer activated on new instances but continues to be supported.
Show full answer Show less  

## Roles Installed

The application installs multiple roles to control access and responsibilities:

* **snprevisit.admin:** Admin access to the application.
* **snprevisit.patientserviceagent:** Views and fulfills procedure request cases as a patient service representative.
* **snprevisit.casecreator:** Creates procedure request cases.
* **snprevisit.agentconnector:** Views, creates, and updates procedure request cases, often combined with other roles for agent profiles.
* **snprevisit.smagent:** Accesses and views all procedure request data as a patient service representative.
* **snprevisit.caseviewer:** Views all procedure request cases.
* **snprevisit.contributor:** Creates procedure request cases for patients, often combined with other roles.

These roles enable fine-grained permission management tailored to various user profiles in healthcare workflows.

## Tables Installed

The primary table installed is the **Procedure Request \[snprevisitprocedurerequest\]**, which stores procedure request cases and extends the Healthcare Case \[snhclscase\] table. This table is fundamental for tracking procedure requests within the application.

## ServiceNow Store Applications Installed

The application installs the **Healthcare and Life Sciences Service Management Core (snhcls)**, which provides essential healthcare digital capabilities such as patient 360-degree views, consent management, and digital documentation to enhance healthcare service delivery.

## Scheduled Jobs Installed

One scheduled job is installed:

* **Send procedure consent schedule:** Sends procedure consent documents to patients before their procedure appointment dates, helping ensure proper consent management.

## Business Rules Installed

Several business rules automate workflow processes:

* **Create book appointment task:** Creates an appointment task when a patient opts for insurance and the insurance review is completed.
* **Create insurance info task:** Creates an insurance task after the patient service representative reviews a procedure request case.
* **Update appointment booked on procedure request:** Updates the procedure request when an appointment task reaches a terminal state, indicating booking completion.
* **Patient access to procedure request:** Allows patients to view their own procedure request cases, enabling transparency and self-service.

## Practical Implications for ServiceNow Customers

By leveraging these components, customers can efficiently manage procedure requests within healthcare workflows, streamline patient service operations, and ensure compliance with consent and insurance processes. Understanding these components helps in configuring user access, automating case management, and preparing for the application's phased deprecation in future releases.  
Several types of components are installed with installation of the Pre-Visit Management application, including tables, user roles, ServiceNow Store applications, scheduled jobs, and business rules.
Important:  
Starting with the Yokohama release, Pre-Visit Management is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

For details, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support knowledge base.

Demo data is available for this feature.  
Note:  
The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see [Find components installed with an
application](https://www.servicenow.com/docs/access?context=find-components&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US).

## Roles installed {#pre-visit-components-installed__section_wly_yyh_wdb}

{#pre-visit-components-installed__table_qzw_m3l_4pb__entry__3}

| Role | Description | Contains roles |
|-|-|-|
| sn_previsit.admin | Administers who can access the Pre-Visit Management application. | sn_previsit.patient_service_agent |
| sn_previsit.patient_service_agent | Views and fulfills procedure request cases as a patient service representative. | sn_hcls.healthcare_agent |
| sn_previsit.case_creator | Creates procedure request cases for all associated objects. | sn_previsit.case_viewer |
| sn_previsit.agent_connector | Views, creates, and updates procedure request cases for all associated objects. You can combine this role with other roles for a user with the agent connector profile. For more information, see [Determining additional user profiles in Pre-Visit Management](https://servicenow-prod.fluidtopics.net/pVdBKh1mMw7tvatgh2xIYA "You can determine who can act as an agent connector or contributor for procedure request cases in the Pre-Visit Management application."). | * sn_hcls.healthcare_agent * sn_previsit.sm_agent {#pre-visit-components-installed__ul_eh4_5rf_15b} |
| sn_previsit.case_viewer | Views all procedure request cases available in the application. | None |
| sn_previsit.contributor | Creates procedure request cases for patients. You can combine this role with other roles for a user with the contributor profile. For more information, see [Determining additional user profiles in Pre-Visit Management](https://servicenow-prod.fluidtopics.net/pVdBKh1mMw7tvatgh2xIYA "You can determine who can act as an agent connector or contributor for procedure request cases in the Pre-Visit Management application."). | * sn_hcls.clinical_data_viewer * sn_hcls.foundation_data_viewer * sn_hcls.patient_data_viewer * sn_hcls.practitioner_data_viewer * sn_hcls.health_insurance_data_viewer * sn_previsit.case_viewer * sn_hcls.revenue_cycle_data_viewer * sn_previsit.case_creator {#pre-visit-components-installed__ul_dxs_lrf_15b} |
| sn_previsit.sm_agent | Accesses and views all data related to procedure requests as a patient service representative. | sn_previsit.case_creator |
[Table 1. Roles installed with Pre-Visit Management]

{#pre-visit-components-installed__table_qzw_m3l_4pb}

## Tables installed {#pre-visit-components-installed__section_s1x_dzh_wdb}

{#pre-visit-components-installed__table_ib2_btj_sqb__entry__2}

| Table | Description |
|-|-|
| Procedure request \[sn_previsit_procedure_request\] | Stores procedure request cases. Extends the Healthcare case \[sn_hcls_case\] table. |
[Table 2. Tables installed with Pre-Visit Management]

{#pre-visit-components-installed__table_ib2_btj_sqb}

## ServiceNow Store applications installed {#pre-visit-components-installed__section_iq1_sgj_sqb}

{#pre-visit-components-installed__table_ldj_jhj_sqb__entry__2}

| Application | Description |
|-|-|
| Healthcare and Life Sciences Service Management Core (sn_hcls) | Provides a data model and critical digital health capabilities including patient 360-degree view, consent management, and digital documentation to better address healthcare services. |
[Table 3. ServiceNow Store applications installed with Pre-Visit Management]

{#pre-visit-components-installed__table_ldj_jhj_sqb}

## Scheduled jobs installed {#pre-visit-components-installed__section_qvd_d1k_sqb}

{#pre-visit-components-installed__table_u5w_d1k_sqb__entry__2}

| Scheduled job | Description |
|-|-|
| Send procedure consent schedule | Sends procedure consent document before the procedure appointment date. |
[Table 4. Scheduled jobs installed with Pre-Visit Management]

{#pre-visit-components-installed__table_u5w_d1k_sqb}

## Business rules installed {#pre-visit-components-installed__section_s24_rdl_4pb}

{#pre-visit-components-installed__table_lyf_vdl_4pb__entry__4}

| Business rule | Table | Rule criteria | Description |
|-|-|-|-|
| Create book appointment task | Procedure request \[sn_previsit_procedure_request\] | After update | Creates an appointment task for the scheduling group when a patient opts for insurance and an agent completes the review of patient insurance. |
| Create insurance info task | Procedure request \[sn_previsit_procedure_request\] | After update | Creates an insurance task for the patient when the patient service representative completes the review of a procedure request case. |
| Update appt booked on procedure request | Book appointment \[sn_hcls_book_appt_task\] | After insert and update | Indicates that an appointment is booked for a procedure request when the appointment task moves to the terminal state. |
| Patient access to procedure request | Procedure request \[sn_previsit_procedure_request\] | Before query | Enables patients to view their procedure request cases. |
[Table 5. Business rules installed with Pre-Visit Management]

{#pre-visit-components-installed__table_lyf_vdl_4pb}