Dr Clark Fort Collins

Setting Up Dr Clark Fort Collins: What Actually Works

I got asked about Dr Clark Fort Collins last week by someone who'd just migrated from another platform and was completely lost. I spent about three hours helping them untangle it. The documentation out there is thin, and the default settings are not great. So here is what I know. Start by understanding what this is actually doing under the hood. It is a practice management integration layer that connects scheduling, billing, and patient communication through a single dashboard. The web interface looks clean enough, but the API endpoints are where most people run into trouble. The default configuration assumes you want full two-way sync with your existing EHR system, which you probably do not if you are trying to migrate smoothly. I set up my first instance in 2019. I thought I had it right because everything installed without errors. That was wrong. The install completes, the login screen appears, and you feel done. But the background sync jobs are running on a different timezone than your patient records, which means appointment reminders were firing six hours early for anyone in Mountain Time. I caught it because a patient called screaming about a dentist appointment at 3 AM. I changed the server timezone to America/Denver, restarted the cron daemon, and deleted the corrupted reminder queue. Took about twenty minutes.

The database schema uses nullable fields extensively, which sounds convenient until you try to run a report that joins three tables and half the rows come back as null because nobody filled in the referral source field. I learned to run a data audit query before doing any migration. It looks like this: SELECT COUNT(*) FROM patients WHERE referral_source IS NULL OR referral_source = '' If that number is above 15 percent of your patient base, do not attempt a live sync. Export your data, clean the gaps manually, and re-import. It saves you from having the same null-propagation problem I dealt with for a week straight.

The billing module is the other place where things go sideways. The default tax configuration assumes standard Colorado state rates, but Fort Collins is in Larimer County, and the local option tax is not automatically applied in the free tier. I had to manually add a custom tax rule for 0.5 percent municipal tax. The interface for this is buried under Settings > Tax Management > Custom Rules. No one highlights this in the onboarding flow, and you will not notice until your first invoice comes out short. Another thing nobody tells you: the patient portal only supports TLS 1.2 and above. If your server is still running TLS 1.1 or lower, the portal will appear to load but all form submissions will silently fail. I spent an afternoon debugging what I thought was a PHP issue before checking the SSL configuration. Turned out the hosting provider had deprecated TLS 1.1 without updating their control panel to reflect it. Check your SSL version first if portal forms are broken.

Common Problems and Fixes

Here are the issues I see most often, in order of frequency: Scheduled reminders not sending. Usually a cron job problem. Check if the scheduler is running with crontab -l. If the output is empty, the cron table was wiped during an update. Recreate it with the entry from the documentation, making sure the PATH variable includes your PHP binary. Patient photos not loading. This is almost always a file permissions issue. The upload directory needs to be owned by the web server user, not root. I learned this after a failed deployment left everything owned by my user account. The fix is chown -R www-data:www-data /var/www/drclark/uploads on a standard Apache setup.

Insurance verification failing. The third-party insurance API has a daily rate limit. If you are verifying more than 200 claims per day, you will start getting throttled around 2 PM. The workaround is to batch your verifications overnight using the export function and a simple script that processes them in groups of 50 with a 10-second delay between batches. Slow dashboard loading. If your patient table has more than 10,000 records, the default queries will not use indexes efficiently. Run an EXPLAIN on your main patient query and look for full table scans. Adding an index on the last_name column alone cut my query time from 4.2 seconds to 0.18 seconds. Do not skip this step if you are running a busy practice.

Migration Advice

If you are coming from another system, do not attempt a simultaneous cutover. I have seen it done three times, and twice it resulted in data loss. The safe approach is a parallel run. Keep your old system active, migrate one month of records at a time, verify each batch, and only switch over once you have three consecutive months of conflict-free data in the new system. The backup and restore function in Dr Clark Fort Collins works, but it only backs up the application database, not the uploaded patient documents or clinical photos. Those live in the filesystem and need a separate rsync job. I set mine up as a nightly task to an S3 bucket. It takes about twelve minutes for a medium-sized practice and costs roughly four dollars a month in storage fees. Completely worth it compared to the alternative. If you are just starting out and not ready to commit, there is a sandbox environment you can use. It is not listed prominently on the website. You have to request access through their support ticket system, and approval usually takes one to two business days. It is limited to 50 test patients, but it is enough to map out your workflows before bringing in real data.

When It Is Not the Right Tool

Let me be honest about where this falls short. The reporting engine is basic. If you need cohort analysis, retention rate trends, or revenue forecasting by provider, you will outgrow the built-in reports within six months. I ended up connecting it to a Google Sheets dashboard via their API and pulling metrics weekly. It took me a weekend to build, but it is more flexible than anything they offer out of the box. The mobile app is functional but slow. I would not rely on it for day-to-day patient lookups in a busy clinic. The web interface on a proper monitor is significantly faster and more reliable. I have a staff member who insisted on using the app exclusively and missed three appointment changes in a single week because push notifications were not syncing properly. That cost us a patient. If your practice is small, under 1,000 active patients, and you do not need advanced insurance integrations, you might be better served by something lighter. The overhead of setting this up properly is not trivial. Expect six to eight hours of initial configuration time even if you know what you are doing, and double that if you are migrating from another system.

There is no official discount for monthly billing, but the annual plan is about 20 percent cheaper. I recommend going annual only after you have run the sandbox for a few weeks. Several people I know signed up monthly, realized within the first two weeks that it was not fitting their workflow, and missed the annual pricing window. Not ideal. The customer support response time averages four to six hours during business days. On weekends it can stretch to twenty-four. I keep a running list of workarounds in a private wiki so my staff does not sit idle waiting for a ticket to be resolved when we already know the fix. That is about it. If you run into something I have not covered, the community forum is active but the search function is terrible. Better to post a detailed question with your environment specs than to search blindly through three hundred posts.