SimplyBook.me
Hosted booking with plan-based booking, provider and custom-feature limits. Deposits require Accept Payments; allow feature capacity for Google/Outlook calendar sync.
Treat “HIPAA” as a compliance requirement to investigate—not a marketing checkbox. Start with data flow, contracts and notification behavior before comparing design.
A scheduling product can have privacy controls and still be unsuitable for your exact healthcare workflow. Before you let a booking system handle protected health information, confirm what data is collected, where it is stored, which integrations receive it and whether the vendor will execute the agreements your organization requires.
SimplyBook.me’s official pricing currently lists a HIPAA custom feature on its Standard tier and above. That is a useful starting signal, but it does not remove the need to validate the BAA, configuration and exact workflow before using the platform for PHI.
Hosted booking with plan-based booking, provider and custom-feature limits. Deposits require Accept Payments; allow feature capacity for Google/Outlook calendar sync.
WordPress booking plugins can be appropriate for many healthcare-adjacent scheduling workflows, but BookingToolScout does not label a WordPress plugin “HIPAA compliant” merely because it has secure payments or appointment controls. Hosting, plugins, email delivery, analytics and administrative access all affect the environment.
If your booking form does not collect PHI and simply routes users to a separate compliant patient system, the technical requirements may be different. Document that architecture before choosing software.