> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/analyze_network/analyze_network_setup.md).

# Analyze Network Setup

When organizations embrace openness and accessibility, they can pool their expertise to enhance interpretation of genomic data. This collaboration can lead to more accurate and comprehensive interpretations of genomic information, potentially resulting in advancements in medical research.

{% hint style="success" %}
Users can collaborate **across cloud environments and geographic regions**, broadening the scope of potential collaborations.

* The same secure, opt-in data sharing module is enabled across any Emedgene cloud.
* All existing data sharing network components support **cross-region sharing**.

**Limitations:** If networks share the same workgroup/organization name across cloud regions, they can't be distinguished in the UI.

**Recommendation:** Use unique network names across collaborators.
{% endhint %}

Emedgene aims to simplify the process of sharing cases among organizations, while ensuring that patient privacy and consent are respected.

The *Network* allows users to review tagged variants from other organizations within their network(s). The [*Related Cases tab*](/emedgene/emedgene-analyze-manual/variant_page/related_cases_section.md) on the [*Variant page*](/emedgene/emedgene-analyze-manual/variant_page/variant_page.md) displays shared case data that is relevant to the variant being reviewed.

Level of sharing of a particular case with a particular network of collaborators is defined by:

1. [Sharing configuration for a particular network](/emedgene/emedgene-analyze-manual/analyze_network/network_sharing_configuration.md), and
2. [Case subject consent for extended data sharing](/emedgene/emedgene-analyze-manual/analyze_network/case_subject_consent_for_extended_sharing.md).

One organization may participate in multiple networks under different terms.

Networks are being managed by the network admin in [*Settings*](/emedgene/emedgene-analyze-manual/settings.md) > *Network*.

![](https://4225924541-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YO86ZgkG5vXGkBAMT71%2Fuploads%2Fgit-blob-d059df18daeda07c39556754a0794ac49fd6779a%2F_network.png?alt=media)

Here the dedicated network manager can:

1. Create networks and set data sharing policy for each network;
2. Leave or delete networks.

{% hint style="info" %}
To invite other organizations to their network(s), the network manager must reach out to <techsupport@illumina.com>.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/analyze_network/analyze_network_setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.