# ChipSoft HiX

## Introduction

Easily and securely send appointment reminders, referrals, and other types of messages directly from HiX. Secure emailing is available from HiX version 6.1.

Three different options exist for securely sending messages from HiX:

1. [Send all messages securely](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#alle-berichten-veilig-versturen).
2. [Use Exchange on-premise to securely send specific types of messages (for example, appointment reminders)](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#exchange-on-premise-gebruiken-om-bepaalde-type-berichten-veilig-te-versturen).
3. [Use a mail server to securely send specific types of messages (for example, appointment reminders)](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mailserver-gebruiken-om-bepaalde-type-berichten-veilig-te-versturen).

_This option also applies to Exchange Online (Office 365)._

Info

To send secure emails from ChipSoft HiX, you need a business Zivver account in combination with the _Zivver Mail Submission_ add-on. For Mail Submission, you need an [Ultimate subscription](/content/nl/prijzen/index.html) and a contract that includes Mail Submission. To activate Mail Submission, please contact [sales@zivver.com](mailto:sales@zivver.com).

## Configure mail submission in Zivver

To configure secure emailing in ChipSoft HiX, you use the Zivver Mail Submission functionality. You must be an administrator to configure this.

1. Go to [SMTP credentials](https://app.zivver.com/admin/smtp-credentials).
2. Click  New SMTP credentials.
3. Enter a description.  
   _For example, “HiX”._
4. Click Generate.
   _A new screen opens showing a username and password. These credentials are displayed only once. Make sure to store them securely._
5. Click Close.

You have now generated an SMTP username and SMTP password. You will use these SMTP credentials later in this guide to authenticate the connection to smtp.zivver.com. Depending on which of the three options you choose, you will use these credentials in [HiX](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#alle-berichten-veilig-versturen), [Exchange on-premise](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#exchange-on-premise-gebruiken-om-bepaalde-type-berichten-veilig-te-versturen), or a [mail server](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mailserver-gebruiken-om-bepaalde-type-berichten-veilig-te-versturen).

## Send all messages securely

Use this option to securely send all messages from HiX via Zivver. To do this, you set up an SMTP connection with Zivver in HiX. This feature is available from HiX version 6.1.

Tip

Check which email report definitions exist in HiX to ensure that all types of messages (for example, appointment reminders and messages to chain partners) can be sent securely. Are there email report definitions that should not be sent securely? If so, use [Exchange on-premise](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#exchange-on-premise-gebruiken-om-bepaalde-type-berichten-veilig-te-versturen) or a [mail server](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mailserver-gebruiken-om-bepaalde-type-berichten-veilig-te-versturen) to securely send specific types of messages from HiX.

Note

In this section, we assume that HiX is configured to send emails. This means that CS-Routeer is configured for email, that email report definitions exist in CS-Overzichtsgenerator, and that routing fields are filled in within CS-Patiënt. If this is not the case, please contact ChipSoft or consult the CS-Routeer HiX manual to learn how to configure this.

### Set up an SMTP connection in HiX

Follow the steps below to set up the SMTP connection between HiX and Zivver. To do this, you adjust the global settings in CS-Routeer.

Tip

Always test the steps below first in the **acceptance environment** before configuring them in the **production environment**.

1. Open HiX.
2. Go to **CS-Routeer**.
3. Go to the global settings.
4. Go to **Routeertypes** > **Emailen**.
5. Verify that the **Emailen actief** option is enabled.
6. Enter _smtp.zivver.com_ in **Emailhost**.
7. Enter the _SMTP password_ from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver) in **Mailserver password**.

Warning

Do **not** enter the password of a Zivver account here.

8. Enter the _SMTP username_ from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver) in **Mailserver user**.

Warning

Do **not** enter the email address of a Zivver account here.

9. _Optional_: enter the default email address of the _sender_ in lowercase.

HiX is now configured to securely send messages via Zivver.

Warning

smtp.zivver.com only accepts the submitted message if:

1. A Zivver account exists for the default sender. _Verify this on the [account page](https://app.zivver.com/admin/accounts)._  
2. This Zivver account is a member of the Zivver organization for which the SMTP credentials were generated.

## Use Exchange on-premise to securely send specific types of messages

In this chapter, we explain how to set up an SMTP connection with Zivver in Exchange on-premise. We use a **Mail Flow Rule** to filter messages. This allows you to determine which types of messages are sent securely via Zivver, while regular email traffic is not routed through Zivver.

Tip

Use this option if you want to securely send specific types of messages (for example, only appointment reminders) from HiX. Do you want to securely send all messages from HiX? Then read [Send all messages securely](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#alle-berichten-veilig-versturen).

Note

In this chapter, we assume that an active SMTP connection exists between HiX and Microsoft Exchange on-premise. If this is not the case, please contact ChipSoft or consult the CS-Routeer HiX manual to learn how to configure this.

### Create an accepted domain

The first step is to add a new accepted domain in Exchange. This domain is fictitious and exists only within Exchange.

1. Go to the Exchange Admin Center (EAC).
   _For example, via `https://<ServerFQDN>/ecp`._
2. Log in to the EAC as an administrator (admin).
3. In the menu, go to **Mail flow**.
4. Go to **accepted domains**.
5. Click _add_ to add a new domain.
6. Enter a name, for example **Zivver HiX**.
7. Enter `zivver.org` in **Accepted domain**.
8. For **This accepted domain is**, select **Authoritative**.
9. Click Save.

The fictitious _accepted domain_ has now been created. In the next section, create a mail contact for this domain.

### Create a mail contact

The second step is to create a mail contact. This mail contact uses the fictitious domain that was created in the previous section.

01. Go to the Exchange Admin Center (EAC).  
    _For example, via `https://<ServerFQDN>/ecp`._  
02. Log in to the EAC as an administrator (admin).
03. In the left-hand menu, select **recipients**.
04. Select **contacts**.
05. Click _add_.
06. Select **Mail contact**.
07. Enter `Zivver Relay` for **Display name**.
08. Enter `Zivver Relay` for **Name**.
09. Enter `relay` for **Alias**.
10. Enter `relay@zivver.org` for **External email address** (the placeholder domain).
11. Click Save.

The _mail contact_ has now been created. Later in this chapter, we will route messages to this contact using a **Mail Flow Rule**.

### Configure an Exchange Send Connector

The third step is to create an SMTP connection with smtp.zivver.com. To do this, you create a **Send Connector**.

Warning

These steps are written for Exchange on-premise and are **not suitable for Exchange Online (Office 365)**. In Exchange Online, it is not possible to authenticate the connection to smtp.zivver.com using a username and password.  
As a workaround, you can add your organization’s domains to the Zivver allowlist.

01. Go to the Exchange Admin Center (EAC).  
    _For example, via `https://<ServerFQDN>/ecp`._  
02. Log in to the EAC as an administrator (admin).
03. In the left-hand menu, select **Mail flow**.
04. Select **Send connectors**.
05. Click _add_ to add a new connector.
06. Name the connector `Zivver Send Connector`.
07. For **Type**, select **Internet**.
08. Click Next.
09. Select **Route mail through these smart hosts**.
10. Click _add_.
11. Enter `smtp.zivver.com`.
12. Click Save.
    _The smart host now appears in the list._
13. Click Next.
14. For **Smart host authentication**, select **Basic authentication**.
15. Enable **Offer basic authentication only after starting TLS**.
16. Enter the generated SMTP username from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver) in **User name**.

Warning

Do **not** enter the email address of a Zivver account here.

17. Enter the generated SMTP password from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver) in **Password**.

Warning

Do **not** enter the password of a Zivver account here.

18. Click Next.
19. Click _add_.
20. Enter `SMTP` for **Type**.
21. Enter the placeholder domain `zivver.org` for **FQDN**.
22. Enter `1` for **Cost**.
23. Click Save.
24. Click Next.
25. Click _add_.
26. Select a server and click add ->.
27. Click OK.
28. Click Finish.

The **Send Connector** is now configured to intercept all messages addressed to this fictitious domain. To actually submit the messages to smtp.zivver.com, one additional change is required. This cannot be done via EAC/ECP and must be performed using PowerShell. See [Connect to Exchange servers using remote PowerShell](https://docs.microsoft.com/en-us/powershell/exchange/exchange-server/connect-to-exchange-servers-using-remote-powershell?view=exchange-ps) for background information on the PowerShell cmdlets below.

01. Start _Windows PowerShell_ with administrator privileges.
02. Run the following cmdlet to ensure that all loaded scripts use a valid certificate:

`Set-ExecutionPolicy RemoteSigned`
03. Run the following cmdlet to prompt for credentials:

`$UserCredential = Get-Credential`
04. Connect to Exchange on-premise and replace `ServerFQDN` with the correct server name:

`$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://"ServerFQDN"/PowerShell/ -Authentication Kerberos -Credential $UserCredential`
05. Import the Exchange cmdlets:

`Import-PSSession $Session -DisableNameChecking`
06. Retrieve an overview of the Send Connectors:

`Get-SendConnector`
07. Check the current port number of the **Zivver Send Connector**:

`Get-SendConnector "<Naam-Zivver-SendConnector>" | Select-Object port`
08. Change the port number of the **Zivver Send Connector** to 587:

`Set-SendConnector "<Naam-Zivver-SendConnector>" -port 587`
09. Verify that the port number has been updated:

`Get-SendConnector "<Naam-Zivver-SendConnector>" | Select-Object port`
10. Close the PowerShell session:

`Remove-PSSession $Session`

```fallback
Set-ExecutionPolicy RemoteSigned
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://"ServerFQDN"/PowerShell/ -Authentication Kerberos -Credential $UserCredential
Import-PSSession $Session -DisableNameChecking
Get-SendConnector
Get-SendConnector "<naam>" | Select-Object port
Set-SendConnector "<naam>" -port 587
Get-SendConnector "<naam>" | Select-Object port
Remove-PSSession $Session
```

The **Send Connector** is now ready. In the next section, create a _Mail Flow Rule_ to route specific types of messages to the contact with this fictitious domain.

### Configure a Mail Flow rule

The fourth step is to create a rule that filters messages. The filtered messages are then routed to the mail contact with the fictitious domain.

#### Filter messages by subject

In the steps below, we use an example filter that checks the subject. If the subject of the message contains _Afspraakbevestiging_, the message will be sent securely.

01. Go to the Exchange Admin Center (EAC).  
    _For example, via `https://<ServerFQDN>/ecp`._  
02. Log in to the EAC as an administrator (admin).
03. In the left-hand menu, go to **Mail flow**.
04. Go to **Rules**.
05. Click the _add_ button.
06. Select **Create a new rule...**.
07. Name the rule `Stuur HiX-afspraakbevestiging via Zivver`.
08. At the bottom, click **More options...**.
09. Under **\*Apply this rule if...**, select **The subject or body...** and then **subject matches these text patterns**.
10. Enter `Afspraakbevestiging`.
11. Click _add_ to add the value.
12. Click OK.
13. Click add condition.
14. Under **And**, select **The recipient...** and then **is external/internal**.
15. Select the option **Outside the organization**.
16. Click OK.
17. Under **\*Do the following...**, select **Redirect the message to...** and then **these recipients**.
18. Select the _mail contact_ with the fictitious domain created in [Contactpersoon aanmaken](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#contactpersoon-aanmaken).
19. Click add ->.
20. Click OK.
21. For **Choose a mode for this rule**, select **Enforce**.
22. Enable the option **Defer the message if rule processing doesn’t complete**.

Warning

When this option is enabled, a message (regardless of whether it comes from HiX or Outlook) will only be sent after it has been checked against this rule. If Exchange temporarily fails to check messages, sending will be paused.

23. Click Save.
24. Check that the priority of the newly created rule is correct. Adjust if necessary to ensure that the different rules have the intended effect.
25. Activate the rule.

The rule is now configured and active. All sent messages are checked and, depending on the subject, routed to the mail contact with the fictitious domain. The **Send Connector** intercepts all messages to this fictitious domain and then sends them via the SMTP connection to the Zivver SMTP server.

## Use a mail server to securely send certain types of messages

This chapter explains how to set up an SMTP connection with Zivver on a mail server.

Tip

Use this option if you want to securely send only certain types of messages (e.g., appointment confirmations) from HiX. If you want to securely send all messages from HiX, see [Use a mail server to securely send all messages](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#alle-berichten-veilig-versturen).

Note

Does your organization use Exchange Online (Office 365)? Then you need a different mail server, because in Exchange Online it is not possible to authenticate the connection to smtp.zivver.com using a username and password.

### Deploying an additional mail server alongside Exchange Online

With Exchange Online, you need an additional mail server to authenticate the SMTP connection to smtp.zivver.com using a username and password. This additional mail server filters messages from HiX, allowing you to determine which types of messages (e.g., appointment confirmations) are sent securely via Zivver, while regular message traffic is not sent through Zivver.

Messages from HiX then follow one of the routes below:

1. HiX > Additional mail server > smtp.zivver.com > Recipient (secure message)
2. HiX > Additional mail server > Exchange Online > Recipient (regular message)

To enable these routes, set up the following two SMTP connections on the additional mail server:

1. An SMTP connection that sends certain types of messages (e.g., appointment confirmations) securely via smtp.zivver.com.
2. An SMTP connection that sends all other messages via Exchange Online (Office 365).

In the following sections, we will show how to configure an additional mail server.

### Setting up the SMTP connection

Use the following information to set up the SMTP connection with Zivver on your mail server:

Note

Refer to your mail server’s documentation to learn how to set up an SMTP connection.

- SMTP server: smtp.zivver.com
- SMTP port: 587
- TLS: Yes, v1.2 with STARTTLS
- SMTP authentication: Yes, using a username and password.
- For **username**, enter the _SMTP username_ from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver).

Warning

Do **not** enter a Zivver account email address here.

- For **password**, enter the _SMTP password_ from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver).

Warning

Do **not** enter a Zivver account password here.

#### Setting up the SMTP connection in hMailServer

In this chapter, we use [hMailServer](https://www.hmailserver.com/) as the mail server. It is a free, open-source mail server for Microsoft Windows, which allows you to set up multiple SMTP connections and filters.

Follow the steps below to set up an SMTP connection with Zivver in _hMailServer_:

01. Open _hMailServer Administrator_.
02. Select the mail server.
03. Click **Connect**.
04. Enter the password.
05. Click **Settings**.
06. Click **Protocols**.
07. Click **SMTP**.
08. Click **Routes**.
09. Click **Add**.
10. Enter _Zivver_ in _Domain_.
11. Enter _smtp.zivver.com_ in _Target SMTP host_.
12. Enter _587_ in _TCP/IP port_.
13. For _Connection security_, select _STARTTLS (Required)_.
14. For _When sender matches route, treat sender as_, select _A local email address_.
15. For _When recipient matches route, treat recipient as_, select _A local email address_.
16. Go to the _Delivery_ tab.
17. Enable _Server requires authentication_.
18. Enter the _SMTP username_ from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver) under **User name**.

Warning

Do **not** enter a Zivver account email address here.

19. Enter the _SMTP password_ from the chapter [Mail submission instellen in Zivver](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#mail-submission-instellen-in-zivver) under **Password**.

Warning

Do **not** enter a Zivver account password here.

20. Click **Save**.

The SMTP connection with Zivver is now set up. Repeat these steps to set up a second SMTP connection with your own mail server (e.g., Office 365).

### Setting up a filter

In this section, we use [hMailServer](https://www.hmailserver.com/) as the mail server. It is a free, open-source mail server for Microsoft Windows that allows you to set up multiple SMTP connections and filters.

Note

Not using _hMailServer_? Refer to your mail server’s documentation to learn how to filter messages.

The steps below use an example filter that checks the subject. If the subject of the message contains _Afspraakbevestiging_, the message will be sent securely.

01. Open _hMailServer Administrator_.
02. Select the mail server.
03. Click **Connect**.
04. Enter the password.
05. Go to _Rules_.
06. Click **Add**.
07. Enter a name.
    _For example: Send HiX appointment confirmation via Zivver._
08. Enable _Enabled_.
09. Under _Criteria_, click **Add**.
10. Select the option **Predefined field**.
11. Select _Subject_.
12. For _Search type_, select _Equals_.
13. Enter _Afspraakbevestiging_ under _Value_.
14. Click **OK**.
15. Under _Actions_, click **Add**.
16. Select the option _Send using route_.
17. Select the option _Zivver_.
18. Click **OK**.
19. Click **OK**.

The filter is now set up and activated. All outgoing messages will now be checked and, depending on the subject, sent securely via Zivver.

## Modifying an email report definition

Follow the steps below to make a HiX email report definition suitable for secure emailing:

Tip

Always test the steps below first in the **acceptance environment** before configuring them in the **production environment**.

Warning

smtp.zivver.com will only accept the message if:

1. A Zivver account exists for the default sender.
   _Check this on the [account page](https://app.zivver.com/admin/accounts)._  
2. This Zivver account is a member of the Zivver organization for which the SMTP credentials were generated.

1. Open HiX.
2. Go to **CS-Overzichtsgenerator**.
3. Open an existing email report definition.
4. Ensure that **Rapportage type** has the option **Emailen** enabled.
5. Enter the sender’s email address in lowercase.
6. Enter a recipient.
   For example, the patient’s email address using the following expression: _=\[Context\]Patient(Emailadres)_.
7. _Optional_: see [Bericht extra beveiligen met 2FA](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#bericht-extra-beveiligen-met-2fa) to secure the message further with an SMS code or access code.
8. _Optional_: see [Bericht automatisch intrekken na de vervaldatum](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#bericht-automatisch-intrekken-na-de-vervaldatum) to automatically retract the message after the expiration date for the recipient or both sender and recipient.
9. Click **OK**.

Repeat the steps above for each email report definition you want to use for secure emailing.

### Securing a message with 2FA

This functionality is optional. Secure the message with an SMS code or access code. The recipient can only read the message after entering the SMS code or access code. This ensures that only the intended recipient can access the message.

This can be done by [providing the recipient’s mobile number](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#beveiligen-met-een-sms-code), by setting [the patient number](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#beveiligen-met-een-toegangscode) as an access code, or by using [a combination of SMS codes and patient numbers](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#beveiligen-met-een-sms-code-of-toegangscode). Zivver uses this information to secure the message further. The mobile number and access code are not visible to the recipient, as these details are included as _comments_ in the email report definition.

#### Securing with an SMS code

Include the patient’s mobile number in the message. Add the following code to the email report definition. The location of this code in the message does not matter.

[Download expression to secure Zivver messages with SMS code](https://docs.zivver.com/downloads/hix-secure-with-sms-code.txt)

#### Securing with an access code

Include the patient number in the message as an access code. Add the following code to the email report definition. The location of this code in the message does not matter.

[Download expression to secure Zivver messages with access code](https://docs.zivver.com/downloads/hix-secure-with-access-code.txt)

#### Securing with an SMS code or access code

Include the patient’s mobile number in the message, or use the patient number as an access code if the mobile number is not available. Add the following code to the email report definition. The location of this code in the message does not matter.

[Download expression to secure Zivver messages with SMS code or access code](https://docs.zivver.com/downloads/hix-secure-with-sms-code-or-access-code.txt)

### Automatically retract message after expiration date

This functionality is optional. Set an expiration date after which the message can no longer be read by the [recipient](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#bericht-na-vervaldatum-niet-meer-leesbaar-voor-ontvanger) or by [sender and recipient](https://docs.zivver.com/en/admin/integrations/chipsoft-hix.html#bericht-na-vervaldatum-niet-meer-leesbaar-voor-verzender-en-ontvanger). This setting is not visible to the recipient, as these details are included as _comments_ in the email report definition. See below how to configure this in an email report definition.

#### Message no longer readable by recipient after expiration date

In this example, the message is set to expire 30 days after sending and can no longer be read by the recipient. Add the following code to the email report definition. The location of this code in the message does not matter.

[Download expression to make Zivver messages expire after 30 days for the recipient](https://docs.zivver.com/downloads/hix-expiration-date-recipient.txt)

#### Message no longer readable by sender and recipient after expiration date

In this example, the message is set to expire six months (178 days) after sending and can no longer be read by the sender and recipient. Add the following code to the email report definition. The location of this code in the message does not matter.

[Download expression to make Zivver messages expire after 178 days for the sender and recipient](https://docs.zivver.com/downloads/hix-expiration-date-recipient-sender.txt)

Updated on 2026-06-18