---
sourceDocument: Australia Healthcare and Life Sciences
sourceDocumentLink: https://www.servicenow.com/docs/r/healthcare-life-sciences

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Healthcare and Life Sciences

ft:clusterId :

    - hcls

bundleId :

    - hcls

workflow :

    - Customer and Industry


---

# Domain separation

# Domain separation and Pre-Visit Management {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read


Domain separation is supported for
Pre-Visit Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.  
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.

## Support level: Basic {#pre-visit-domain-sep__section_wlt_zgg_bpb}

{#pre-visit-domain-sep__domain-sep-supported}  
* Business logic: Ensure that data goes into the proper domain for the application's service provider use cases.
* The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
* The owner of the instance must set up the application to function across multiple tenants.
{#pre-visit-domain-sep__ul_yhr_g2j_xkb}

Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer's
message, the customer must be able to see the SP's response.{#pre-visit-domain-sep__p_lsc_nfg_h1c}

For more information on support levels, see [Application support for domain
separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#pre-visit-domain-sep__p_msc_nfg_h1c}

## Pre-Visit Management overview {#pre-visit-domain-sep__section_uqy_zgg_bpb}

The Pre-Visit Management application includes domain separation for
transactional data like procedure request cases. The application is based on the [Healthcare and Life Sciences data model](https://www.servicenow.com/docs/k2Tpu4tcQJpqLOW_xZ3p6g "The Healthcare and Life Sciences Service Management Core application provides a data model that is used in the Healthcare and Life Sciences Service Management workflows.") that also includes domain separation.

## How domain separation works in Pre-Visit Management {#pre-visit-domain-sep__section_vqy_zgg_bpb}

For customers using the Pre-Visit Management application to raise procedure
requests, the domain is set from the logged-in user's session, in the case created, and the
associated healthcare data.

## Use cases {#pre-visit-domain-sep__section_t33_bxz_c5b}

When healthcare providers have their healthcare data separated by domains, the healthcare
requests and corresponding fulfillment tasks are associated with the respective customer
domains.