> For the complete documentation index, see [llms.txt](https://documentation.qure.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.qure.ai/users-manual/qure.ai-app-users-manual/configuration.md).

# Configuration

## Configuration of Qure.ai App with Medical System (modality) <a href="#configuration" id="configuration"></a>

### Prerequisite

The following are the supported modalities.

* X-Rays
* CT scans

### Setting up the Medical System (modality) Configuration

Before configuring the Qure.ai app, the user must have basic knowledge of modality networking to configure with Qure app successfully. Each modality is a computer that is linked to another computer through a network. The modality has its settings (local settings). The user must add the following settings in their modality:&#x20;

* **AE Title**: QUREAI
* **IP**: Static IP of the system where the Qure.ai app is installed.

  **Note**: For more information on how to set up a static IP address in Windows, see [<mark style="color:blue;">How to set a static IP address in Windows</mark>](https://kb.netgear.com/27476/How-do-I-set-a-static-IP-address-in-Windows).
* **Port**: 5253

The modality must know the remote settings of the Qure.ai app with which it wants to communicate with.

### Configuring Medical System (modality)

The main objective of this configuration is to initiate communication between the medical system and the Qure.ai app.

The following are the steps to configure the medical system (modality).

{% hint style="info" %}
**Attention**:

The console will differ based on Vendor. Therefore, the steps to configure the nodes may also differ between modalities. So, consider the steps below as a reference example to configure any modality.
{% endhint %}

1. Login to the modality console with an admin access privilege.
2. On the modality console, select **DICOM** in the console configuration.&#x20;

   <div align="center"><figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZoJKHhnFYNEcdzbCHz2j%2Fuploads%2FMPBGw1qkou6NvTFES6RP%2FNode%20Configuration.png?alt=media&#x26;token=ab4af1e1-26f4-42ee-96da-e74a80a2b8f0" alt="" width="375"><figcaption></figcaption></figure></div>
3. On the **Add/Remove: Archive**, type the name/AE Title of the Qure.ai app. Then click **Add**.

   <div align="center"><figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZoJKHhnFYNEcdzbCHz2j%2Fuploads%2FkSMdgNOX9uB4AxlbTSai%2FImage%2016-11-22%20at%203.47%20PM.jpeg?alt=media&#x26;token=7ea792bd-0052-4ebe-9bd4-6fe24813fba4" alt="" width="375"><figcaption></figcaption></figure></div>
4. On the **Configurations of the Archive**, type the **Alias name**, **IP-Address**, **AeTitle**, and **Port** of the Qure.ai app as shown.

   <div align="center"><figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZoJKHhnFYNEcdzbCHz2j%2Fuploads%2F9ItxIHZRJVlXxHFtxBt3%2FModality.png?alt=media&#x26;token=7257cdc9-7f41-41d7-aced-eb15347d19d0" alt="" width="375"><figcaption></figcaption></figure></div>
5. Select **Always send the images to this archive?** checkbox. This option enables the modality to auto-push the study images to the Qure.ai app.&#x20;

   <div align="center"><figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZoJKHhnFYNEcdzbCHz2j%2Fuploads%2FwtxHHPQJ1IwAydGAWKSG%2FENTER%20IP%20AND%20port%20and%20enable%20auto%20push%20and%20check%20the%20connection.jpeg?alt=media&#x26;token=234a94c3-2c46-4334-acc1-9f5c112b1f06" alt="" width="563"><figcaption></figcaption></figure></div>
6. After successfully configuring the modality console, click **check connection** to check the connection between the modality and Qure.ai app.&#x20;

   <div align="center"><figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZoJKHhnFYNEcdzbCHz2j%2Fuploads%2FN2nTqr8UytZ8cOwwCX4O%2FENTER%20IP%20AND%20port%20and%20enable%20auto%20push%20and%20check%20the%20connection.jpeg?alt=media&#x26;token=99b53e1b-c75d-441f-8901-01795686007e" alt="" width="188"><figcaption></figcaption></figure></div>

   **Note**: The option for checking the connection varies between vendors, for example, **PING PACS workstation**/**RIS**/**ECHO Dicom**/**check connection**.
7. If the connection between them is **Successful**/**Connected**, the connection is complete.&#x20;
8. If the **connection failed**, repeat steps 4 through 6. If the issue still persists, seek the assistance of your modality vendor or engineer for support.