HIPAA & Security

HIPAA-Compliant Virtual Assistants for Eye Care Practices

EyeCareWorks is built exclusively for optometry and ophthalmology practices. Every virtual assistant we place completes formal HIPAA training, holds a HIPAA Certificate of Completion, and signs a Business Associate Agreement directly with your practice. Your VA works inside your systems, under your permissions, with every access logged.

✓
Signed BAA
✓
HIPAA Certificate of Completion
✓
Every Access Logged
✓
Signed BAA
✓
Multi-factor authentication
✓
Encrypted sessions
✓
Every access logged
HIPAA Certificate of Completion
Our Operating System

HIPAA Compliance at EyeCareWorks

HIPAA compliance at EyeCareWorks is not a feature we advertise. It is the operating system our entire service runs on. Before a virtual assistant ever logs into a practice's systems, three things have already happened: they have completed formal HIPAA training and earned a HIPAA Certificate of Completion, they have signed confidentiality agreements covering all PHI handling, and they have signed a Business Associate Agreement (BAA) directly with your practice. From that point forward, the safeguards required under the HIPAA Security Rule, administrative, physical, and technical, are actively maintained, documented, and available for your review.

The Difference

Why Eye Care Practices Choose EyeCareWorks for HIPAA Compliance

Specialized Eye Care Knowledge

Our VAs are trained on optometry and ophthalmology workflows before placement: vision plans versus medical insurance, refraction data, OCT imaging, and recall protocols. PHI is handled by people who understand exactly what it is.

Dedicated Model

You work with the same assistant every day. No rotating pool, no shared logins, no unknown hands on your patient data. The result is a smaller attack surface and a cleaner audit trail.

Built for Compliance

HIPAA Certificate of Completion, signed confidentiality agreements, secured workstations, and documented incident response procedures, all in place before day one, not bolted on afterward.

Affordable Peace of Mind

A flat $10/hour includes every safeguard described on this page. There is no "security package" upsell, because compliance is not optional equipment. Your practice stays secure, efficient, and focused on patient care.

The Three Safeguard Pillars

How We Protect PHI

The HIPAA Security Rule organizes a business associate's obligations into three categories of safeguards. Here is how EyeCareWorks and every assistant we place implement each one, not as policy language, but as daily practice.

Administrative Safeguards

Workforce screening, formal HIPAA training, and a HIPAA Certificate of Completion before placement. Signed confidentiality agreements covering all PHI handling, documented policies and procedures, a zero-tolerance sanction policy for mishandling, and incident response procedures written down before they are ever needed.

Physical Safeguards

Secured, dedicated workstations on hardwired internet connections. No personal devices in the workspace, locked screens when unattended, and restricted local storage so patient data never leaves your systems. The workstation environment is part of the compliance program, not an afterthought.

Technical Safeguards

Encrypted remote sessions, multi-factor authentication on assistant accounts, role-based access built on least privilege, and automatic session timeouts on every workstation. All work happens inside your systems under permissions you control, so every access lands in your own audit trail, backed by secure time and activity tracking.

What Compliance Actually Requires

What a HIPAA-Compliant Virtual Assistant Arrangement Requires

HIPAA compliance is not a property of virtual assistants as a category. It is a property of a specific arrangement, built from four layers you can verify before any patient information moves. Here is what each layer means and how EyeCareWorks meets it.

A Business Associate Agreement

Anyone who handles protected health information on your behalf is a business associate, and HIPAA requires a written BAA before any PHI flows. It binds the assistant to safeguard patient information, report incidents, and use data only for the work you assign. Your EyeCareWorks assistant signs a BAA directly with your practice before day one. No BAA, no arrangement.

Trained People, With Documentation

HIPAA requires workforce training, and that requirement follows the work wherever it sits. Every assistant completes Privacy and Security Rule training and earns a HIPAA Certificate of Completion before placement, with dates and content you can ask to see. Eye care adds its own detail: appointment history, optical purchases and diagnoses are all PHI, and the minimum-necessary principle governs every task.

Technical Safeguards on the Remote Connection

Individual, scoped credentials rather than shared logins, so every action is attributable in your audit trail. Multi-factor authentication on assistant accounts. Encrypted remote sessions into your EHR or practice management system. Controlled workstations with no local storage of patient data. A written incident response process the assistant can describe without looking it up.

Your Side of the Arrangement

Compliance is bilateral. Grant access role by role (the biller does not need the optical sales module), keep the audit logs your systems already generate, include remote staff in your own policies and risk analysis, and deactivate credentials promptly when a role ends. We walk every practice through these steps during onboarding.

Remote placement done properly is not a compliance compromise. Done well, it is often tighter than the in-office equivalent, because access is scoped, logged and monitored in ways a shared front-desk terminal never was.

Due Diligence

Six Questions to Ask Any Virtual Assistant Provider

If you are evaluating remote staffing for your practice, ours or anyone's, these are the questions a diligent practice administrator should ask before signing anything. Here is where EyeCareWorks stands on each.

“Will you sign a Business Associate Agreement?”

Yes. Your assistant signs a BAA directly with your practice before any PHI access begins, and we make sure it is executed as part of onboarding. A provider who hesitates on this question has already answered it.

“How are your assistants trained on HIPAA?”

Formal HIPAA training plus a HIPAA Certificate of Completion before placement, kept current throughout the engagement. Ask any vendor who issued their certificate, and when it expires.

“Where does patient data live?”

In your systems, full stop. Our VAs work inside your EMR under permissions you control. PHI is never downloaded, exported, or stored on the assistant's workstation.

“How is remote access secured?”

Secured workstations, hardwired connections, multi-factor authentication, encrypted sessions, automatic timeouts, and activity logs are available for your review.

“What happens if something goes wrong?”

Documented incident response procedures, prompt notification to your practice, and a zero-tolerance policy for PHI mishandling: enforced, not aspirational.

“Can we see your documentation?”

Yes. Compliance documentation, including training records, certificate status, and security protocols, is available to your practice on request, before and during the engagement.

The Definition

What Makes a Virtual Assistant HIPAA Compliant

A HIPAA compliant virtual assistant is a remote team member who handles protected health information under a signed Business Associate Agreement, with documented HIPAA training, technical safeguards on the remote connection, and access limited to what the role needs. Compliance belongs to that arrangement, not to the person or the vendor, which is why the same assistant can be compliant in one practice and not in another.

The legal basis is the business associate rule. Anyone who creates, receives, maintains or transmits PHI on a practice's behalf is a business associate, and the practice must have written assurances from them before any PHI moves. In the words of the U.S. Department of Health and Human Services:

The HIPAA Rules permit a covered entity to disclose PHI to a business associate if the covered entity obtains satisfactory assurances, in the form of a contract or other written arrangement (collectively referred to as a "business associate agreement," or BAA), that the business associate will appropriately safeguard the information, among other obligations.HHS, Business Associates guidance

HHS also notes that "a business associate is also directly liable for complying with certain provisions of the HIPAA Rules." That is why an EyeCareWorks assistant signs the BAA directly with your practice: the person handling your patient information is the person bound by it.

Trained Versus Certified

"HIPAA Certified" Virtual Assistants: What HHS Actually Says

Many providers advertise HIPAA certified virtual assistants. There is no government HIPAA certification. HHS answers the question directly in its Security Rule FAQ:

HHS does not endorse or otherwise recognize private organizations' "certifications" regarding the Security Rule, and such certifications do not absolve covered entities of their legal obligations under the Security Rule.HHS, Are we required to certify our organization's compliance?

What a certificate can honestly show is that a person completed HIPAA training on a known date, with content you can review. That is what every EyeCareWorks assistant holds: a HIPAA Certificate of Completion covering the Privacy and Security Rules, kept current during the engagement, and available to your practice on request. We say HIPAA trained rather than HIPAA certified, because that is the accurate description and because the certificate is one layer of the arrangement, not a substitute for the other three.

Eye Care Specifics

HIPAA Security for Eye Care Practices: What the Rules Require

Optometry and ophthalmology practices are covered entities. The American Optometric Association puts it plainly: "A doctor of optometry is considered a 'covered entity' if he/she transmits any information in an electronic form in connection with a transaction," and "for each of your business associates, you are required to obtain an agreement that requires them to appropriately safeguard your patients' PHI" (AOA, HIPAA resources). Eye care carries more PHI per visit than most specialties: refraction data, OCT and retinal images, vision plan and medical insurance details, and optical purchases tied to a diagnosis are all protected.

The HIPAA Security Rule requires three categories of safeguards for electronic PHI, and HHS notes the rule "was designed to be scalable, and technology neutral to all different sizes of regulated entities." A solo practice is not exempt; it is expected to meet the same standards at its own scale.

Safeguard categoryWhat HHS requiresHow it applies to a remote assistant
AdministrativeRisk analysis, workforce training, access management, sanction policy, incident procedures, business associate contractsSigned BAA, documented training, defined role and access, written incident response, a sanction policy the assistant has acknowledged
PhysicalFacility access, workstation use and security, device and media controlsSecured dedicated workstation, hardwired connection, locked screen when unattended, no personal devices in the workspace, no local storage of PHI
TechnicalAccess control, audit controls, integrity, authentication, transmission securityIndividual credentials, multi-factor authentication, encrypted remote sessions into your systems, every action logged in your own audit trail

Enforcement has reached eye care

In February 2025 HHS imposed a $1.5 million civil money penalty on Warby Parker after a cyberattack exposed the PHI of nearly 200,000 people; the findings included "a failure to conduct an accurate and thorough risk analysis" and a failure to review records of system activity (HHS press release). In August 2026 Azul Vision, a California optometry and ophthalmology provider, paid $50,000 and entered a two year corrective action plan after failing to provide a patient's records within 30 days (HHS press release). Neither case involved a virtual assistant; both show that OCR looks at documentation and process, not intentions.

The proposed Security Rule update

In December 2024 HHS proposed the first major revision of the Security Rule in over a decade. Among the changes in the HHS fact sheet: make all implementation specifications required, "require encryption of ePHI at rest and in transit," "require the use of multi-factor authentication," and require written procedures to restore systems within 72 hours. The rule is not final as of this writing, but it describes the direction every practice and every business associate should already be moving in. Multi-factor authentication on assistant accounts, encrypted sessions and no local copies of patient data are already how EyeCareWorks assistants work.

Before Day One

Patient Data Compliance Checklist for a Remote Assistant

Eight items, in the order they should happen. If a vendor cannot walk you through each one, the arrangement is not ready.

  1. BAA signed before any access. Signed by the person who will handle PHI, with incident reporting and permitted uses spelled out.
  2. Training on file. A dated HIPAA Certificate of Completion, and the content it covered, available to you.
  3. Individual credentials. One login per person in your EHR and phone system. No shared accounts, so every action is attributable.
  4. Least privilege. Access scoped to the role. A scheduler does not need the optical sales module or billing history.
  5. Multi-factor authentication on every account the assistant uses.
  6. Encrypted session, no local storage. The assistant works inside your systems over an encrypted connection and never downloads, exports or stores PHI on their workstation.
  7. Audit logs you keep. Activity lands in your own EHR and phone system logs, where you already review it.
  8. Offboarding plan. Credentials deactivated the day a role ends, and the BAA's return or destruction clause followed.

EyeCareWorks walks every practice through this list during onboarding, and the assistant's role, access and BAA are settled before the first shift.

Questions

HIPAA and Virtual Assistants: Frequently Asked Questions

Are virtual medical assistants HIPAA compliant?

They can be, and only when the arrangement is. A remote assistant is HIPAA compliant when they have signed a Business Associate Agreement with the practice, completed documented HIPAA training, work through encrypted access with individual credentials and multi-factor authentication, and hold no PHI outside the practice's systems. A virtual assistant with none of those things is not compliant no matter what the vendor's website says.

Is there such a thing as a HIPAA certified virtual assistant?

Not in the sense of a government credential. HHS states that it "does not endorse or otherwise recognize private organizations' certifications." A certificate shows that HIPAA training was completed on a date, which is useful; it does not make anyone compliant on its own. EyeCareWorks assistants hold a HIPAA Certificate of Completion and we describe them as HIPAA trained.

Does a virtual assistant need a BAA, and who signs it?

Yes. HHS requires a written BAA before a covered entity discloses PHI to a business associate. An EyeCareWorks assistant signs the BAA directly with your practice, because the assistant is the person handling your patient information. EyeCareWorks itself does not receive PHI.

How do virtual receptionist services ensure data security and compliance?

The same four layers apply to phones as to charts: a BAA, trained people, technical safeguards and your own access controls. In practice that means the receptionist works inside your phone system and scheduler with individual credentials, calls are handled and documented in your systems rather than on a personal device, nothing is written down outside the EHR, and the practice keeps the call and access logs.

Can a virtual assistant access my EHR remotely without creating a compliance risk?

Yes, when access is scoped to the role, the session is encrypted, the login is individual with multi-factor authentication, and no data is stored locally. EyeCareWorks assistants work in RevolutionEHR, Eyefinity, Crystal PM, Compulink and other eye care systems under permissions you control, so every action lands in your own audit trail.

Does HIPAA apply to a small or solo optometry practice?

Yes. Any practice that bills or transmits patient information electronically is a covered entity, and HHS describes the Security Rule as scalable to all sizes of regulated entities. The Azul Vision settlement in 2026 involved a single California eye care provider.

What happens if a virtual assistant mishandles patient information?

Under the BAA the assistant must report the incident to the practice promptly, and the practice's own breach procedures apply from there. EyeCareWorks assistants work under a documented incident response process and a zero tolerance sanction policy, and the practice can end the engagement at any time with no notice period.

Does EyeCareWorks sign the BAA or hold my patient data?

No on both. The assistant signs the BAA directly with your practice, and all patient information stays in your systems. EyeCareWorks provides the trained person, the workstation standards and the documentation; it does not receive, store or transmit PHI.

Simple Pricing for Busy Practices

No contracts. No setup fees. Cancel anytime.

Service
Dedicated EyeCare Virtual Assistant™
Rate
$10.00 PER HOUR
Billing
Weekly, for tracked productive hours only
Term
No contracts · Cancel anytime
Replacement
Free anytime, no extra cost
Flexibility
Scale hours up or down as needed
Ongoing support
Included
Setup fees
None
Schedule a Call
The rate above is the whole price. There is nothing else to add.