Setting up the server that powers your ChiroTouch environment is one of the most consequential IT decisions a chiropractic practice makes, yet it is often handled as an afterthought. The official guidance is clear: the main server should be a dedicated, standalone desktop computer running a 64-bit version of Windows 11 or Windows Server 2016 or newer. Laptops, Macs, and All-In-One machines are explicitly not acceptable as the server. For clinics running one to seven workstations, the server needs at least 6 GB of RAM, 20 GB of available hard-drive space on a SATA III drive, and a processor with a benchmark score of 3000 or higher. Practices with eight or more workstations should plan for 12 GB of RAM, 50 GB of drive space, and a CPU scoring 8000 or above. Microsoft SQL Server 2016 Express or Standard Edition (or newer) is required, and the Standard Edition is the recommended choice when the EHR-enabled version of ChiroTouch is in use.

Common Environment Pitfalls That Cause Downtime

Most ChiroTouch support tickets related to performance or connectivity trace back to a handful of avoidable configuration choices. The server must be connected via a wired 10/100/1000 Mbps network card; wireless connections to the server are not supported and can introduce data-loss risks. Every workstation on the network must be able to reach a shared directory on the server, so network segmentation or overly restrictive firewall rules will break the system. ChiroTouch relies on three specific firewall ports—1433 for SQL Server traffic, 8221 for iPad app traffic, and 443 for web traffic—and any of these being blocked will produce partial or total outages. Additionally, the practice should confirm that no other software on the server occupies the default SQL instance (MSSQLSERVER) or port 1433, because ChiroTouch is incompatible with applications that claim those resources.

Software compatibility is another area where well-meaning upgrades backfire. ChiroTouch requires the 32-bit version of Microsoft Office, with Word and Excel available for opening, exporting, and printing forms and reports. Office 365 must be installed locally on each workstation that needs it. The system does not support 32-bit operating systems, Windows Small Business Server, virtual machines, terminal workstations, or VPN connections. Surface tablets, touchscreens, and monitors driving resolutions above 1920 × 1080 can produce display errors in the ChiroTouch applications. If your office uses a Mac at the front desk, Parallels or Boot Camp can run Windows on that workstation, but the configuration is unsupported and the Mac can never serve as the primary server under any circumstance.

Integrated hardware deserves the same scrutiny. For document scanning, only the Fujitsu ScanSnap ix500, ix1500, and ix1600 models carry official support; other TWAIN-compliant USB scanners may work but fall outside the support scope. Signature capture is supported through ePad and ePad II pads, with drivers available from the ePad vendor site. For voice-to-text charting, Rheo AI Scribe was introduced in ChiroTouch version 7.2.14.6 and is available to subscription and legacy clients with active maintenance in the United States and its territories. iPad apps for patient-facing or provider tasks require an iOS-compatible iPad model; no other mobile operating system is supported. Before purchasing any peripheral, run it past your IT professional and, if possible, test it in a staging environment so the production server is not the first place a driver conflict surfaces.

Finally, keep the software stack current. Microsoft's latest updates, including the newest .NET Framework and PowerShell versions, should be installed on both the server and every workstation. A practical pre-launch checklist for any new or upgraded ChiroTouch deployment looks like this: confirm the server hardware meets the tier appropriate to your workstation count, verify the wired network connection and open the three required ports, install the correct 32-bit Office edition locally on each seat, confirm no incompatible third-party applications share the SQL instance, and test every integrated peripheral against the supported list. Walking through that checklist with your IT vendor before go-live is far less expensive than troubleshooting a half-configured environment on a Tuesday morning when three providers are waiting to chart.

Sources and further reading