Many companies say they “integrate” with your EHR (your patient records and scheduling software). That word gets used loosely.
A real integration means the other software is connected to your EHR’s actual patient and schedule data. A look-alike “integration” often means the company adds a staff user in your EHR, signs in like a person, and copies what appears on the screen.
TrackStat connects to the data in your EHR. It does not read your schedule by pretending to be a front-desk user clicking through screens.
If another company is marketing to you and claims they have an integration, use this article to compare what they actually do with what a true data connection looks like.
What a real EHR integration is
A real integration pulls information from the EHR itself, not from the pictures and lists a person sees on the screen.
Depending on your EHR, that connection may work in one of these ways:
For cloud EHRs, a secure connection is made to the EHR’s data.
For office-based / server EHRs such as ChiroTouch Classic, a small communication program on the office computer talks to the EHR software and sends the needed information.
In both cases, the tool is reading the underlying patient and schedule information. You keep using the same EHR. Your charting and clinical workflow do not change.
A real connection should:
Keep working when your EHR changes how a page looks
Stay in sync with appointments, visits, and patient status
Allow the tool to act on the same information your office already uses
Not depend on a bot clicking buttons in your EHR all day
What some companies mean when they say “integration”
Some third-party tools claim they integrate with many EHRs. In practice, they may be doing this:
They ask you to create a user in your EHR, the same way you would create a login for a new staff member.
They sign in with that user.
Their software opens the same screens your team uses.
They copy names, dates, and other details off those screens into their own system.
That method is often called screen reading or screen copying. It can look fine in a demo. It is not the same as connecting to the EHR’s database.
This matters because the screen is only a display. It is not the full, reliable record. If a page is filtered, cut off, or laid out differently after an update, the copied information can be wrong or incomplete.
Screen reading is not the same as a software connection
These two setups can both involve a password. They are not the same thing.
Staff-user sign-in used to read the screen
The other company logs in as if they were an employee. They look at the same pages your front desk looks at and copy what is shown. If your EHR moves a button, changes a column, or updates its layout, that copy process can break.
A connection to the EHR software or its database
The other company is talking to the EHR behind the screens. Some of those connections use a secure access password or connection key. That is normal. The difference is what the password is used for. It is used to reach the data, not to sit in a staff login and read the page like a person.
If a company needs a regular staff login so their software can click through your EHR, that is a warning sign. If a company needs connection details so their software can talk to the EHR’s database, that can be a real integration.
Why this matters for your practice
When a tool only copies the screen, your office can run into problems:
The lists can be wrong. The tool may miss patients, copy an old appointment, or only see what was on one page.
It can stop working after an EHR update. A new look in the EHR can break a screen-copying tool overnight.
Staff lose trust. If the daily list does not match the EHR, your team stops using the tool.
You may have to pay for an extra EHR user just so another company’s software can sign in.
It can slow your EHR down if a program is clicking through screens while your team is trying to work.
It is harder to see who accessed what. Activity can look like a staff member was in the chart, even when a program was doing the clicking.
A real database connection is more stable. It works from the information already in your EHR so reminders, follow-up, reactivation, and scheduling tools are based on the same source your office uses every day.
Why the access method also affects compliance and liability
Even when the data belongs to the clinic, the way a third-party tool accesses it still matters under HIPAA.
Vendors that create, receive, maintain, or transmit protected health information on a clinic’s behalf are business associates. They need a Business Associate Agreement that defines permitted uses and requires appropriate safeguards. The casual claim that “it’s the clinic’s data, so they can do whatever they want” does not remove those requirements.
Screen reading or UI automation often creates:
Audit gaps - Activity can appear as a staff login rather than a clear, structured system-to-system connection, making it harder to track what was accessed and when.
Reliability and accuracy risks - Incomplete or stale copies can lead to decisions based on information that does not match the EHR.
Liability that remains with the clinic - Covered entities are responsible for their vendors and for risk analysis. If an access method contributes to an improper disclosure, security incident, or failure to meet minimum-necessary standards, the clinic can still face regulatory exposure.
Official integrations are designed to be more auditable, stable, and easier to scope within a Business Associate Agreement. That is why TrackStat prioritizes connecting to the underlying data rather than reading screens.
How TrackStat connects
TrackStat sits on top of the EHR you already use. You do not need to switch EHRs.
Cloud EHRs connect directly.
Server-based EHRs such as ChiroTouch Classic use a small communication program that connects with your software and syncs the needed information.
TrackStat then turns that information into daily follow-up, reminders, reactivation, reviews, online scheduling, and other practice workflows.
TrackStat currently integrates with systems including ChiroTouch Classic (server), ChiroTouch Cloud, Prompt, ClinicMind, Genesis, IntakeQ, Fortis, FormDr, CashPractice, and HighLevel (GHL). Coming soon are integrations with ChiroUp. Integrations are added regularly.
Questions to ask any company that says they “integrate”
Ask these in writing or on a demo. A trustworthy company should answer in plain English.
Do you read information from the EHR’s database, or do you sign in like a staff member and copy the screen?
If my EHR changes how a page looks next month, will your connection still work?
How often does your system refresh information from the EHR?
If I book or reschedule a patient in your software, does that appointment show up inside my EHR, or only in your software?
Do you need me to create a normal staff user so your program can click through the EHR?
Can you explain, in simple terms, how your software gets appointment and patient information from my specific EHR?
What happens if the connection fails? How will my office know the information is out of date?
Do you have a Business Associate Agreement that covers how you access and use data from our EHR?
If the answers are vague, or if the main setup step is “create a user and give us that login so we can go into your EHR,” you are likely looking at screen copying, not a true data connection.
Quick comparison
What you hear | What it often means | What to look for |
“We integrate with your EHR.” | Could be a real connection, or just a staff login that copies the screen | Ask how they get the information |
“Just add a user for us.” | Their software may sign in like a person and read pages | Ask if they need to click through the EHR |
“It works with every EHR.” | They may use the same screen-copy method everywhere | Ask what is different for your EHR |
“We connect to your data.” | Should mean they read the EHR’s records, not the screen | Ask what happens when the EHR changes its layout |
“Appointments sync.” | Should mean changes show up in the EHR itself | Book a test appointment and check the EHR schedule |
Summary
Not every company that says “we have an integration” is connected to your EHR’s data. Some add a user and copy what they see on the screen. That can look similar in a sales demo and still be unreliable in a live office, harder to audit, and leave more liability with the clinic.
TrackStat is built to connect to the information in your EHR, either directly in the cloud or through a small communication program for server-based systems. That is the difference that keeps follow-up lists, reminders, and scheduling tools aligned with the system your team already trusts - and that keeps the access method clearer for compliance purposes.
If another company claims an integration, use the questions in this article to compare approaches. The difference between a real data connection and screen reading shows up in reliability, auditability, and how clearly the access method can be governed.
This article is for general education only and does not constitute legal advice. Clinics should consult their own compliance or legal advisors regarding their specific situation.