Getting the Foundation Right: Server, Workstation, and Network Requirements for ChiroTouch

One of the most common causes of sluggish performance, failed updates, and recurring support calls in a chiropractic office is a server environment that was never properly provisioned. ChiroTouch runs as a local, network-based application, which means the dedicated standalone computer you designate as the server carries the entire practice database, the SQL Server instance, and every workstation's file access. The platform explicitly does not support laptops, Macs, or all-in-one computers in that role, so if your current setup relies on a repurposed desktop or a small-form-factor PC, that is the first thing to address. For clinics running one to seven workstations, the server needs at least 6 GB of available RAM, 20 GB of free hard-drive space, a CPU with a PassMark benchmark score of 3000 or higher, and a SATA III drive interface with a wired 10/100/1000 Mbps network card. Practices with eight or more stations step up to 12 GB of RAM, 50 GB of drive space, and a CPU scoring 8000 or above, typically in the Intel i7 or AMD Ryzen 5 range or better. In both tiers, Microsoft SQL Server 2016 Express or Standard Edition is the database engine, and the Standard Edition is the recommended choice whenever an EHR-enabled version of ChiroTouch is in use.

Workstation configuration is where many offices cut corners, yet the minimums are straightforward: Windows 11 64-bit, a dual-core CPU scoring at least 1500 on PassMark, 4 GB of RAM, 10 GB of available disk space, and a wired or 802.11ac wireless network connection. Every workstation must be able to reach a shared directory on the server, so if your office network uses VLANs, segmented subnets, or a domain controller, your IT professional should verify that the shared-folder permissions and DNS resolution are in place before the first user logs in. The operating system must also carry the latest Microsoft updates, including the current .NET Framework and PowerShell versions, because ChiroTouch relies on those runtime components for its application logic and reporting engine.

Two software details trip up more setups than almost anything else. First, the Microsoft Office integration requires the 32-bit version of Office, licensed for commercial use, with Word and Excel available for opening, exporting, and printing forms and reports; Office 365 must be installed locally on each machine rather than accessed purely through a browser. Second, ChiroTouch is incompatible with any application that occupies the default SQL Server instance (MSSQLSERVER) or binds to port 1433, so if your office runs another program that uses that instance, you will need to configure a named instance or resolve the conflict before installation. A short list of known-incompatible products includes ChiroNotes, ChiroOffice, Chiro8000, MyoVision, Pinnacle, QuickCharts, and the on-premise version of ACOM Healthcare, among others. If your current stack includes any of those, plan the migration or removal in advance rather than discovering the conflict during go-live.

On the network and security side, three firewall ports must remain open for normal operation: 1433 for SQL Server traffic between workstations and the server, 8221 for iPad app communication, and 443 for web traffic. If your practice uses CTSecure for off-site data replication, your internet connection should support at least 25 Mbps download and 10 Mbps upload to keep sync windows reasonable. It is also worth noting that ChiroTouch does not support virtual machines, RAID 5 arrays with spinning disks (due to write-speed penalties on the SQL database), terminal workstations, or VPN connections as part of its supported configuration. Remote-access scenarios require additional work from a local IT vendor and fall outside the standard support scope. Finally, the platform requires a system backup strategy—whether that is an external hard drive, an off-site service, or both—and the practice team bears responsibility for verifying the integrity of those backups regularly. Treating the server room, the network switch, and the backup routine as a single unit rather than three separate IT tasks is what keeps a ChiroTouch deployment stable month after month.

Sources and further reading