Understanding What "Local" Actually Means for Your ChiroTouch Deployment

When a practice owner hears "practice management software," the mental image often lands on a browser tab pointing to a vendor's cloud. ChiroTouch works differently. The platform is a local network-based program that runs on a dedicated standalone server in your building, with Microsoft SQL Server handling the database layer. Every SOAP note, patient record, appointment, billing entry, and treatment plan your team creates lives on that hardware. The system requirements documentation is explicit: laptops, Macs, and all-in-one computers are not acceptable as the server, and the server must meet specific CPU, RAM, and hard-drive thresholds depending on whether you run one to seven workstations or eight or more. That architecture gives you fast, low-latency access to your charts at the front desk and in the treatment room, but it also means the single point of failure sits in your own office.

ChiroTouch's own system-requirements page lists "External hard drive and/or offsite backup" under the server specifications, and the accompanying disclaimer places responsibility squarely on the practice: "You are responsible for backing up your data and verifying the integrity of your data and backups." The vendor further notes that it is not liable for lost, corrupted, or unusable information. In practical terms, a ChiroTouch backup is not an optional add-on you can defer to a rainy Tuesday. It is a core operational task tied to the same hardware that keeps your practice running from the moment the first patient checks in until the last one is discharged. If the server's hard drive fails on a Friday afternoon, the practice that has a tested, verified offsite copy of its SQL database recovers in hours; the practice without one is looking at days of manual reconstruction or, in the worst case, permanent loss of encounter notes and billing history.

For office managers and IT staff, the specifics of the ChiroTouch environment shape what a good backup actually looks like. The database lives in Microsoft SQL Server, which means a simple file copy of a folder is not the same as a consistent database backup. The server also requires specific firewall ports to be open—1433 for SQL Server traffic, 8221 for iPad traffic, and 443 for web traffic—and the workstations must be able to reach a shared directory on the server. If a backup process is scheduled to run overnight, it needs to coordinate with SQL Server's transaction log so that the snapshot is internally consistent. Additionally, the system-requirements document strongly discourages RAID 5 arrays with spinning disks for the SQL database due to slower write speeds, a detail that matters because a backup solution that assumes a certain disk topology may behave differently than expected. Practice owners who are considering a ChiroTouch backup service or a new IT arrangement should ask their vendor or local IT professional to walk through exactly which SQL Server backup type (full, differential, transaction log) is being captured, how often, and where the offsite copy resides.

Finally, the verification step is where most backup plans quietly fail. ChiroTouch's documentation reminds practices to verify the integrity of their backups, and that reminder deserves more attention than it typically gets. A backup file that exists on an external drive or in an offsite location is only as valuable as the ability to restore it and confirm the data is readable. For a chiropractic practice, that means being able to pull up a patient's SOAP notes, treatment plan progress history, and billing records after a restore test. Schedule a restore drill at least once a quarter—pick a random patient file, confirm the encounter notes, appointment history, and charge codes all come back intact. Document the result. If you are working with ChiroTouch support staff or a third-party backup provider, make sure everyone understands that the goal is not merely "the file was copied" but "the practice could open ChiroTouch against that restored data and serve the next patient without a gap in the record." That level of confidence is what separates a ChiroTouch backup you hope works from one you know works when the server finally has its bad day.

Sources and further reading