Checklist · 24 items
HIPAA checklist for offshore vendors
What to confirm before an offshore team touches your patients’ data. Each item links to the rule behind it, so your compliance lead can check our reading.
This is a working checklist, not legal advice. Have your privacy officer or counsel confirm what your contracts and state law add.
01Before any patient data is shared
Settle these in writing before the vendor gets a single login.
- A signed business associate agreement
The agreement must set out what the vendor may do with protected health information (PHI), require it to safeguard that data, and require it to report breaches and security incidents to you. It must also bind the vendor’s subcontractors to the same terms and make its records available to HHS. When the contract ends, the vendor has to return or destroy the PHI.
Source: 45 CFR 164.504(e)
- Agreements with every subcontractor that touches PHI
If the vendor uses another company for hosting, payroll systems that hold PHI, or staff, that company needs a business associate agreement with the vendor. Ask for the list.
Source: HHS business associate FAQs
- The vendor’s own security risk analysis
Business associates must do their own accurate and thorough risk analysis. Ask when it was last done and what it found; a vendor that cannot answer has not done one.
Source: 45 CFR 164.308(a)(1)
- Your payer and state contracts allow offshore work
HIPAA doesn’t ban offshore work, but some Medicaid, managed care and Medicare Advantage contracts restrict it. Depending on the contract, you may have to disclose it, get approval first, or keep member data onshore, so read yours before you sign.
- Named security and privacy contacts on the vendor’s side
The Security Rule requires an assigned security official. A Philippine vendor must also have a Data Protection Officer under the Data Privacy Act of 2012.
02Access to your systems
The vendor should work inside your systems, with access you grant and can take back.
- Minimum necessary access, set by role
Each person sees only the PHI their task needs: a billing specialist does not need clinical notes, and an intake coordinator does not need payment history.
- A login in each person’s own name
Never let the team share accounts. Unique user identification is a required Security Rule standard, and without it an audit log can’t tell you who did what.
Source: 45 CFR 164.312(a)(2)(i)
- Multi-factor authentication on every system that holds PHI
It’s the simplest way to make a stolen password useless. Before the team starts, turn it on in your EHR and billing system and everywhere else they will log in, including the clearinghouse and email.
- Automatic logoff on idle sessions
Sessions close after a short idle period so an unattended screen does not stay open on PHI.
Source: 45 CFR 164.312(a)(2)(iii)
- Audit logs that are actually reviewed
Your systems record who opened which record and when. Agree who reviews the logs for the vendor’s users, and how often.
- An access list reviewed on a schedule
A current list of every vendor user and their permissions, reviewed with you at least quarterly and whenever someone changes role.
Source: 45 CFR 164.308(a)(4)
03Devices and the workplace
Most offshore teams work from home or from a shared office, and these controls apply in either setting.
- PHI stays in your systems
Work happens in your EHR, billing system or a virtual desktop. Nothing is downloaded to personal drives or exported to spreadsheets, and PHI never goes into email or chat outside the systems you approve.
- Encryption on devices and connections
Laptops are encrypted and every connection to your systems runs over an encrypted channel.
Source: 45 CFR 164.312(a)(2)(iv) and (e)
- A written workstation policy
Each person works in a private space with the screen out of view of others. Phones stay off the desk so nobody can photograph a screen, and nothing is printed.
Source: 45 CFR 164.310(b) and (c)
- Rules for disposing of and reusing devices
The vendor should have written rules for how a laptop is wiped before it is reissued or retired, and who confirms it.
Source: 45 CFR 164.310(d)
- Managed, patched devices with malware protection
The vendor, not each worker, controls updates and antivirus on every device that reaches your systems.
Source: 45 CFR 164.308(a)(5)(ii)(B)
04People
- HIPAA and security training before access, with records
Every person is trained before their first login and again at least yearly, and the vendor can show you the records.
Source: 45 CFR 164.308(a)(5)
- Background checks before hire
In the Philippines this usually includes an NBI clearance. Ask what the vendor checks and when.
Source: 45 CFR 164.308(a)(3)(ii)(B)
- A sanctions policy that is applied
The vendor should put in writing what happens to someone who breaks the rules, and be able to show you an example of the policy being used.
Source: 45 CFR 164.308(a)(1)(ii)(C)
- Access removed the day someone leaves
Agree who tells you, how fast you disable their logins, and how the vendor recovers the device.
Source: 45 CFR 164.308(a)(3)(ii)(C)
05Incidents and the end of the engagement
- A security incident procedure you have seen
Ask to see how the vendor detects, contains and reports an incident, and who calls whom.
Source: 45 CFR 164.308(a)(6)
- A breach notice deadline shorter than the legal maximum
The rule allows a business associate up to 60 calendar days from discovery to tell you about a breach. Many covered entities write a much shorter window, such as 24 to 72 hours, into the agreement so they can meet their own deadlines.
Source: 45 CFR 164.410
- Backup and continuity plans
Ask what happens to your work during a power cut, typhoon or internet outage. The plan should cover backup power and connections, and name who picks up the work while it lasts.
Source: 45 CFR 164.308(a)(7)
- PHI returned or destroyed at the end, in writing
At the end of the contract the vendor returns or destroys all PHI and confirms it in writing. Keep your HIPAA documentation for six years.
Watch: what a risk analysis has to cover
Item three asks for the vendor’s risk analysis. This webinar from the HHS Office for Civil Rights explains what a real one includes, so you know what to look for.

Common questions
Is it legal under HIPAA to send patient data offshore?
Yes. HIPAA doesn’t prohibit offshore business associates, and the same rules apply as for a vendor down the street: a business associate agreement, safeguards and oversight. Your payer contracts and some state Medicaid programs may add their own limits, so check those too.
Should I ask for a HIPAA certification?
HHS does not certify or endorse any HIPAA certification, so a certificate on its own proves little. Ask instead for the vendor’s risk analysis and training records, along with its written policies. If it has independent audit reports such as SOC 2 or ISO 27001, ask for those too.
Who is responsible if the vendor has a breach?
Both of you can be. Business associates are directly liable for complying with the Security Rule and parts of the Privacy Rule, and you remain responsible for your own obligations, including having a compliant business associate agreement in place and notifying patients when a breach requires it.
How does TrueNext handle this?
We sign a business associate agreement before any PHI is accessible, work inside your systems with logins in each person’s own name, and give you the access list on request. The details are on our compliance page.
Sources
- Business associate contracts: sample provisions (HHS)
- Business associates: frequently asked questions (HHS)
- Summary of the HIPAA Security Rule (HHS)
- Minimum necessary requirement (HHS)
- Breach Notification Rule (HHS)
- HIPAA audit protocol (HHS Office for Civil Rights). What an OCR audit checks, control by control
- 45 CFR Part 164, Subpart C: Security standards (eCFR)
- 45 CFR 164.504(e): Business associate contracts (eCFR)
- Security Risk Assessment Tool (ASTP/ONC)
- Data Privacy Act of 2012 (National Privacy Commission (Philippines))
Leave with a clear scope
A quick discovery call maps the work and what success looks like for you. You leave with a written scope that is yours to keep.