TRUSTDICOM Gateway

TRUST DICOM Gateway — User Manual

This manual covers installation, first-time setup, daily use, and troubleshooting. Processing stays on your workstation. Studies are not uploaded to Trust Software Solutions servers. Related pages: product · download · support.

Contents: 1. Installation · 2. Initial setup · 3. Daily use · 4. Troubleshooting

Chapter 1: Installation

Install the gateway on the PC that will sit on the same LAN as the imaging device (or that the modality can route DICOM to).

1.1 Download

  1. Open the download page.
  2. Windows: save TRUST-DICOM-Gateway-Setup.exe.
  3. Linux: save TRUST-DICOM-Gateway-1.0.0-linux.tar.gz.

1.2 Install

Windows: Run TRUST-DICOM-Gateway-Setup.exe. Prefer a short path such as C:\Trust\DicomGateway.

Linux:

sudo mkdir -p /opt/trust-dicom-gateway
sudo tar -xzf TRUST-DICOM-Gateway-1.0.0-linux.tar.gz -C /opt/trust-dicom-gateway
cd /opt/trust-dicom-gateway
chmod +x ./trust-dicom-gateway

1.3 Run

Windows: After setup, open TRUST DICOM Gateway from the Start menu. If Windows SmartScreen appears, choose More info → Run anyway when you downloaded the file from this site. Allow the app through the firewall when prompted so DICOM can listen on the configured port.

Linux: Start from the install directory (./trust-dicom-gateway). If you bind a port below 1024 you may need elevated privileges; the default DICOM port 11112 does not.

On first launch, paste the Polar license key from your purchase email. The license is bound to this workstation. Moving the install to another PC requires contacting support@trustsoftsolutions.com.

Chapter 2: Initial setup

2.1 Connect the imaging device (DICOM)

  1. In the gateway, open Settings → DICOM.
  2. Set AE Title (for example TRUSTGW). This must match what the modality will call.
  3. Set Listen port (default 11112) and note the workstation IPv4 address.
  4. On the modality or PACS, add a DICOM destination: IP of this PC, the same port, and the same AE Title. Use C-STORE (send / print-to-DICOM / “send to workstation”).
  5. Send a test study. The gateway Incoming list should show the study UID, patient name as provided by the modality, and a Received status.

If nothing arrives, confirm Windows/Linux firewall allows inbound TCP on the listen port, and that the modality and PC share a route (same subnet or a router that does not block the port).

2.2 WhatsApp API keys

  1. Create or open the WhatsApp Business / Cloud API (or the provider documented in the app’s WhatsApp panel).
  2. Copy the access token (or API key) and the destination phone number ID / recipient numbers you will send to.
  3. In the gateway, open Settings → WhatsApp, paste the token, set default recipients (clinic group, referring doctor, or patient workflow as your policy allows), and send a test text.

WhatsApp delivery requires outbound HTTPS. Images leave this PC only toward WhatsApp’s API after local conversion — not toward Trust servers. Follow your clinic’s consent rules before sending identifiable images.

2.3 Telegram API keys

  1. In Telegram, create a bot with BotFather and copy the bot token.
  2. Add the bot to the target chat or channel and obtain the chat ID.
  3. In the gateway, open Settings → Telegram, paste the token and chat ID, enable send, and run a test message.

You can enable WhatsApp, Telegram, both, or neither. Conversion to JPG/PDF still runs locally even if messaging is off.

2.4 Output folders

Choose a local folder for JPG and PDF (for example D:\Studies\Export). Keep this on a disk with enough space. The gateway does not require a medical film printer.

Chapter 3: Daily use

After setup, the usual clinic flow is:

  1. The technologist completes the exam on the modality.
  2. The modality sends the study to TRUST DICOM Gateway (C-STORE), the same way it would send to a printer or PACS node.
  3. The gateway receives the DICOM objects, writes them locally, and converts series/images to JPG and a PDF packet according to your template settings.
  4. If WhatsApp and/or Telegram are enabled, the gateway attaches the converted files and sends them to the configured destinations.
  5. Success appears as Sent. Failures go to the Retry queue. The queue retries automatically on a backoff schedule; you can also retry or discard an item manually.

Automatic updates check when the PC is online. Apply updates when no study is mid-transfer. License validation uses Polar; a short offline period is tolerated after a successful check, but messaging still needs internet.

Do not share the license key. One activation is tied to one workstation.

Chapter 4: Troubleshooting

4.1 Connection problems (nothing received)

  • Ping the gateway PC from another machine on the LAN.
  • Confirm AE Title, IP, and port on the modality match Settings → DICOM.
  • Allow inbound TCP on the listen port in the OS firewall and any antivirus.
  • Verify the modality is sending C-STORE to this node, not only printing to film.

4.2 Send failures (WhatsApp / Telegram)

  • Open the Retry queue. Read the error (invalid token, blocked number, chat not found, rate limit).
  • Re-test API credentials with the in-app Test button.
  • Confirm outbound HTTPS is not blocked by a clinic proxy; add exceptions if required.
  • Expired tokens: generate a new token at the provider and paste it again.

4.3 Logs

Open Help → Logs (or the logs folder next to the application). Look for receive, convert, and send lines around the study time. When contacting support, attach the log file for that day, your OS version, and a description of AE Title/port — do not send full patient studies unless your privacy officer approves a redacted sample.

Email support@trustsoftsolutions.com or WhatsApp 01273722444.