Key Takeaways:
- HIPAA compliant file sharing means moving and storing PHI in a way that meets the HIPAA Security Rule.
- No file sharing tool is HIPAA compliant on its own. You need an appropriate Business Associate Agreement (BAA) when the provider is acting as a business associate, plus compliant configurations, policies, and oversight.
- The baseline includes risk analysis, access and audit controls, and BAAs where required. Encryption at rest and in transit is an addressable Security Rule specification; MFA is a strong security practice but not expressly mandated by the current rule.
- External file transfer raises an extra question: once a file reaches a recipient, can you limit further access, record disclosures, and revoke access when the engagement ends?
- For healthcare M&A, start with aggregate or properly de-identified information; share identifiable patient data only when the disclosure is permitted and necessary for a defined purpose.
- There is no official HHS HIPAA certification that makes software automatically compliant.
Table of Contents
ToggleHIPAA compliant file sharing is the transfer and storage of protected health information in a way that meets the administrative, physical, and technical safeguards in the HIPAA Security Rule.
The part most guides bury: no product is HIPAA compliant by itself. Compliance depends on the legal basis for the use or disclosure, an appropriate BAA where applicable, the vendor’s obligations, and the settings and procedures your organization maintains.
That matters most when a corporate development team, investment banker, or private equity buyer needs external access to healthcare records. The question is not simply whether a platform encrypts files, but which information can be disclosed, to whom, for how long, and with what evidence afterward.
This article provides general information, not legal advice. Have privacy counsel and security reviewers assess your transaction and vendor arrangements.
What Does It Mean to Be HIPAA Compliant?
A covered entity can be a healthcare provider, health plan, or healthcare clearinghouse that meets HIPAA’s definition. A business associate performs certain functions or services involving PHI on behalf of a covered entity. A file-sharing provider handling PHI for a covered entity may therefore need a BAA. The agreement allocates required contractual duties; it does not replace either party’s compliance obligations.
There is also no official HIPAA certification.
A buyer is not automatically a business associate merely because it receives information in diligence. Counsel must determine whether the disclosure fits a HIPAA permission, whether a BAA or another agreement is appropriate, and which access restrictions apply.
Core Requirements for HIPAA Compliant File Sharing
HIPAA file sharing requires safeguards proportionate to the risks and an appropriate legal basis for the data use. These four checks should guide a vendor review:
- BAA where required. Covered entities must obtain satisfactory assurances through a compliant BAA from service providers acting as business associates. A BAA is not universally required for every outside recipient or every transfer.
- Encryption in transit and at rest. The present Security Rule treats encryption as addressable, not universally mandatory. Organizations must evaluate it, implement it when reasonable and appropriate, or document a compliant alternative or rationale. AES-256 at rest and modern TLS in transit are sensible procurement standards, not statutory cipher mandates.
- Access controls and authentication. Unique user identification and relevant access controls are required; MFA and short sessions are prudent measures to assess in the risk analysis.
- Audit controls. Maintain mechanisms that record and examine activity in systems containing or using ePHI. For diligence, evaluate whether reports identify user, document, action, and time.
ISO 27001 certification and SOC 2 Type II reporting can provide useful independent assurance, but neither is a HIPAA certification or substitutes for a BAA, security review, and risk assessment.
HIPAA compliant document storage, retention, and paper records
Document storage is broader than encryption. Review backup, disaster recovery, emergency access, access review, secure disposal, and retention policies. HIPAA generally requires security-rule documentation to be retained for six years; it does not impose a universal six-year retention period for every medical record. State medical-record retention laws and transaction holds may require different periods. For paper PHI, physical safeguards should address locked storage, controlled access, and secure destruction. If documents move between paper and electronic systems, record who took custody of each set.
HIPAA Compliant File Transfer: Sending PHI Outside Your Organization
HIPAA compliant file transfer is a governed process for transmitting ePHI to an authorized external recipient. It is not simply emailing an encrypted attachment: teams must verify the recipient, confirm a permitted disclosure, limit information to the minimum necessary where that standard applies, protect transit, and document the transfer.
External transfers occur when a provider sends materials to auditors, insurers, counsel, another provider, or a potential acquisition counterparty. The most useful transfer method depends on whether the recipient is a person reviewing documents or a system ingesting them.
Table 1: HIPAA compliant file transfer methods compared.
| Method | Control after receipt | Auditability | Best fit |
|---|---|---|---|
| Encrypted email | Typically limited once attachment is downloaded | Message-level logs; document views may be unavailable | Small, approved exchanges |
| SFTP / FTPS | Usually limited once transferred | Transfer logs; not always document-level review | Scheduled system-to-system files |
| Managed file transfer (MFT) | Workflow and routing controls vary | Central job and delivery records | Repeatable integrations and batch transfers |
| Secure portal / VDR | Granular view/download access; some offer DRM revocation | User- and document-level activity when supported | Multi-party human review, diligence and audits |
Before an external transfer, confirm whether the recipient is a business associate requiring a BAA, whether any authorization or other conditions apply, and whether the minimum necessary standard applies. Avoid public links; apply time-limited permissions where possible. Record which data went to which parties, who approved disclosure, and when access should end.
For recurring bulk exchanges, SFTP or managed file transfer may be better than a VDR. For bid teams and auditors who must inspect documents, compare secure portals or data rooms on permissioning, revocation, Q&A, and reporting.
Related read: FTP alternative.
Sharing PHI in Healthcare M&A, Audits, and Partnerships
HIPAA can permit certain disclosures of PHI for due diligence connected with the sale, transfer, merger, or consolidation of a covered entity with another covered entity, or an entity that will become a covered entity after the transaction. This is part of the definition of health care operations in 45 CFR 164.501; it is not unrestricted permission to expose patient charts to every bidder. Legal basis, purpose, minimum necessary limits, contracts, and access restrictions still matter.
A practical staged disclosure process is to (1) share aggregated operating data and properly de-identified data first; (2) redact identifying details from samples wherever possible; (3) restrict any necessary identifiable data to an approved group at the appropriate stage; (4) use a clean team or restricted access structure when a competing provider is involved; and (5) preserve a defensible activity and disclosure record. De-identification must meet HIPAA’s Safe Harbor or Expert Determination method; merely deleting names is not enough.
Physician-practice and provider-group acquisitions
For a PE roll-up, early due diligence usually needs revenue concentration, payer mix, staffing, productivity, and quality trends, not patient names. If deeper claims or charts become necessary to test a specific issue, release only approved samples to designated legal, clinical, or compliance reviewers.
Payers, insurers, and claims reviewers
Claims files can include member identifiers, diagnoses, and sensitive service information. Segment claims extracts by purpose, check the recipient’s legal authority, and avoid making a whole member-level dataset available to every finance or deal-team participant.
Life sciences, licensing, and clinical data
Clinical trial and licensing materials may involve HIPAA, research authorizations, contractual restrictions, or other privacy regimes depending on the data source and use. Keep protocol, aggregate outcomes, and operational files apart from identifiable
What Features Should a HIPAA Compliant File Sharing Tool Have?
Evaluate the product against the specific exchange: internal folders, automated data transfer, or external review. A provider’s security brochure cannot prove that every feature is included in your plan.
Table 2: Features to look for in a HIPAA compliant file sharing tool.
| Security | Operational | Collaboration |
|---|---|---|
| Encryption at rest and in transit | Exportable audit trails | Sharing simple enough that staff do not route around it |
| Folder- and group-level permissions | Backup and documented recovery | Access through supported browsers/devices |
| Strong authentication, MFA where supported | Version history and retention controls | Structured questions within a controlled workspace |
| Expiring access and link restrictions | Document preview and redaction where available | Clear reviewer onboarding and NDA process |
| Download controls / DRM where required | Evidence of who viewed and downloaded files | Integrations with approved upload sources |
The collaboration column is the one buyers underweight. A compliant tool that is awkward gets bypassed, and a bypassed tool protects nothing.
Your HIPAA Compliant File Sharing Vendor Checklist
Ten questions to put to a vendor in writing before you sign.
- Will you sign a BAA for the specific service and plan, if one is required?
- Is data encrypted at rest and in transit, and how is key management handled?
- Do you support MFA and single sign-on on our proposed plan?
- Can we assign file- and folder-level permissions to separate external groups?
- What controls continue after download, and can access be revoked?
- Can administrators export view, download, edit, and sharing records?
- How long are logs retained, and can we preserve them for a deal hold?
- Can you provide current ISO 27001 and SOC 2 Type II evidence, if claimed?
- Where is PHI hosted, and which subprocessors are involved?
- What incident notification commitments, escalation contacts, and contractual timelines apply?
Before PHI moves: document your risk analysis and permitted disclosure; complete any necessary BAA and confidentiality documents; restrict link sharing and permissions; verify logging and incident contacts; then train users on the actual approved workflow. Review permissions again after a bidder exits or the engagement closes.
Can You Use Dropbox, Google Drive, or OneDrive for HIPAA?
Yes, these services may support HIPAA-regulated workloads on eligible organizational subscriptions when the vendor offers and executes an appropriate BAA and the customer configures covered services correctly. Personal accounts, unapproved third-party integrations, and unsupported services should not be presumed covered. Vendor terms, product scope, and plan eligibility must be checked before uploading PHI.
Table 3: HIPAA file sharing platforms compared on BAA scope and the question to ask in diligence.
| Platform | BAA status / scope | Primary use | Key diligence question |
|---|---|---|---|
| CapLinked | Enterprise BAA availability represented in supplied CapLinked brief; confirm agreement with sales | External transaction review / VDR | Which features and BAA coverage are on the quoted plan? |
| Google Workspace / Drive | Google offers a HIPAA BAA for defined included functionality | Team collaboration | Is every enabled app and integration in scope? |
| Microsoft 365 / OneDrive | Microsoft HIPAA BAA framework applies to in-scope services under applicable agreement | Microsoft-centric collaboration | Which services, sharing settings, and logs are covered? |
| Dropbox team plans | Dropbox documents BAA workflows for eligible teams | General file collaboration | Is the exact plan eligible, and are integrated apps outside the BAA? |
| Box | Confirm BAA availability and covered subscription directly with Box | Cloud content collaboration | What controls are included in this license? |
| ShareFile | Confirm current BAA and covered service/plan with provider | Client document exchange | Are e-signature and associated integrations covered? |
Is Dropbox HIPAA compliant?
Eligible Dropbox team accounts support BAAs; Dropbox says eligible US-based admins may execute one through the admin console. Its BAA does not automatically cover external apps connected to a Dropbox account. That makes Dropbox viable for properly governed team collaboration, but external due diligence still calls for separate scrutiny of access expiry, downloaded copies, and deal records. Dropbox’s help center describes its current BAA process, and our ShareFile vs Dropbox comparison covers the wider trade-offs.
Are Google Drive and OneDrive HIPAA compliant?
They can support covered workflows within the applicable contract and service scope. Do not rely on one universal instruction such as “turn syncing off”: choose policies based on the organization’s documented risk assessment, the scope of the BAA, and the approved collaboration workflow. Use least-privilege access, secure external-sharing defaults, monitoring, and periodic review.
General cloud drives often suit ongoing internal collaboration. For a healthcare deal involving several independent outside groups, a VDR is worth evaluating when staged disclosure, bidder segregation, Q&A, downloaded-file controls, and a transaction-specific review record are important.
Risks and Common Mistakes of Non-Compliant File Sharing
Improper PHI disclosures can trigger investigation by HHS OCR, corrective action obligations, breach-notification analysis, and civil penalties when violations are established. In M&A, privacy failures can also complicate diligence, representations, warranties, and negotiated indemnities. Penalty amounts depend on the applicable inflation-adjusted schedule, violation tier, and facts; verify the current official HHS schedule rather than publishing unverified figures.
- Emailing patient attachments without assessing the recipient, security, and disclosure basis.
- Using a personal or unsupported account without an appropriate BAA when one is required.
- Copying PHI to unmanaged laptops or phones.
- Leaving shared links or guest access available long after a project ends.
- Failing to review old external users, terminated bidders, and departed staff.
- Skipping or failing to update a documented risk analysis as circumstances change.
- Assuming signing a BAA transfers all HIPAA duties to the provider.
- Uploading unredacted patient-level records to a data room before reviewer access, permission, and minimum-necessary checks are complete.
What Counts as PHI? The 18 HIPAA Identifiers
PHI is individually identifiable health information held or transmitted by a covered entity or business associate in relevant circumstances. Under HIPAA’s Safe Harbor de-identification method, the following 18 categories of identifiers must be removed with respect to the individual and specified related persons, subject to the full regulatory conditions.
Table 4: The 18 HIPAA identifiers under the Safe Harbor method.
| Identifiers (1 to 9) | Identifiers (10 to 18) |
|---|---|
| 1. Names | 10. Account numbers |
| 2. Geographic subdivisions smaller than a state (with limited ZIP exceptions) | 11. Certificate/license numbers |
| 3. Dates directly related to an individual (except year), subject to rules for age over 89 | 12. Vehicle identifiers and serial numbers |
| 4. Telephone numbers | 13. Device identifiers and serial numbers |
| 5. Fax numbers | 14. Web URLs |
| 6. Email addresses | 15. IP addresses |
| 7. Social Security numbers | 16. Biometric identifiers |
| 8. Medical record numbers | 17. Full-face photographs and comparable images |
| 9. Health plan beneficiary numbers | 18. Other unique identifying numbers, characteristics, or codes |
Removing a name while leaving a patient ID, detailed date, or distinctive ZIP code does not necessarily de-identify a record. The two HIPAA methods are Safe Harbor and Expert Determination. Refer to HHS de-identification guidance before relying on either method in a deal room.
How CapLinked Helps Deal Teams Share PHI Securely
A healthcare transaction often requires disclosing sensitive information to people who may never become the buyer. The deal team needs to stage access, limit what each party can see, and preserve a useful record without turning every diligence question into another uncontrolled email thread. A data room supports that workflow; it does not, by itself, establish permission to disclose PHI or guarantee HIPAA compliance.
- Contract and security review. CapLinked’s supplied product brief identifies HIPAA/HITECH/Omnibus support, enterprise BAAs, ISO 27001 and SOC 2 Type II assurance, encryption at rest and in transit, and AWS hosting. Confirm current certifications, the scope of the offered BAA, and available features before PHI upload.
- Stage the data. Set separate permission groups for each buyer, advisor, or reviewer, and assign folder-level view, download, or upload rights. CapLinked documents group workspace expiration; when DRM is enabled, expiration also revokes access to those DRM-protected files.
- Redact before releasing. Use the enterprise PDF editing/redaction workflow when enabled, review what recipients can see, and retain versioned copies rather than overwriting an uncontrolled original.
- Control copies after download. FileProtect offers DRM controls, watermarks, and revocation for protected files. DRM is not a guarantee against screenshots or other manual capture, and permissions must be configured intentionally.
- Keep the process in one place. Use agreements, structured Q&A, and activity reporting to track reviewer access and questions rather than dispersing sensitive exchanges through email. Confirm the report’s actual event coverage and retention before calling it a complete disclosure log.
CapLinked integrations with Google Drive, Dropbox, Box, OneDrive, or Salesforce can serve as upload sources where supported; an integration does not automatically extend another system’s BAA or compliance coverage. Explore the Healthcare & Pharma and Life Sciences pages linked above.
| Next step: Start a 14-day trial to evaluate the reviewer workflow, or request an enterprise quote and BAA before using the workspace for PHI. |
Frequently Asked Questions
What is HIPAA compliant file sharing?
A permitted use or disclosure of PHI supported by appropriate administrative, physical, and technical safeguards, vendor agreements where required, and organizational controls. A platform label alone does not prove compliance.
Is there a HIPAA certification for file sharing tools?
No official HHS HIPAA certification automatically qualifies a software vendor. Review contracts, safeguards, and how the service is configured and used.
Do I need a BAA for secure file sharing?
A BAA is required when the vendor or other recipient qualifies as a business associate. It is not required solely because any two parties exchange PHI; the recipient’s role and the legal basis matter.
Is Google Drive HIPAA compliant?
Covered Google Workspace functionality may support HIPAA-regulated use with the applicable BAA and correct policies. Verify the specific subscription, included functionality, and external sharing configuration.
What are the penalties for HIPAA violations?
Civil monetary penalties vary by enforcement tier and are adjusted for inflation. Verify the current official HHS inflation-adjustment rule, including effective and violation dates, before citing specific amounts.
What causes HIPAA file-sharing failures?
Common risks include misdirected disclosures, excessive access, weak identity controls, unmanaged copies, insufficient logging, and vendor arrangements that do not cover PHI processing.
Can you share PHI with a buyer during M&A due diligence?
Sometimes. HIPAA healthcare operations can include due diligence for qualifying transactions described in 45 CFR 164.501. Apply minimum-necessary and other requirements, and seek legal review before patient-level disclosures.
What makes a virtual data room HIPAA compliant?
No VDR is automatically compliant. Evaluate the vendor’s role and BAA, safeguards, permissions, logs, retention and incident process alongside the organization’s permitted disclosure and workflow.
Is it HIPAA or HIPPA?
HIPAA is correct: Health Insurance Portability and Accountability Act.
What is the most secure way to transfer PHI externally?
The right method depends on the recipient and workflow. MFT or SFTP may fit automated transfers; a secure portal or VDR may better fit governed human review. Controls and legal authorization matter more than the category name.


