HIPAA and HITECH SFTP server for healthcare file transfers

Run a healthcare SFTP server on your own infrastructure with SFTPPlus MFT. Combine encrypted connections, partner access controls, and audit logs to support HIPAA and HITECH requirements, with no licence limits on users or transfers.

Healthcare files connected to an SFTP server with restricted access and audit records on a dark purple background

SFTPPlus MFT provides an SFTP server for healthcare organizations exchanging files with laboratories, insurers, billing providers, and other authorized partners. It encrypts connections using SSH, restricts which files each account can access, and records file transfer activity. These capabilities support the technical controls in a HIPAA and HITECH file transfer workflow while keeping the server and file storage under your control.

Partners can upload and download files using their existing SFTP clients. If you need to collect files from a partner's server or send them without an operator starting each transfer, see secure automated file transfers for HIPAA and HITECH.

Can SFTP support HIPAA and HITECH compliance? ​

SFTP (SSH File Transfer Protocol) protects files while they travel over a network. HIPAA, the Health Insurance Portability and Accountability Act, covers more than the transfer protocol. The HHS Security Rule summary describes administrative, physical, and technical safeguards for electronic protected health information (ePHI).

HITECH is the Health Information Technology for Economic and Clinical Health Act. It strengthens the HIPAA framework, including making business associates directly responsible for certain HIPAA requirements. The HHS guidance on business associate liability covers obligations such as Security Rule compliance and reporting breaches to the covered entity. For a healthcare file exchange, this makes the controls operated by service providers and subcontractors relevant alongside your own server configuration.

An SFTP server can support these safeguards, but installing software alone does not establish HIPAA or HITECH compliance. Your organization needs a risk assessment, suitable configuration, access reviews, and procedures for operating the complete system. HHS also explains that it does not recognize private Security Rule certifications as a substitute for meeting the requirements.

Protect partner access and record file activity ​

SFTPPlus MFT brings the connection, account, permission, and audit settings into one managed service. For example, a laboratory can upload results into its own incoming folder while a billing provider can download only the exports assigned to it.

ControlSFTPPlus MFT capabilityPractical use
Encrypted connectionsSFTP over SSH with configurable cryptographic algorithmsProtect credentials and file contents in transit.
Account authenticationPassword and SSH public key authenticationGive each partner or automated process its own identity and credentials.
File accessUser and group rules for paths and operationsAllow an account to upload to its assigned folder without reading another partner's files.
Network restrictionsSource IP rules and automatic blocking of repeated failed login attemptsLimit permitted connection sources and respond to repeated authentication failures.
Audit recordsEvents for authentication, file operations, and administrative changesInvestigate who connected, which operation occurred, and whether a transfer succeeded.

Use the SFTP service configuration and authorization reference to configure the service and account permissions. The source IP restrictions and automatic IP blocking guides explain the network controls.

The audit log can be reviewed in the Web Manager or written to files and external monitoring systems through event handlers. Configure the events and retention your organization needs, protect the stored logs, and assign someone to review failures and unexpected access. Use those records in your incident response process, including assessing suspected breaches and handling any required notifications under the HIPAA Breach Notification Rule. The event handler documentation describes event records and available destinations.

Exchange files through AS2, a web browser, or a REST API ​

SFTPPlus MFT also supports AS2 for partner exchanges with message encryption, digital signatures, and delivery receipts (MDNs). It can send and receive AS2 messages with the separate EDI connectors licence.

Staff and partners can upload, download, and manage files through the web file transfer interface without installing an SFTP client. This browser interface runs on the HTTP and HTTPS service. Use HTTPS to protect healthcare file transfers with TLS.

Applications can use the REST API to list folders, upload and download files, and perform other permitted file operations over HTTPS. The web interface and REST API use the same accounts, folder permissions, and audit controls as other file transfer services, so you can manage browser, application, and SFTP access together.

Keep storage and encryption under your control ​

SFTPPlus MFT runs on your own supported Windows or Linux infrastructure, including cloud virtual machines. It is software you operate; ProAtria does not host the transferred files as a SaaS file transfer service. Your team chooses the storage location, network boundaries, backup arrangements, and administrators.

SSH encryption protects the connection, so stored files need their own protection. Configure encryption at rest for the underlying storage and backups, with access to encryption keys restricted appropriately. SFTPPlus MFT also provides OpenPGP file encryption and signing for workflows that require encrypted files outside the SFTP connection. OpenPGP processing must be configured, including how plaintext source files, temporary files, and decrypted output are handled.

For cloud deployments, assess the hosting provider and the services that receive or retain ePHI. HHS cloud guidance explains the need for appropriate business associate agreements, including when a provider stores encrypted ePHI without the decryption key. Running SFTPPlus MFT on a cloud VM does not replace those arrangements.

A cost effective healthcare SFTP server ​

SFTPPlus MFT licensing does not limit the number of users, connections, file sizes, or transfers. This helps keep software licensing predictable when you add healthcare partners or exchange more files. Perpetual licences and annual or multi-year subscriptions are available.

Choose the Server licence role when partners connect to SFTPPlus MFT to upload or download files. Add client orchestration when SFTPPlus MFT must initiate connections to partner servers. The pricing page explains the roles and quote options, including separate clustering and EDI connector licences where needed. Include hosting, storage, backups, network charges, support, and operational work when comparing the total cost of a deployment.

Evaluate a partner exchange ​

Request a supported trial and test with synthetic healthcare files before introducing patient information. Create separate partner accounts, confirm each can access only its assigned files, and check that successful and failed operations appear in the audit log. Test recovery from an interrupted connection and verify the storage and backup controls with your infrastructure team.

Contact our team with your deployment, partner count, authentication requirements, and transfer directions. We can help identify the SFTPPlus MFT features and licence roles for your workflow.