GoldenrozBook a call

HIPAA for a small practice: email, scheduling and website

HIPAA does not certify products, so no email service, scheduling tool or website is HIPAA compliant by itself. A practice is compliant when each vendor that handles patient information has signed a business associate agreement, the systems are configured with safeguards chosen through a documented risk analysis, and staff follow written procedures. This post explains the technical side in general terms and is not legal advice.

A gold sphere under a clear glass dome on a navy base.

Read this first

This post is general technical information written from an IT engineer’s point of view. It is not legal advice. Goldenroz is not a HIPAA auditor and does not issue compliance attestations. The statements about what HIPAA permits are drawn from guidance published by the US Department of Health and Human Services (HHS) on hhs.gov. Rules and guidance change, so confirm anything that matters with the source and with your own counsel.

What “HIPAA compliant” means for a tool

There is no government certification that makes a product HIPAA compliant. A vendor that uses the phrase usually means two things: it will sign a business associate agreement, and its product has the security features a practice needs to meet its own obligations.

Compliance belongs to the practice. In technical terms it comes down to three layers:

  1. Contract. A business associate agreement (BAA) with every vendor that handles protected health information (PHI) for you.
  2. Configuration. The product is set up securely. A capable product with multi-factor authentication switched off and one shared login does not protect anyone.
  3. Procedure. Staff know what may go into an email, a reminder or a web form, and there is a written record of the decisions.

The Security Rule ties these together with a risk analysis: a documented review of where electronic PHI lives, what could go wrong, and which safeguards you chose. Every answer below assumes that review exists.

Business associate agreements

A business associate is a person or company that creates, receives, maintains or transmits PHI on behalf of a covered entity such as a practice. For a small clinic, that typically includes the email provider, the scheduling or practice management system, the reminder service, the website form or hosting provider if forms carry patient information, the backup provider and the outside IT company.

Two points from HHS cloud computing guidance surprise people:

  • A cloud provider that stores only encrypted PHI and does not hold the decryption key is still a business associate.
  • A practice that uses a cloud provider to maintain electronic PHI without first signing a BAA is in violation of the HIPAA Rules.

So the first task is an inventory. List every system where a patient’s name can appear next to anything about their care, and check that a signed agreement exists for each. If a vendor will not sign one, patient information cannot go into that product.

Email

HHS has answered the email question directly. Its guidance says the Privacy Rule allows providers to communicate with patients by email, provided they apply reasonable safeguards. The same guidance notes that the Privacy Rule does not prohibit unencrypted email for treatment-related communication, that practices should take precautions such as checking the address before sending and limiting the information included, and that a patient who asks for a more secure channel should be offered one.

The Security Rule adds technical requirements. HHS guidance states that the rule does not expressly prohibit email for sending electronic PHI, and that the practice must assess its use of open networks, select a way to protect the information in transit, and document the decision. Encryption is “addressable”: implement it if your risk assessment finds it reasonable and appropriate, or document why not and implement an equivalent alternative. In January 2025 HHS published a proposed rule that would make encryption required with limited exceptions. Check hhs.gov for its status before you rely on the addressable standard.

What that means when setting up a practice mailbox:

  • Use a business email plan from a provider that signs a BAA. Confirm on the provider’s own documentation which plans are covered.
  • One named account per person, with multi-factor authentication. No shared front-desk password.
  • Turn on the provider’s message encryption feature for messages that contain clinical detail, and teach staff when to use it.
  • Disable automatic forwarding to personal mailboxes.
  • Apply the same controls to phones: screen lock, device encryption, and the ability to remove the mailbox from a lost phone.
  • Keep audit logging on, and know how to retrieve it.

Patients email the practice from their own accounts, and that is their choice. The practice’s obligations concern what it sends and how it stores what it receives.

Scheduling software

A booking record contains a patient’s name, contact details, a date, a provider and often a reason for the visit. That is PHI, and the scheduling vendor is a business associate.

A general-purpose booking tool can be technically excellent and still be the wrong choice if the vendor does not offer a BAA on the plan you are using. Check that before anything else, then look at configuration:

  • Individual staff logins with roles, so a receptionist does not have administrator rights.
  • An audit trail of who viewed and changed appointments.
  • Control over what the confirmation email and calendar invitation contain. Many tools put the appointment type in the subject line by default.
  • Calendar synchronization. Syncing appointments to a personal calendar account copies PHI to a system with no agreement.
  • Export and deletion, so you can leave the vendor with your data and without leaving copies behind.

If patients book through a chat or messaging assistant, the same rules apply to every component in the chain: the messaging channel, the automation platform, any AI model provider and the calendar. Our appointment booking bot page describes how we build these. For a clinic, the design starts from which of those components will sign a BAA and what information the bot is allowed to ask for.

Appointment reminders

HHS guidance treats appointment reminders as a permitted communication and advises limiting the amount of information disclosed. Patients also have the right to ask for communication by a different channel or at a different address, and practices must accommodate reasonable requests.

A sensible reminder policy:

  • Content is limited to practice name, date and time. No diagnosis, procedure, specialty detail or test result.
  • The channel preference (text, email, call) is recorded per patient and respected.
  • Opt-out works and is recorded in the patient’s file.
  • The reminder vendor has signed a BAA.
  • Replies from patients land somewhere staff read and that is covered by the same safeguards.

Text messages also fall under telephone consumer protection rules that are separate from HIPAA. Consent wording is a question for counsel.

Website and web forms

A brochure website with opening hours and directions holds no PHI. The moment the site has a contact form with a free-text “how can we help” field, an appointment request or a patient intake form, it is collecting health information from identifiable people.

For those forms:

  • Submissions travel over HTTPS and are stored with a vendor that has signed a BAA, or are delivered straight into the practice system that has one.
  • The form does not email the full submission in plain text to a general inbox.
  • Access to stored submissions is limited to named staff, and old submissions are deleted on a schedule.
  • Fields ask for the minimum needed to book or respond.

Tracking and analytics scripts

HHS’s Office for Civil Rights published a bulletin on online tracking technologies in December 2022. On June 20, 2024, a federal court in Texas vacated part of it, the part concerning visits to public, unauthenticated pages. The HHS page says the agency is evaluating its next steps. The remaining guidance still describes cases where tracking tools on a practice’s site can receive PHI, for example on a scheduling page where a visitor enters an email address, or inside a patient portal.

The cautious engineering position is simple. Keep third-party tracking scripts off any page where a patient logs in, books or submits a form, unless the tracking vendor has signed a BAA. Decide the rest with counsel.

Questions to ask every vendor

Question Why it matters
Will you sign a BAA, and on which plan? Without it, PHI cannot go into the product
Is data encrypted in transit and at rest? Supports your encryption decision and breach analysis
Does every user get an individual login with MFA? Access control and accountability
Is there an audit log, and how long is it kept? Needed to investigate an incident
Which subcontractors handle our data? Each one is part of your chain of agreements
How do you notify us of a security incident? You have notification duties that depend on theirs
How do we export and delete our data when we leave? Avoids orphaned copies of PHI
What do notification emails and texts contain by default? Defaults often include more detail than a reminder should

What IT can and cannot do

An IT provider can configure mailboxes, enforce multi-factor authentication, encrypt laptops, set up backups and test a restore, restrict form submissions, document the setup and collect vendor agreements into one folder. Remote access to the practice’s systems needs the same care, and our post on VPN vs ZTNA covers that choice.

An IT provider cannot decide your legal obligations, write your privacy notice, sign off your risk analysis or declare you compliant. Those belong to the practice with a compliance consultant or attorney.

What to do next

Write down every system that touches patient information, then mark three columns for each: BAA signed, MFA on, named accounts only. The blanks are your work list. For a small private clinic, our IT support for medical practices is a defined setup project covering website, email, scheduling and reminders with the technical safeguards documented. Larger provider organizations with servers, networks and multiple sites are covered under healthcare IT services, where projects start at $25,000 at a fixed price per phase and managed IT is a monthly retainer quoted after an assessment.

Questions buyers ask

Is regular email HIPAA compliant?

HHS guidance says the Privacy Rule allows providers to communicate with patients by email if they apply reasonable safeguards, and the Security Rule does not expressly prohibit sending electronic PHI by email. The practice still needs a business associate agreement with its email provider, access controls, and a documented decision about encryption. A free consumer mailbox without an agreement does not meet that bar.

Does HIPAA require email encryption?

Under the current Security Rule, encryption is an addressable implementation specification. HHS explains that a practice must implement it if its risk assessment finds it reasonable and appropriate, and otherwise must document why and implement an equivalent alternative. HHS published a proposed rule in January 2025 that would make encryption required, so check hhs.gov for the current status.

What is a business associate agreement?

It is the written contract HIPAA requires between a practice and any vendor that creates, receives, maintains or transmits protected health information on the practice's behalf. HHS guidance on cloud computing states that using a cloud provider to maintain electronic PHI without such an agreement is a violation of the HIPAA Rules.

Can a practice send appointment reminders by text or email?

HHS guidance treats appointment reminders as permitted communications and advises limiting the information in them. Keep reminders to the date, time and practice name, leave out the reason for the visit, and honor a patient's request to be contacted a different way. Text messages are also subject to consumer protection rules outside HIPAA, so ask counsel about consent.

Can Goldenroz certify that our practice is HIPAA compliant?

No. Goldenroz is not a compliance auditor or a law firm. We build and document technical safeguards such as access control, encryption settings, backups and logging, and we help collect vendor agreements. The risk analysis sign-off, policies and legal interpretation belong to the practice and its compliance or legal advisers.

Written by

CTO and technology partner

Shai leads the technology side: business software, SaaS and mobile apps, payments and escrow systems, Postgres security, AI agents built with Claude Code and MCP, and IT and infrastructure projects with senior infrastructure engineers.

Keep reading

Talk to the person who will do the work

One hour, no sales team. You talk to Daniel or Shai, we look at your account or your product, and you leave with a clear next step.

Or send the details

Book a 1-hour consultationWhatsApp us