# Configuration
## Setting up DCMIO Configuration
### Prerequisite
Before setting up the DCMIO configuration, the user must have the following information.
1. Base URL
2. Username
3. Source
4. Sitename
5. Token
**Note**: Either Qure will provide the above list of information or the user can create them in the Qure platform. For further assistance, contact [support@qure.ai](https://qure.ai/support/).
### Configuring DCMIO
The objective of this configuration is to set up the communication between DCMIO and Qure's cloud server. This will allow the DCMIO to send study images to the cloud server for processing and receiving the processed results from it. Then, the processed results can be sent back to the medical system (modality).
The following are the DCMIO configurations.
1. API config
2. Filter config
3. Upload config
4. Publishers config
#### **API Config**
**API** config is used for configuring the DCMIO with API information. The API information allows the DCMIO to communicate with the cloud server through the API address for transferring and receiving study images.
The following is the API information that needs to be configured.
1. **Base Url**: Base Url is Qure.ai cloud address. This is a secure address that is used to send and receives study images to the API. The Base Url will differ based on the application's geographical area.
2. **Username**: Username is the cloud identity name.
3. **Source**: Source is the cloud identity source name.
4. **Sitename**: Sitename is the unique name given to the location in which the software is deployed. For example, a source can have multiple sitenames when it deploys its software in many locations.
5. **Token**: Token is the authentication/license key that will allow the user to access the source.
6. **Number of threads**: The default number of threads is 5.
7. **Enable compute**: Enable compute is the option that allows the processing of study images in a single instance base processing and series instance base processing.
* **Single instance base processing:** For single instance base processing, the processing of the study image will be processed one at a time by the DCMIO. For example, the DCMIO will just receive one study image from the medical system (modality) and pass it to the cloud server. Therefore, the **Enable compute** checkbox must be clear.
**Note**: Single instance base processing applies for qXR study images.
* **Series instance base processing:** For series instance base processing, a series of study images will be processed by the DCMIO. Sometimes, there is a delay in receiving all the series of study images in the DCMIO from the medical system (modality). Therefore, the **Enable compute** checkbox must be selected. This will enable the user to set a process delay time so that the DCMIO will receive all the related series of study images.
**Note**: Series instance base processing applies for qER and qCT study images.
If the user wants to set the process delay time, perform the following steps.
1. Open the link [localhost:7000/config/ ](http://localhost:7000/config/)on the system in which the DCMIO is installed. This will open the **Config** page.
**Note**: Make sure that the DCMIO is installed before you open the above link.
2. Now select and copy the whole programming language of the **Config** page that is from the open parenthesis to the closing parenthesis. Make sure that the program is copied correctly.
For example,
**From**
**To**
3. Scroll down the config page and paste it in the **Content** blank space.
4. In the content, search for the **"stability"** section. Then change the **"process\_delay"** value from 20 to any required number. This will set a process delay time in the DCMIO.
**Note**: The user must update only the **"process\_delay"** value in the **Config**.
5. Select **POST** to save the changes.
#### **Filter Config**
**Filter** config allows the users to filter specific study metadata information that needs to be uploaded into the server for processing. By default, the **Query** field is set as True and the **Enable Query** checkbox is clear.
The following are the steps if the user wants to filter specific study metadata information into the server for processing.
1. Select the **Enable Query** checkbox and it will enable the **Query** field.
2. Type `{metadata__FieldName}` in the **Query** field. Make sure that the FieldName is accurate as it is case-sensitive.
For example, if the user wants to process only the BodyPartE image of the chest, type `{metadata__BodyPartE} == 'CHEST'` as shown.
#### **Upload Config**
**Upload** config allows the user to configure the amount of study that the DCMIO can upload at a time, the compression of study images, and the anonymization of study data.
The users can configure the following upload config option.
1. **Batch Size**: Batch Size is the number of study images that the DCMIO can upload at a time. **32** is the default number, however, the user can change it as per the requirement.
2. **Enable compression**: The Enable compression option is used to compress the size of the study images.
* If the user wants to compress the study images, select the **Enable compression** checkbox.
* Type **+eb** in the compression options field to compress it to the default study image size.
3. **Anonymize Fields**: This option saves the patient data like Patient ID, Patient Name, etc. from uploading into the cloud server. The following are the steps to anonymize.
1. The user must select the **Anonymize Fields** checkbox to anonymize the patient data.
2. Select **FIELDS TO ANONYMIZE**, to add data of the patient that needs to be anonymized.
3. Type one patient data at a time in the empty field. Select to add multiple patient data.
The following are some of the examples that can be entered in the empty field.
* PatientID
* PatientName
* InstitutionName
* InstitutionAddress
* ReferringPhysicianName
* OperatorsName
* PatientBirthDate
* StationName
* AdditionalPatientHistory
* PatientComments
* PlateID
* AdmissionID
* ConfidentialityOnPatientDataDescr.
4. Select to delete unnecessary fields.
#### **Publishers Config**
**Publishers** config is used for sending the processed study image results back to the medical system (modality) or to other platforms.
Publishers allow the users to publish the processed study image results on any of the 4 platforms. They are as follows.
1. DICOM
2. Telegram
3. API
4. Health Level Seven (HL7)
**DICOM**
**DICOM** allows the users to publish the processed study image results back to the medical system (modality). The following are the steps to configure the **DICOM publishers**.
1. Select to add the details of the medical system (modality). Then select box 1.
2. Select the **Enable** checkbox.
3. Type the **Remote AET** title of the medical system (modality) in the box.
4. Type the **Remote Address** which is the IP address of the medical system (modality) in the box.
5. Type the **Remote Port** of the medical system (modality) in the box.
6. If the user wants to compress the study image, select the **Compression** checkbox. Else keep the checkbox clear.
7. Select to add **Keys To Send** data. Type any keys (**SC/SR/pdf**) in the clear field. Use one key at a time.
**Note**: If the user requires to add multiple keys, select to add a new key.
8. Select to add **Fields To Deanonymize** data. Type any of the patient data that was anonymized during upload. For more information, see step 3 of [Upload config](#upload-config).
9. If the user wants to delete any of the above fields. Select and click **Yes** on the **Confirm Deletion** pop-up.
**Telegram**
**Telegram** is currently inactive.
**API**
**API** allows the user to publish the processed study image results on other API platforms. The following are the steps to configure the **API publishers**.
1. Select to add the details of the other API platform. Then select box 1.
2. Select the **Enable** checkbox.
3. Type the **Endpoint** of the other API platform.
4. Type the **Payload Encoding** of the other API platform.
5. Type the **Timeout** of the other API platform.
6. Select to add **Auth** data which is the authentication data. Type the authentication data of the other API platform in the field.
7. If the user wants to delete any of the above fields. Select and click **Yes** on the **Confirm Deletion** pop-up.
**Health Level Seven (HL7)**
**HL7** allows users to publish processed study results to other software applications used by various healthcare providers. The following are the steps to configure the **HL7** **publishers**.
1. Select to add the details of the other HL7 software application. Then select box 1.
2. Select the **Enable** checkbox.
3. Type the **Host** or the IP address of the other software application.
4. Type the **Port** number of the other software application.
5. If the user wants to delete any of the above fields. Select and click **Yes** on the **Confirm Deletion** pop-up.
to add multiple patient data.
to delete unnecessary fields.
#### **Publishers Config**
**Publishers** config is used for sending the processed study image results back to the medical system (modality) or to other platforms.
