How do I check if my clinic's booking system is secure?
A plain-English way for clinic owners to check an online booking system: map the patient data it holds, get a business associate agreement, ask the vendor eight questions and fix the basics on your side.
- Author
Umair Mateen- Published
- Reading time
- 6 min
- Category
- Engineering
Ideas in this post
Tap one for a 5-second answer. Underlined words in the article work the same way.
0 of 4 understood

Start by treating your booking system as a place where patient information lives, because it usually is: names, contact details, appointment reasons and sometimes intake forms. To check it, you map what data it holds and who can reach it, get written answers from the vendor on a short list of security questions, and confirm the basics on your side, such as staff logins and who still has access. In the US, this check is also part of the risk analysis that the HIPAA Security Rule requires.
The HIPAA points apply to US covered entities. Elsewhere, data-protection law (such as GDPR in the EU and UK) has its own rules for health data, and the same practical checks are a good place to start.
Step 1: Write down what the booking system holds and where it goes
List the patient information the system collects (name, contact details, date of birth, reason for visit, insurance, uploads, messages) and where it travels: the vendor's servers, reminder texts and emails, your calendar, payment tools and records system.
Quick check · Myth or fact
Encryption: myth or fact?
Decide for yourself first, then tap each statement to check it.
0 of 4 checked
From the explainer What is encryption? Explained with a sealed envelope
HHS guidance on risk analysis says the analysis must cover all electronic protected health information (ePHI) a practice creates, receives, maintains or transmits, whatever the medium, and that you should identify and document where it is stored and which vendors handle it. If patient names sit next to appointment details in your booking tool, include it in that list and confirm with your compliance adviser how it is classified.
Step 2: Confirm you have a business associate agreement (US)
A business associate agreement (BAA) is a contract in which a vendor that handles patient information on your behalf agrees to protect it. HHS guidance on cloud services says a provider that stores ePHI for a covered entity is a business associate even if it only stores and does not hold the key, and that using such a provider without a BAA breaks the HIPAA rules.
Ask your booking vendor for its BAA. According to HHS, the agreement should set out how the vendor may use and disclose the data, require it to safeguard the data and report security incidents to you, and require the data to be returned or destroyed when the contract ends where that is feasible. If a vendor will not sign one, treat that as your answer.
Step 3: Ask the vendor these questions, in writing
HHS points out that encryption alone does not cover everything: you still need the data to be available, recoverable and properly controlled. Its guidance lists topics worth settling in the service agreement, including availability, and recovery, how data is returned at the end, who is responsible for which security tasks, and limits on how data is used and kept. Turn those into questions:
- Is patient data encrypted when it is sent and when it is stored?
- Can every staff account use two-step verification (a code or app prompt on top of the password)?
- Can we give staff different permission levels, so a receptionist does not see what a clinician sees? This is called role-based access.
- Does the system keep an audit trail of who viewed or changed a booking, and can we see it?
- How are backups made, and how quickly can service be restored after an outage?
- How fast will you tell us about a security incident, and how?
- In which country is our data stored?
- How do we get all our data back if we leave, and when is it deleted?
HHS also notes that the HIPAA rules do not force a cloud vendor to hand over security documentation or allow audits; you can ask for that in the contract. Independent reports, such as a SOC 2 report, help but do not replace your own checks.
Step 4: Check your own side
Then check the clinic side:
- Accounts. Everyone has their own login; no shared front-desk password. Remove people who have left.
- Two-step verification. Switch it on for the booking system and for the email accounts that receive booking notifications.
- Devices. Front-desk computers and phones are kept up to date and locked when unattended.
- Reminders and forms. Reminder texts and emails say no more than they need to. Online forms ask only for what you use.
- Scams. Staff know how to spot fake "your booking account is locked" messages.
These line up with the topics in the UK National Cyber Security Centre's free guide for small organisations: securing email, securing important online accounts, protecting devices, backing up data and spotting attacks.
Step 5: Record what you found and repeat it
HHS says risk analysis results must be documented, though no particular format is required, and that the process should be ongoing, with a fresh look after events such as a security incident, staff turnover or new technology. Note each gap, how serious it is and what you will do about it. Repeat it when you change vendor or add payments or intake forms.
What it costs and how long it takes
- Risk assessment tool: the US government's Security Risk Assessment Tool (version 3.7) is a download from HealthIT.gov, as a Windows app or an Excel workbook, with no price listed. It is aimed at small and medium providers, and its own disclaimer says using it does not guarantee compliance. The page says what you enter stays on your own computer.
- Your own time: the NCSC says many of its recommendations can be done in as little as five minutes each. Vendor answers take longer.
- Outside help: a security review or penetration test is priced by scope; there is no reliable public average, so ask for a written scope before a quote.
Common mistakes
- Assuming the booking tool is "just a calendar" and leaving it out of the risk analysis.
- Accepting "we're HIPAA compliant" on a website instead of a signed BAA and written answers.
- Sharing one login at the front desk, so no shows who did what.
- Putting appointment reasons in reminder texts that anyone holding the phone can read.
- Checking once and never again after adding new features.
A checklist you can use today
- List the patient data your booking system collects and where it is sent.
- Find your signed BAA with the vendor (US), or ask for one.
- Send the vendor the eight questions above and keep the replies.
- Turn on two-step verification for every staff account and booking email inbox.
- Remove accounts for anyone who no longer works with you.
- Read a reminder text as a stranger would; cut anything sensitive.
- Confirm how you would get your data back if you left the vendor.
- Record the gaps you found, who owns each fix and a date to check again.
If you want a second pair of eyes on your booking system or a vendor's answers, The DevDrift can help: get in touch.
Sources
You’ve read the news. Now understand it.
- Learn · 5 min · Myth or factWhat is encryption? Explained with a sealed envelopeEncryption scrambles data with a secret key so only someone with the right key can read it. Explained as the difference between a postcard and a sealed envelope.Start in 5 seconds →
- Learn · 5 min · Spot the weak pointWhat are backups? Explained with a spare key at a friend's houseA backup is a separate copy of your business data, kept out of reach of whatever goes wrong with the original. Explained with a spare house key left at a friend's house.Start in 5 seconds →
- Learn · 5 min · What would you do?What is role-based access? Explained with office keycardsRole-based access control gives permissions to job roles, then gives people the roles they need. Explained with office keycards that open only certain floors.Start in 5 seconds →
- Learn · 5 min · Myth or factWhat is an audit trail? Explained with a visitor logbookAn audit trail is a time-ordered record of who did what in a system, when and with what result. Explained with the visitor logbook at an office reception desk.Start in 5 seconds →


