HIPAA compliant document sharing: what actually counts
We're not lawyers
Nobody at LiveDocument is a legal professional, and nothing in this article is legal advice. Laws vary between countries, states and regions, so have a qualified lawyer who practises where you are review any agreement before you draft, sign or rely on it.
Encrypt the file in transit and at rest, then sign a business associate agreement. Most HIPAA sharing guides stop there. Both steps matter. Neither tells you who opened the document, whether they were entitled to, where the link went next, or what the analytics layer recorded about the reader.
Shared files travel past the inbox you chose. Healthcare documents do the same, and the consequence is sharper when they reach the wrong person. Encryption guards the file on its journey. It says nothing about the twelve hours after a recipient forwards it from a personal account.
Viewer analytics and link lifecycle are PHI risks in their own right. A record of who opened a file, and when, is information about a person. A link anyone can forward is an access decision you no longer control. "HIPAA compliant" only holds when the access rules, the contract, the evidence, the telemetry and the life of the link all stand up together.
What HIPAA requires from a sharing workflow
A vendor badge does not meet the standard. The Security Rule sets administrative, physical and technical safeguards, so you score the workflow as one system: who can reach a document, how the platform is configured, how staff use it, and what the logs can prove afterwards. HHS publishes an overview of the Security Rule, and the 2013 Omnibus Final Rule extended the same duties to business associates. Compliance is ongoing governance. You don't buy it once with an encryption setting and walk away.
In plain terms, the technical safeguards ask this of a shared PDF:
| Safeguard | What it requires | Shared-document check |
|---|---|---|
| Access control | Each recipient limited to the documents and pages they need | Confirm the link can't be opened by someone outside the named audience |
| Unique user identification | Every user has a distinct login | No shared accounts for sending or viewing |
| Emergency access | A documented way to reach records when the system is down | A written break-glass procedure exists and has been tested |
| Audit controls | Records of views, downloads, sharing changes and admin actions | Logs export with user, time, object, action and outcome |
| Integrity | Protection against unauthorised alteration | Links point to the current version and changes are traceable |
| Person or entity authentication | Confirmation that the recipient is who they claim to be | An email link alone is a weak check for sensitive files |
| Transmission security | Encryption in transit and at rest, or a documented equivalent | Uploads, storage and recipient sessions are encrypted |
Encryption is one row of seven, and the easiest to tick. Access control, identity, auditability and authentication fail more often, because they depend on link settings and on what the recipient does next, not on the protocol.
I'd treat the analytics layer as PHI too. A log that names who opened a referral, which pages they read and when they came back is information about a person and their care. So is the lifecycle of the link: who still holds it, whether it was forwarded, and whether that person was allowed to see the file. Switch those features on only when you can protect and account for them the way you protect the PDF.
Run one test this week. Take a document you shared last month that held patient or member information. Can you show who opened it, when, and that they were entitled to? A no is a gap, even with strong encryption. For the wider picture on sending files without widening your exposure, see secure file sharing for business.
Sign a business associate agreement first
A hosted viewer that creates, receives, maintains or transmits ePHI is a business associate, whether or not the vendor can read your files. HHS is explicit that holding no decryption key doesn't take a provider out of scope. Its cloud computing guidance says the use is permitted only when a compliant BAA is in place and both parties follow the HIPAA Rules.
The agreement is what turns a vendor's promise into an obligation. A platform can be well encrypted and still leave you with no route to evidence, no notice when something goes wrong and no deletion on exit.
The clauses worth reading twice
- Role and data: which service the vendor provides, which categories of ePHI it touches, and where processing happens.
- Permitted uses and subcontractors: who else handles the data, and whether each of them is bound by the same terms you signed.
- Security incident duties: identifying and responding to suspected or known incidents, mitigating harm where practicable, documenting what happened and reporting it to you.
- Breach timing: how quickly you hear about an incident, in hours rather than weeks.
- Exit terms: how documents and logs come back to you, and what gets deleted.
Say a referral coordinator wants to upload referral letters to a hosted viewer. Before the first upload, the practice confirms a signed BAA exists, that the vendor's incident duties match the practice's own response process, and that deletion at exit is defined.
Red flag: a vendor who says a BAA isn't necessary because the files are encrypted. Encryption reduces exposure. It doesn't replace contractual accountability.
Test vendor claims against evidence you can ask for
A badge on a pricing page tells you a report exists somewhere. It doesn't tell you what the report covers, whether the sharing product you're buying sits inside the scope, or whether the controls it describes are switched on in production. Treat every claim as the opening of a request.
Encryption of ePHI is an addressable specification under the Security Rule: implement it where reasonable and appropriate to your risk analysis, or document why not and adopt an equivalent measure. That is a written obligation, so ask the vendor for theirs. A ciphertext answer isn't enough when the same product also logs who opened the file, where they were and how long the link stayed live.
| Vendor claim | Evidence to request | Red flag |
|---|---|---|
| HIPAA compliant | Signed BAA covering ePHI and security incidents | Compliance shown only as a badge on the website |
| Encrypted in transit and at rest | Key ownership, rotation schedule and backup encryption details | No clear answer on who controls the keys |
| SOC 2 report | Current report with its scope stated | Scope excludes the sharing product you would use |
| ISO 27001 certified | Certificate number and scope statement | Certificate covers a head office only |
| Audit logs available | Sample export with user, time, object, action and outcome | Logs can't be exported or are kept for a few days only |
| Viewer analytics and link lifecycle | What is logged, who can export it, how long it is kept, and how access ends | Opens and viewer details treated as a side feature with no retention or access rules |
| Instant link revocation | A live test: revoke a link and check access | Revocation requires a support ticket |
Controls a certificate never proves
Encryption doesn't prove the file stays unaltered, remains available during a disruption, or opens only to the people you authorised. Those are separate controls, so keep going after the certificate.
Ask who holds the encryption keys and how often they rotate. Ask what happens to backups when a customer leaves, and whether they're encrypted to the same standard as live storage. Ask what session expiry looks like for a recipient who opened a link on a shared laptop in a waiting room. Then ask the same of the viewing record: if page-level analytics or an open alert can name a person tied to a clinical file, that log needs access limits, a retention period and a deletion path.
Security compliance requirements lays out the controls behind each of those requests in one place.
LiveDocument is HIPAA compliant, GDPR compliant, ISO 27001 certified and SOC 2 (AICPA SOC), and the HIPAA page explains how to request a BAA. I'd still say the same to you as to any vendor: ask for the scope documents, the certificate number and a revocation test before a patient file goes out. Ask me too.
Map analytics before you switch them on
Encryption and a signed agreement settle how a file travels. They settle nothing about what the tracking layer around it records, and that layer is where teams get comfortable with risks they'd never accept in the document itself.
A patient summary can be properly protected and still generate a viewing record that names a family member, their city, their device and the four minutes they spent on page nine. HHS warns that covered entities and business associates may not use online tracking technologies in ways that cause impermissible disclosures, in its online tracking guidance. That guidance is written about websites and apps, but the principle carries over: the viewing record is data about a patient's care, held in a second system, often with weaker access rules than the document it describes.
| Data collected | Example | Can identify a person? | Control to check |
|---|---|---|---|
| Document content | Patient names, clinical text, dates in the file | Yes | Limit what goes into the file |
| Viewer identity | Email address captured by gating | Yes | Turn off gating where it isn't needed |
| Device and network data | IP address, browser, device type | Often | Check retention and who can access it |
| Location data | Country or city derived from IP | Sometimes | Disable it or keep it coarse |
| Referral data | Referring page or email client | Sometimes | Strip query parameters from links |
| Engagement data | Time on page, reopen counts | Yes, when linked to a person | Restrict which roles can see it |
Map the fields before you switch tracking on
- List every telemetry field the tool collects, including the ones on by default and the ones buried in an admin panel.
- Record where each field is stored, in which region, and for how long.
- Confirm which roles inside your organisation can read the viewing data, then cut that list to the people who need it.
- Check whether the viewing record lands in your audit logs, so a disclosure can be reconstructed later.
- Confirm what can be disabled or minimised, and write down the risk decision for anything you leave on.
Say a practice sends a patient summary through a tracked link and page-level timing shows which sections a family member read. A page view shows attention, not intent, but the report is now information about a household. It needs the same access rules, retention limit and audit trail as the document, or it shouldn't exist.
If you can't list every telemetry field the tool collects, don't send PHI through the tracked view yet. This is the one place I'd tell you not to use our own PDF tracking the way you would for a sales deck.
Match the link type to the recipient
Encryption protects the file in transit. It does nothing about a forwarded link, a shared inbox, or a personal email address that outlives someone's employment. Most of the realistic failures here are recipient problems more than protocol problems.
| Link type | Who can open it | Forwarding risk | How revocation works | Best for |
|---|---|---|---|---|
| Public link | Anyone with the URL | High | Replace or unpublish the link | Not suitable for PHI |
| Email-gated link | Anyone who enters an address | Medium | Remove the viewer or the link | Low-sensitivity one-off sharing |
| Named-user access | Only listed accounts | Low | Remove the user account | Ongoing clinical work with known people |
| Organisation identity through SAML | Users authenticated by your identity provider | Lowest | Disable the user in your identity provider | Staff and teams inside the organisation |
Five questions to ask of any link:
- Can it be forwarded? If access is tied to a URL rather than a person, assume it travels.
- Does authentication confirm the intended person? An email address typed into a box confirms almost nothing.
- Can access be revoked? Test it yourself rather than reading the feature page.
- Are downloads controlled? A downloaded copy leaves your audit trail behind.
- Are leavers removed promptly? Former staff, outside counsel and brokers are the accounts nobody remembers.
For PHI leaving your network, named-user access or organisation identity is the default. Email gating suits a low-sensitivity one-off. A public link never carries PHI, however short the engagement.
One honest limit from us. The access control LiveDocument offers is link expiration and revocation, so if your policy needs named-user accounts or SAML on every share, check that against what a tool provides before you commit. See direct link file sharing for how link models trade off.
Take a clinic that emails a link to a former employee's personal inbox because that person still helps with scheduling. The link works, the account is never removed, and three months later nobody can say what was opened. A named-user account with a leaver process would have caught it.
Write the breach clock into the contract
Under the Breach Notification Rule, a business associate that discovers a breach of unsecured PHI must notify the covered entity without unreasonable delay and no later than 60 days after discovery, per HHS's breach notification requirements. Treat 60 days as the legal ceiling. If the vendor's systems can flag an unexpected open on day two, the contract should require notice on day two.
Discovery is the moment the vendor knows, including when an access log shows a viewer who shouldn't have been there. Waiting until the investigation closes before starting the clock is how a covered entity loses the days it needs for its own notices. Name who investigates: the role, the escalation path and the out-of-hours contact. A Friday-night flag on a shared clinical file should produce a named caller and a written first report, not a ticket sitting in a support queue.
That first report lists affected individuals, the documents involved, the dates and the access logs behind the account. Page-level opens, reopen times and download events belong in the packet, because those fields can identify a patient as clearly as the PDF does. Set a fixed update cadence in the contract. A promise to keep you posted isn't a cadence.
Pick one live sharing workflow this week and score it against link type, named audience, telemetry, BAA scope and the breach clause. Write each gap as a task with an owner and a date. Audits fail on unowned intentions. If you're sharing video alongside documents, the same checks apply in HIPAA compliant video sharing.
I built LiveDocument so a document goes out as one tracked link, with page-level analytics and a notification when someone opens it. Run a dummy referral packet through it first, then a file to a colleague, before anything that names a patient.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.