Checked November 16, 2026

How do you choose HIPAA-compliant med spa software?

Any software that stores your charts, consent forms, before-and-after photos or client messages is a business associate under HIPAA, and the law requires a signed business associate agreement with it before patient information goes in — a “HIPAA compliant” badge on a pricing page is not that agreement. Beyond the paperwork, the Security Rule names the controls to ask about: unique user IDs, role-based access, audit logs, encryption and automatic logoff. The checklist below covers the ten questions, including the 60-day breach notification deadline a vendor must be able to meet.

Why the agreement comes before the feature list

The Department of Health and Human Services defines a business associate as a person or entity that performs functions or provides services involving protected health information on behalf of a covered entity. A med spa that operates under a medical director and documents treatments is handling PHI, and the booking, charting and photo software it uses is performing services with that PHI. HHS requires the covered entity to obtain satisfactory assurances in writing, in the form of a contract containing the elements set out at 45 CFR 164.504(e).

HHS’s cloud-computing guidance closes the obvious loophole: a cloud provider that creates, receives, maintains or transmits electronic PHI is a business associate even if it stores only encrypted data and holds no key, and the conduit exception does not apply to storage. Using such a provider without a business associate agreement puts the covered entity in violation of the HIPAA Rules. Marketing language about compliance, however sincere, does not substitute for the signed document.

What “addressable” means in the Security Rule

The technical safeguards at 45 CFR 164.312 are a mix of required and addressable specifications. Unique user identification is required. Encryption at rest, encryption in transit and automatic logoff are addressable. Addressable does not mean optional: the covered entity must implement the specification if it is reasonable and appropriate, or document why not and adopt an equivalent measure. When a vendor tells you a control is “not required by HIPAA”, the right follow-up is whether they implement it anyway and can show you.

Audit controls — mechanisms that record and examine activity in systems containing electronic PHI — are a standard, not an addressable item, and so are integrity controls and person-or-entity authentication. Multi-factor authentication is not named in the current rule text, but HHS’s Office for Civil Rights has recommended it in its cybersecurity newsletters, and there is no good reason for a vendor holding clinical records not to offer it.

Photos, messages and the places PHI leaks

Before-and-after photographs of a face are protected health information, and they need the same access, audit, encryption and retention controls as the chart. Ask where photos are stored, whether image links expire, who inside the vendor can view them, and how a consented marketing copy is separated from the clinical original. A photo that is easy to text to a client is also easy to text to the wrong one.

Appointment reminders, two-way texting and email are the most common places PHI escapes: a confirmation that names the treatment, a reminder that mentions a prescription, a support ticket with a screenshot. Ask the vendor how messages are kept generic by default, whether PHI is excluded from application logs and analytics, and whether their subcontractors — messaging, hosting, analytics — are themselves bound by downstream agreements, which 164.504(e) requires.

The breach clock, and leaving the vendor

Under the Breach Notification Rule, individuals must be notified without unreasonable delay and in no case later than 60 days after a breach is discovered. Breaches affecting 500 or more individuals must be reported to the HHS Secretary within the same 60 days and, where more than 500 residents of a state are affected, to prominent media outlets; smaller breaches go on an annual log due within 60 days of the end of the calendar year. A business associate must notify the covered entity no later than 60 days after discovery, and your agreement may set a shorter deadline — many practices ask for five to ten days so they can meet their own obligations.

Finally, read the exit terms. HHS’s sample provisions call for PHI to be returned or destroyed at termination where feasible, and your agreement should state the export format, the window in which you can retrieve records, and any fee. The time to negotiate that is before signature; software that is painless to join and painful to leave is a compliance risk as much as a commercial one.

Ten questions for any med spa software vendor

  1. 1. Will you sign a business associate agreement, and what does it contain?

    The agreement should cover permitted uses and disclosures, safeguards, breach reporting duties and timelines, flow-down to subcontractors, and return or destruction of PHI at termination — the elements HHS lists at 45 CFR 164.504(e). Ask for the full text before you commit, not after.

  2. 2. Does every staff member get a unique user ID?

    Unique user identification is a required specification under 164.312(a)(2)(i). Shared front-desk logins make every audit log useless, so confirm the vendor supports one login per person and that pricing does not push you toward sharing accounts.

  3. 3. Can access be limited by role to the minimum necessary?

    A receptionist should see the schedule, not the chart. Ask whether permissions are granular enough to separate booking, checkout, clinical notes and photos, and whether a provider can be limited to their own patients.

  4. 4. Is multi-factor authentication available for every user?

    Not named in the current rule text, but recommended by HHS’s Office for Civil Rights and a reasonable expectation for any system holding clinical records. Ask whether it can be enforced for all accounts rather than left optional.

  5. 5. Does the system log off idle sessions automatically?

    Automatic logoff is an addressable specification under 164.312(a)(2)(iii). A tablet left open in a treatment room is the everyday version of this risk; confirm the idle timeout exists and that you can set it.

  6. 6. Are there audit logs showing who viewed and changed what?

    Audit controls are a standard under 164.312(b). You should be able to see which user opened which record and when, and export that log if you ever need to investigate an incident.

  7. 7. Is data encrypted in transit and at rest?

    Both are addressable under 164.312(a)(2)(iv) and 164.312(e)(2)(ii), meaning the vendor must either implement them or document an equivalent. Ask for a plain statement of both, including for backups.

  8. 8. How are before-and-after photos stored and shared?

    Photos are PHI. Ask for private storage, expiring links rather than permanent public URLs, access restricted by role, and a clear separation between the clinical image and any copy the client has consented to for marketing.

  9. 9. Is PHI kept out of texts, emails, logs and analytics?

    Reminders should not name the treatment by default, support tickets and application logs should not carry chart content, and messaging and analytics subcontractors should be covered by downstream agreements.

  10. 10. What are your breach notification duties and your exit terms?

    The vendor must notify you no later than 60 days after discovering a breach; ask for a shorter contractual deadline so you can meet your own 60-day duty to individuals and, for 500 or more people, to HHS. Confirm how your data is exported or returned at termination, in what format and at what cost.

If you’re switching

Whichever platform you choose, move in this order: sign the agreement, configure roles and multi-factor authentication, import clients, and only then start charting and photographing. Tersavia’s free platform attaches intake and consent forms to the client profile, stores before-and-after photos, and supports role-based staff access, with no contract and no per-location, per-user or per-calendar charge.

The AI phone receptionist is an optional paid add-on and the platform is fully functional without it.

How switching worksAlternatives

Questions

Does a med spa need a business associate agreement with its booking software?

If the software stores charts, consent forms, photos or messages that identify a patient and relate to their treatment, it is handling protected health information on your behalf and is a business associate under HIPAA. HHS requires a written agreement with the elements of 45 CFR 164.504(e) before that information is shared.

Is “HIPAA compliant” software the same as having a BAA?

No. Compliance language describes the vendor’s own controls; a business associate agreement is the signed contract HIPAA requires between you and the vendor. HHS guidance states that using a cloud provider for electronic PHI without one is a violation, regardless of how the product is marketed.

How quickly must a software vendor report a data breach?

A business associate must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery, under 45 CFR 164.410. You then have your own 60-day clock to notify affected individuals, and HHS if 500 or more people are involved, so many practices negotiate a shorter vendor deadline.

Does HIPAA require encryption of med spa records?

Encryption at rest and in transit are addressable specifications in the Security Rule. That means a covered entity must implement them if reasonable and appropriate, or document why not and use an equivalent safeguard; in practice, any vendor holding clinical records should offer both.

Are before-and-after photos protected health information?

Yes. A photograph that identifies a patient and relates to their treatment is PHI and needs the same access controls, audit logging, encryption and retention rules as the written chart, plus documented consent before any copy is used in marketing.

Book your free setup

15 minutes · no card, no contract · free forever

Sources and caveats

This guide is vendor-neutral and names no software product. Regulatory statements paraphrase HHS guidance and 45 CFR Parts 160 and 164 as checked on November 16, 2026; it is general buyer guidance, not legal advice, and your medical director or counsel should review your own agreements.

All vendor figures are published list prices as of November 16, 2026, not negotiated rates and not drawn from any private account. Vendors change pricing frequently — verify current terms directly with the vendor before making a decision. Where third-party guides disagree with a vendor’s own pricing, we have said so rather than picking the number that suited us.

Our bias, stated plainly. We sell competing software and we want your business. Every figure above is checkable against the vendor’s own pricing page or your own invoice, and we would rather you check than take our word.