HIPAA compliant file sharing and document delivery
A delivery service for clinical documents where every link, read and expiry can be shown to an auditor.
HIPAA compliant file sharing has to answer one question later: who opened which document, and when. We build the delivery layer between your systems and your partners. A link opens one document for one recipient for a set time, each file is scanned first, and the audit trail records what happened to it.
When to build file delivery yourself
-
Systems exchange the documents
Files move between an EHR and partner systems with no person in between, and an audit is on the calendar.
-
Staff send files now and then
A managed file transfer product under a BAA covers occasional sharing by hand.
What the delivery service includes
-
Scoped download links
Each link carries a token for a single file, a single recipient and a fixed period.
-
Virus scanning gate
Every file is scanned before it leaves, and no download path skips the scan.
-
Retention per partner
How long a file is kept follows each partner contract and is set in configuration.
-
Per-document audit trail
Reads, downloads and expiries are logged for each document.
-
EHR and partner adapters
EHRs and partner systems connect the same way, through adapters.
-
Compliance queries
The compliance team asks the audit data directly, with no CSV export in between.
A file sharing product or a custom delivery service
Managed file transfer products can be used under HIPAA. Files.com, for one, signs a Business Associate Agreement with customers on its Enterprise plan and requires its maximum security configuration. That suits people who exchange files by hand.
| A file sharing product | A custom delivery service | |
|---|---|---|
| Who sends the file | A person, through the product's interface. | Your EHR or a partner system, through an adapter. |
| Scope of a link | As the product's sharing settings allow. | One document, one recipient, one time window. |
| Audit data | The product's own logs and reports. | A dataset your compliance team queries directly. |
| Retention rules | As the product's settings allow. | A rule per partner contract, set in configuration. |
Product facts as each vendor states them: Files.com on HIPAA.
Case study: a file proxy before a HIPAA audit
-
What the audit would have found
Links that were scoped too loosely, download paths that skipped the virus scan and gaps in the trail for documents from outside EHRs.
-
What the proxy enforces
A token per file and recipient, a scan before delivery, retention by contract and a log of each read, download and expiry.
Built with .NET, token auth, audit log. Read the case study: HIPAA audited file proxy
File delivery we have built
-
HIPAA audited file proxyOur file proxy for clinical documents went through an outside HIPAA security audit and passed on the first review. Compliance questions that used to take weeks now take minutes.
-
Clinical document watcherWatcher agents at provider sites send each signed document on with a record that proves where it came from.
How a file delivery project starts
-
Flows and partners
List which systems send documents, who receives them and what each contract says about retention.
-
Rules on paper
We write down the link scope, the scan rules and what the audit data must show.
-
First partner live
One flow goes live end to end, and the other partners are added as adapters.
And much more. Ask about your project
Common questions
Can you trace one file from sender to recipient?
What happens when someone opens an expired link?
How long are files and records kept?
Is HIPAA compliant SFTP not enough?
Which documents leave your systems?
Name the systems that send files, the partners that receive them and the date of the next audit.