I really want to use a different firewall to Windows Firewall

We recommend you use Windows Firewall and support only that configuration.

However, if you really want to use a different firewall, here is some information that may be helpful to you. If you encounter problems (most likely affecting patient flow), you will have to diagnose and fix them yourself.

Program exceptions

On each startup, Spinalogic checks to see if it has an entry in the Windows Firewall. If it is missing, it attempts to create that entry. The command used is:

netsh firewall add allowed program “Name” “Program”

Where ‘Name’ is the name to be used by Windows Firewall for the entry, and ‘Program’ is the full path to the Spinalogic program.

These paths are:

Workstation – {programfiles}\Spinalogic\Workstation\Spinalogic.exe

Calling – {programfiles}\Spinalogic\Calling\Spinalogic_Calling.exe

Arrivals – {programfiles}\Spinalogic\Arrivals\Spinalogic_Arrivals.exe

What are these exceptions needed for?

Spinalogic coordinates the movement of patients about the practice and synchronizes other events by broadcasting UDP packets. Each instance of Spinalogic registers in the database the IP address of the machine it is running on. Then, when a station wants to broadcast an update, it sends the UDP packet to each registered IP address. When the program unloads, it de-registers from the IP list in the database.

These packets are sent on ports 51000 through 51050.

Spinalogic also accesses SMTP servers for sending emails. For ‘mother-ship’ notifications, port 587 is used. Then there is the port used by the practice SMTP server.

Finally, on port 80 is Spinalogic license authentication, Spinalogic cloud patient sharing and Spinalogic update checks and downloads.

Server Exceptions

SQL server: C:\Program Files\Microsoft SQL Server\MSSQL10_50.SPINALOGIC\MSSQL\Binn\sqlservr.exe

SQL Browser: UDP port 1434

DICOM Receiver Exceptions

TCP port 104