Free Assessment

Guide

Is a virtual medical assistant HIPAA compliant? What to check before you hire one.

By the Rekha Technologies team · Updated November 18, 2026

In one sentence

A virtual medical assistant can work within HIPAA, but no label makes that true: what protects patient information is a signed business associate agreement, trained staff, their own logins with access to only what they need, secure devices, and supervision you can check.

Virtual medical assistants answer phones, book visits, verify insurance and support billing from outside your office. Practice managers rightly ask whether patient information is safe with them. The answer depends less on the person than on the arrangement around them. Here is what HIPAA requires, and a checklist to use before you sign.

Who is responsible for what

If you hire an assistant through a company, that company is your business associate, because it handles patient information on your behalf (45 CFR § 160.103). The assistant is part of the company's workforce, and the company must protect the information under the HIPAA Security Rule and its agreement with you.

If you engage a remote assistant directly and direct their work yourself, they are generally part of your own workforce, and the duties of training, access control and supervision are yours.

Either way, your practice remains the covered entity. Handing over the work does not hand over the responsibility for how patient information is handled.

The checklist

1. A signed business associate agreement, first

The agreement must be in place before the company or its assistant sees any patient information (45 CFR § 164.502(e) and § 164.504(e)). If the company uses subcontractors that touch patient information, it needs agreements with them too.

2. Training before day one, and on a schedule

HIPAA requires a security awareness and training program for all workforce members (45 CFR § 164.308(a)(5)). Ask when the assistant was trained, what it covered, and when training repeats. Ask to see the record.

3. Their own login, never a shared one

The Security Rule requires a unique user identification for every user (45 CFR § 164.312(a)(2)(i)). With a shared login, nobody can tell who opened a chart or changed an appointment.

4. Access to only what the job needs

Grant access by role (45 CFR § 164.308(a)(4)). An assistant who schedules and verifies insurance needs the schedule, demographics and coverage details, not every part of the chart. HIPAA's minimum necessary standard asks for reasonable efforts to limit use of patient information to what the task requires (45 CFR § 164.502(b)).

5. A second step at sign-in

The Security Rule requires procedures to verify that a person signing in is who they claim to be (45 CFR § 164.312(d)). A second sign-in step, such as a code on a phone, is a common way to meet it, and it stops a stolen password from being enough.

6. A secure device and a private workspace

Ask whose computer the assistant uses, how it is kept updated and protected, and whether patient information can be saved on it. The Security Rule's physical safeguards cover workstations, wherever they are (45 CFR § 164.310). Calls about patients should happen where nobody else can overhear.

7. Activity you can review

Your EHR and practice management system record who accessed what. HIPAA requires a practice to review records of system activity regularly (45 CFR § 164.308(a)(1)(ii)(D)). Include the assistant's account in those reviews.

8. Access removed the day the work ends

Ask how quickly the company removes access when an assistant leaves, and remove the login in your own systems on the same day (45 CFR § 164.308(a)(3)(ii)(C)).

9. A plan for when something goes wrong

A business associate must notify your practice of a breach of unsecured patient information without unreasonable delay, and within 60 days of discovering it (45 CFR § 164.410). Your agreement should say how incidents are reported and to whom.

Questions to ask the company

  • Where will the assistant work, and on whose equipment and network?
  • Who supervises the assistant day to day, and who covers absences?
  • How is the assistant's work checked for quality, and how often?
  • What will the assistant be able to see in our systems, and who decides?
  • How, and how fast, will you tell us about a security incident?
  • Can we see the training record and your security policies?

Set up your side before day one

The safeguards above only work if your own systems are ready. Before the assistant starts, create their login with the right role, turn on the second sign-in step, and write down which tasks they will do and which they will not. Tell your staff who the assistant is and how to reach them, so nobody shares a password to "help out". Then put a date in the calendar for the first review of the assistant's access and activity, a month or so after they start.

Red flags

  • The company will not sign a BAA, or wants to sign it "later".
  • The assistant is asked to use your login, or several people share one.
  • Patient information is kept on personal devices or personal email.
  • A certificate is offered as proof of compliance. No official certification for HIPAA exists; ask about the agreement, the training and the safeguards instead.
  • Nobody can tell you who supervises the assistant, or who covers when they are out.

Where Rekha Technologies fits

Our healthcare virtual assistants are HIPAA-trained before they start, and we sign a BAA with your practice before any work begins. Each assistant is a named, full-time team member who works in your systems, with a trained backup and an operations lead who checks quality every day. We are US-led with global delivery teams. Our operations follow HIPAA's administrative, physical and technical safeguards; our ISO certification and SOC 2 Type II audit are in progress.

This guide is general information, not legal advice.

Sources

Quick answers

Questions about virtual assistants and HIPAA.

Is a virtual medical assistant HIPAA compliant?

An assistant can work within HIPAA, but compliance comes from the arrangement, not a label: a signed business associate agreement with the company, training, unique logins, access limited to the job, secure devices and supervision. Your practice remains the covered entity and should check each of these before granting access.

Does a virtual assistant company need to sign a BAA?

Yes. A company whose staff handle your patients' information on your behalf is a business associate under HIPAA (45 CFR § 160.103). The agreement must be signed before the company or its assistant receives any patient information (45 CFR § 164.502(e)).

Can a virtual assistant use our EHR login?

No. Each person needs their own login. The Security Rule requires a unique user identification for every user (45 CFR § 164.312(a)(2)(i)), so the record shows who did what. A shared login hides that.

Is patient information safe with a remote assistant?

It can be, when the safeguards are real: their own login with a second sign-in step, access limited to the job, a secure device, a private workspace, activity you can review, and access removed the day the work ends. Ask the company to show you each one.

What happens if a virtual assistant company has a data breach?

As your business associate, the company must notify your practice of a breach of unsecured patient information without unreasonable delay and within 60 days of discovering it (45 CFR § 164.410). Your practice then handles the required notifications, so your agreement should say exactly how incidents are reported.

How often should a virtual assistant receive HIPAA training?

HIPAA requires security training for all workforce members but does not fix an interval. Training before access is granted, every year after that, and whenever policies change is the widely followed practice. Ask the company for its training record.

Thinking about a virtual assistant?

Tell us which tasks you want off your team's plate, on a free 30-minute call.

Book a free 30-minute assessment
Book a free 30-minute assessment