Is outsourcing home health work HIPAA-safe?
Handing home health admin work to an outside team is not HIPAA-safe by default. It can be, once the BAA and unique logins are in place. Not legal advice.

Say it’s Friday afternoon at a home health agency. The owner’s screen still shows a list of unworked EVV exceptions, though it could just as easily be claims waiting to be posted. In another tab is a vendor’s email saying its team is HIPAA-certified. The owner is already picturing a remote assistant in the Philippines taking that work off the office’s hands.
The short answer: outsourcing home health work is not HIPAA-safe by default. It can be, once the specific work you want to hand off is set up properly before anyone outside the agency logs into protected health information (PHI).
A covered entity may disclose PHI to a business associate if it obtains satisfactory assurances in a written business associate agreement, HHS says. OCR is blunter about cloud vendors: If a covered entity uses a cloud service to maintain (process or store) electronic PHI without a BAA, the covered entity is in violation of the HIPAA Rules. And HHS and OCR do not certify any persons or products as “HIPAA compliant.” So the vendor’s email can say “certified” all it likes; what decides the answer is how the work is set up on your side.
This article is not legal advice. As the covered entity, the agency owner stays responsible, and your counsel should review the contract. And if you came here about Veterans Affairs home care benefits, this isn’t that: “VA” here means virtual assistant.
Which work are you handing off, and does it involve PHI?
Start with one specific task you want off your desk this week, such as clearing EVV exceptions or posting payments. “A virtual assistant” is not a task. It’s one way of buying help, and that person might end up doing any number of jobs. If you can’t say which task you’re handing off, you don’t have work to hand over yet.
Home health PHI is more than the clinical chart. Schedules, intake notes, EVV exceptions, and claims or posting files can already be PHI when they identify a person and relate to care or payment. HHS lists claims processing, billing, and practice management among the activities a business associate performs on behalf of a covered entity, and scheduling and billing tools can be business associates too when they access PHI.
Recruiting admin is different. It only raises these questions when it creates, receives, maintains, or transmits PHI, because Protected health information excludes individually identifiable health information in employment records held by a covered entity in its role as employer.
The work usually already lives in a system of record such as WellSky, HHAeXchange, or Homecare HomeBase, and that’s where the outside team should do it. Some home health vendors advertise this kind of work done under named logins, but that is vendor marketing, not an HHS standard.
If the work is claims and posting, the AR numbers are covered in what a healthy revenue cycle looks like in 2026. One homecare billing article sums up the principle in a sentence: outsourcing is delegation, not abdication.
Once the setup passes the checks below, the person doing the work can complete that task in your existing system, using the inputs you’ve approved for it. These decisions should still come back to the agency:
- clinical exceptions
- hiring decisions
- payer relationships
- calls with families that the owner wants to keep in-house
You’ll know the handoff worked when:
- the person has their own unique login for this work
- a BAA was dated before that login if they’re a business associate, or direct control is documented if they’re workforce
- no PHI has moved into WhatsApp, a shared inbox, or personal email
- the owner is still the one who attests
Why the answer is no until a BAA is signed
Knowing the task and having a vendor’s email isn’t enough to start. The default is no because a business associate’s access to PHI without the written agreement is already a HIPAA Rules violation. It isn’t because HIPAA forbids outsourcing by geography; location comes later.
45 CFR 164.502 says a covered entity may disclose PHI to a business associate, and may allow it to create, receive, maintain, or transmit PHI on the covered entity’s behalf, if it obtains satisfactory assurances that the business associate will safeguard the information. Those assurances have to be documented in a written contract that meets 45 CFR 164.504(e), and that contract has to establish the permitted and required uses and disclosures of PHI by the business associate.
OCR’s cloud vendor FAQ is about cloud services, and a person who processes PHI for you is not a cloud vendor, so treat it as a close analogy. The Rules OCR cites there are 45 CFR 164.308(b) and 164.502(e), and forwarding the EVV login to a business associate before the written agreement exists fails those same Rules.
Vendor pages put it both ways. One clinic-outsourcing FAQ says “Outsourcing is not HIPAA compliant by default,” while a call-center page says HIPAA doesn’t prohibit outsourcing, it sets standards for vendors. The second one still doesn’t make an unprepared handoff acceptable.
Here’s how it usually goes wrong. The owner replies “start Monday” to the vendor’s HIPAA-certified email, then forwards the EVV login or pastes the shared office password, with no signed BAA and no login of the remote assistant’s own. That handoff is a no. The fix has to happen before anyone else becomes a user, using the seven questions below.
Seven questions to settle before anyone else logs in
Answer each of these for the specific work you’re handing off, before a second person logs into PHI. Fill in every row.
| Question | Fails | Passes |
|---|---|---|
| Who is the covered entity for this work? | Left blank, or the vendor’s certified email is treated as if the vendor attests. | The agency, and the owner attests. |
| Is the person doing the work a business associate or part of your workforce? | “A VA” or “the company,” with no classification, or treated as a postal-service conduit while working in the EHR. | Classified as a business associate or as workforce under the agency’s direct control. If neither, no PHI. |
| Is a 164.504(e) BAA signed before the PHI login? | The login, a forwarded invite, or a WhatsApp thread comes first, or a training certificate or self-certification stands in for the contract. | A written contract meeting 45 CFR 164.504(e), dated before access, or documented workforce control if the person really is workforce. |
| Whose login is it? | A shared front-desk password, or a shared WellSky, HHAeXchange, or Homecare HomeBase login. | A unique name and/or number for identifying and tracking user identity, issued for this work. |
| What PHI does this work need? | The entire chart, or “they’ll see what they need once they’re in.” | Only what this task needs, limited by the BAA or by your own minimum-necessary policies. |
| Where does the PHI live? | A client address in WhatsApp to clear an EVV exception, a shared inbox, personal email, or “we’re just a conduit.” | The person’s unique login on the agency’s EHR, EVV, or billing platform. |
| Who attests if something goes wrong? | The vendor’s certificate, or business associate liability, is assumed to move attestation off the agency. | The owner, as the covered entity. |
The pass column follows HHS and OCR guidance and the HIPAA rules cited below, not vendor marketing. Each row is explained in its own section. Not legal advice.
The covered entity is your agency
HIPAA’s Privacy, Security, and Breach Notification Rules apply to health plans, health care clearinghouses, and health care providers who transmit health information in electronic form in connection with a covered transaction. For a home health agency that does this, the covered entity is the agency handing over the work. Since HITECH and the 2013 rule, business associates are directly liable for certain HIPAA requirements, but that doesn’t move the owner’s attestation off the agency.
The person doing the work must be a business associate or workforce
45 CFR 160.103 treats as a business associate a person, other than workforce, who creates, receives, maintains, or transmits PHI on behalf of the covered entity for a regulated function, including claims processing or administration, billing, and practice management. Workforce means employees, volunteers, trainees, and other persons whose conduct, in the performance of work for a covered entity or business associate, is under the direct control of that entity, whether or not they are paid.
A remote worker in your EHR is not the postal service. HHS limits the conduit exception to transmission-only services, including temporary storage incident to transmission, and entities that access PHI on a regular or frequent basis to perform a service are not conduits. A vendor that only sells software without PHI access isn’t a business associate, but hosting or troubleshooting that accesses PHI does make it one, and the BAA has to exist before that access. If the remote party is neither a business associate nor workforce, stop.
The BAA is signed before any PHI is shared
Disclose PHI to a business associate only after a written contract meeting 164.504(e) is in place. A business associate cannot substitute self-certification or third-party certification for that contract. HHS publishes sample BAA provisions, but that language is sample only. It isn’t required, and it doesn’t replace counsel or a binding state-law contract.
Every login is unique
45 CFR 164.312 makes unique user identification a required technical safeguard: assign a unique name and/or number for identifying and tracking user identity. A shared front-desk password fails that requirement, and so does one login shared between several people in your EHR. Vendors that advertise named, auditable logins are describing what passing this row looks like, though that is their marketing, not HHS guidance.
Access is limited to what the task needs
Covered entities and business associates must make reasonable efforts to limit PHI to the minimum necessary to accomplish the intended purpose of the use, disclosure, or request. The BAA must limit the business associate’s uses, disclosures, and requests so they stay consistent with the covered entity’s minimum-necessary policies. If the person is workforce, those same policies apply directly. Someone clearing EVV exceptions needs the PHI that task uses, not the whole chart “once they’re in.”
PHI stays in your systems
The work should happen through the person’s unique login on your EHR, EVV, or billing platform. The conduit exception doesn’t cover anything that stores or processes PHI over time, so a client address dropped into WhatsApp to clear an EVV exception, a shared inbox, or a personal email thread is storage. Calling that thread a conduit doesn’t make it one.
The owner still attests
HHS lists direct business-associate liability for, among other items:
- failure to comply with the Security Rule
- impermissible uses and disclosures
- failure to limit PHI to the minimum necessary
- failure to enter into BAAs with subcontractors that create or receive PHI
- failure to provide breach notification to the covered entity
None of that erases the agency’s duties. If something goes wrong, the owner still attests.
Done properly, the agency hands over the same EVV exception work, but under a BAA that meets 164.504(e) and is signed before access starts. The person doing it has their own login, limited to EVV exceptions, PHI never leaves that login, and the owner is still named as the person who attests.
Who is responsible: the agency, the vendor, or the person doing the work?
A vendor email saying HIPAA-certified doesn’t answer any row of the table, because HHS and OCR do not certify any persons or products as “HIPAA compliant.” When the person doing the work is a business associate, the agency still has to enter into a contract or other written arrangement that meets 45 CFR 164.504(e), and that BAA is what establishes who is responsible. Internal training can be useful, but it isn’t what permits PHI access.
Who the business associate is depends on how you buy the help:
- A marketplace freelancer who would create, receive, maintain, or transmit PHI may be the business associate, so 164.504(e) still has to be met with that person.
- A company may sign as the business associate, with the person doing the work as its workforce or as a subcontractor. A business associate must establish a BAA with its subcontractor before disclosing PHI to that subcontractor.
- Your own workforce: a person may be treated as the agency’s workforce when their conduct is under the agency’s direct control, paid or not. That is a control test, not a label, and not an IRS 1099 versus W-2 question.
HHS says a covered entity may choose to treat an on-site contractor employee as workforce when that person’s primary duty station is on-site. That option doesn’t turn a remote vendor’s worker into workforce just because you’d prefer it. A remote person whose conduct is actually under your direct control can still be workforce; a remote vendor who isn’t under that control is a business associate, or neither, in which case stop.
Whichever arrangement you choose, the person still needs a unique login, is still not a conduit while working in your EHR, and the owner still attests.
A home care virtual assistant is one of these arrangements (freelancer or company, depending on who employs the person), not a separate HIPAA category. One compliance page states the trigger in plain terms: a virtual assistant is a business associate when it creates, receives, maintains, or transmits PHI, including scheduling, intake, and billing. Some product pages go further. One sells a “HIPAA Compliant Virtual Assistant” and certifies the person upon completion of internal training. If the BAA-before-PHI row is still blank and the office password is still shared, that certificate changes nothing, so stop there.
For the full set of controls to confirm before an offshore team touches PHI, from the BAA through to offboarding, use our HIPAA checklist for offshore vendors. Each item links to the rule behind it.
Can the work be done from the Philippines?
OCR answers a close question about cloud vendors that store electronic PHI on servers outside the United States: yes, provided the covered entity or business associate enters into a BAA and otherwise complies with the applicable HIPAA Rules. The HIPAA Rules do not include requirements specific to protection of electronic PHI processed or stored by a cloud vendor or any other business associate outside of the United States. Overseas storage or other services for electronic PHI may increase risks and present special considerations with respect to enforceability, and OCR tells covered entities and business associates to account for those risks in their Security Rule risk analysis and risk management, citing 45 CFR 164.308(a)(1)(ii)(A) and (B).
So HIPAA doesn’t decide this by location. Onshore and offshore work have to pass the same seven questions, and offshore work adds one more entry to your Security Rule risk analysis: location and enforceability. A Philippines address on a vendor page is not an OCR certification, and the map doesn’t issue the login.
Other documents can still say no. Some law-firm writing treats state law and payer contracts as a separate stop even where HIPAA does not prohibit offshore access. We haven’t reviewed those statutes as primary sources, so we don’t name them as verified law here. Medicare Advantage and Part D offshore guidance, where it exists, is a different federal regime from HIPAA. Have counsel read contract, state, and payer clauses as their own layer.
If the seven questions don’t all pass yet, don’t issue the login. If they do, what remains is agreeing exactly what the team will do and in which systems. Counsel reviews the contract, and the owner still attests.
Where we process PHI under applicable health privacy laws (such as HIPAA in foreign jurisdictions), we act in our capacity as a Business Associate governed by a signed Business Associate Agreement (BAA). TrueNext Global operates from the Philippines and serves clients and users globally. What we can discuss with you is a specific administrative task on your agency’s existing software, after that BAA is signed. We do not claim a published home-care case or OCR certification.


