Secure automated file transfers for HIPAA and HITECH

Automate healthcare file delivery and collection over SFTP or AS2 to support HIPAA and HITECH controls with SFTPPlus MFT. Configure schedules, encryption, retries, audit logs, and failure alerts in one workflow, with no licence limits on transfer counts or file sizes.

A clock connects healthcare files, encrypted transfer, and audit records in an automated workflow on a dark green background

SFTPPlus MFT automates secure file transfers between healthcare systems and partner SFTP or AS2 services. It can monitor folders, collect or deliver files on a schedule, retry temporary failures, and record the result without an operator starting each transfer. SSH encryption, restricted credentials, optional OpenPGP processing, and audit events support the technical controls used in HIPAA and HITECH workflows.

For example, a billing application can export a claims file to a local folder, and SFTPPlus MFT can deliver it to an authorized clearinghouse over SFTP. A separate transfer can collect response files from the clearinghouse and place them in the application's import folder. The healthcare application remains responsible for interpreting the documents and deciding whether a claim or result is accepted.

If partners need to connect to your endpoint, see the HIPAA and HITECH SFTP server guide. SFTPPlus MFT supports both server and client roles, with licensing matched to the workflow.

Automate delivery and collection over SFTP ​

A typical outbound workflow has four steps:

  1. Your healthcare application finishes writing a file to an agreed export folder.
  2. SFTPPlus MFT detects the completed file during the configured transfer window and selects it using folder and filename rules.
  3. SFTPPlus MFT connects to the partner's SFTP server, verifies its SSH host identity, authenticates with the configured credentials, and transfers the file.
  4. After successful delivery, it records the result and can archive or remove the source file according to your configuration.

For inbound transfers, configure the partner's remote SFTP folder as the source and a restricted local import folder as the destination. The partner does not need to initiate an incoming connection to your network.

Administrators manage these workflows through the Web Manager or configuration files. Use the SFTP client location reference for credentials and trusted host identities, and the transfer configuration for source, destination, and processing rules.

Secure HIPAA EDI transactions with AS2 ​

SFTPPlus MFT can also secure HIPAA electronic data interchange (EDI) transactions using AS2. For example, it can collect healthcare claims files from a monitored folder, encrypt and digitally sign the messages, and send them automatically to a clearinghouse over HTTPS. It can also receive AS2 messages, verify signatures, decrypt the files, and make them available to your healthcare application.

SFTPPlus MFT supports signed Message Disposition Notification (MDN) receipts, with synchronous or asynchronous delivery, to confirm AS2 processing and verify message integrity. Your healthcare or EDI application remains responsible for validating transaction contents and processing business acknowledgements. An AS2 MDN does not mean a claim has been accepted.

The SFTP-to-AS2 gateway workflow lets your application keep its existing folder or SFTP handoff while SFTPPlus MFT handles the AS2 exchange with partners.

Schedule transfers and avoid incomplete files ​

Transfers can run continuously or within daily, weekly, or monthly scheduled windows. For example, collect laboratory exports throughout the day and deliver a billing batch during the receiving partner's agreed evening window. Scheduling, file selection, and delivery remain part of the same configuration, reducing the need to maintain separate transfer scripts and scheduling jobs.

Agree how the producing application signals that a file is complete. SFTPPlus MFT supports file stability checks and selection rules, but a pause while an application writes a file is not always proof that the export has finished. An agreed final rename or completion signal can make the handoff explicit. When supported by the destination, transfers can use a temporary filename and rename it after delivery so the receiving application does not read a partial file.

Choose a destination conflict policy for repeated filenames: fail, skip, replace, or preserve both versions with different names. Test that policy with the receiving application so a retry or repeated export does not result in duplicate business processing.

Keep encryption and access controls in the automated workflow ​

Use a dedicated partner account with only the permissions needed for each transfer. Configure a trusted SSH host key or fingerprint for the remote server and protect the private key used by SFTPPlus MFT. Host identity verification helps prevent the automation from sending patient information to an untrusted endpoint.

If the partner requires file encryption or signatures, the built-in OpenPGP handler can encrypt, decrypt, sign, and verify files using configured keys. For an outbound encrypted workflow, transfer only the completed encrypted output. Keep plaintext staging areas, decrypted files, backups, and private keys protected by storage and operating system controls.

SFTP protects data in transit; your deployment must also address stored electronic protected health information (ePHI) and the people and systems that can access it. The HHS Security Rule summary describes the broader safeguards. The Health Information Technology for Economic and Clinical Health (HITECH) Act also makes business associates directly responsible for certain HIPAA obligations, including security and breach reporting. See the HHS business associate guidance when assigning responsibilities across your organization and transfer partners. Automating transfers supports those controls, but does not by itself establish HIPAA or HITECH compliance.

Recover from failures and keep an audit trail ​

SFTPPlus MFT has separate retry settings for connection failures and individual file operations. An unavailable partner endpoint can be retried automatically, while persistent failures can generate email or webhook notifications for an operator. When configured source cleanup depends on successful delivery, a failed transfer leaves the original available for investigation or another attempt. See transfer resilience for retry behavior and recovery options.

A transfer can also define the minimum number of files expected within an interval. If an upstream export stops producing files, SFTPPlus MFT generates an event when the count is below that threshold. This allows your team to detect missing activity as well as explicit delivery failures.

The audit trail records transfer activity and failures. Route relevant events to your monitoring system, and configure archive retention to manage copies kept after delivery. Set retention according to your organization's requirements and protect logs that contain sensitive filenames or other metadata. Operational alerts and audit records can support investigations under your HIPAA and HITECH incident response procedures. Your team must assess suspected breaches and handle any required notifications under the HIPAA Breach Notification Rule. A successful file transfer confirms delivery at the transfer layer; check the receiving application's acknowledgement separately when the workflow requires it.

Control the cost of healthcare transfer automation ​

SFTPPlus MFT includes file monitoring, scheduling, retry handling, and audit events in its client orchestration capabilities. Keeping these operations together can reduce the work of maintaining custom SFTP scripts and separate notification processes. The licence does not limit users, connections, transfer counts, or file sizes, so growing file volumes do not require a larger transfer allowance. Actual capacity depends on your infrastructure and partner systems.

Choose client orchestration when SFTPPlus MFT initiates the connections, whether it uploads or downloads files. Add the Server role if partners also connect to your installation. AS2 requires the separate EDI connectors licence, alongside the Client role for sending or the Server role for receiving. Review licensing and quote options for perpetual or subscription terms, and include infrastructure, support, and any application integration work in your budget.

Test one complete healthcare workflow ​

Request a supported trial using synthetic sample files and one partner endpoint. Check the scheduled delivery, host key verification, file permissions, audit records, and the receiving application's processing result. Then simulate an unavailable endpoint, an incomplete file, and a repeated filename to confirm the retry, alert, and conflict policies.

Contact the SFTPPlus MFT team with your source and destination systems, transfer frequency, and encryption requirements for help configuring the workflow.