Sending automated files via SFTP

Relevant can transmit files on an ongoing, automated basis to any destination that supports SFTP. Health centers often use this feature to transmit data to 340B administrators and other third parties.

Note: This is an add-on feature. If it’s not already enabled, contact Relevant to learn more about the setup steps and associated fees.

How it works

The content of the outbound data file is defined using a Report Builder report. This means you can view the report in Relevant at any time to check its logic and confirm that it’s producing the expected results.

Checking transmission status

To check the status of the most recent file transmission, navigate to the report in Report Builder. You’ll see a notice indicating the last transmission date, time, and status.

To see a complete list of file transmissions, go to Configure > Outbound Job History.

Note: file transmission history is available in Relevant for transmissions made on or after June 17, 2025. If you need to confirm the status of an earlier file transmission, contact Relevant support.

Adjusting the transmission cadence

Files can be transmitted on any regular schedule: for example, every day at 3 AM, or the last day of each month at 12:01 AM. To adjust the cadence of the automated transmission, contact Relevant’s support team and we’ll be happy to adjust this for you. ( Note: it is not currently possible for health centers to view or modify the transmission schedule within Relevant.)

What’s supported

Relevant’s file transmission supports:

  • Generating files in CSV or PSV (pipe-separated) formats
  • Encrypting files with PGP/GPG, if required by the receiving entity

It does not support:

  • File formats other than CSV or PSV
  • Specifically, HL7 or FHIR files are not supported

Relevant only supports “outbound” SFTP; in other words, Relevant pushes a file from our server onto the receiving entity’s server. This means that the receiving entity must provide an SFTP service that can accept files from external sources.

Relevant does not host an SFTP server; allowing external parties to SFTP into Relevant’s server to “pull” a file is not supported.

Getting started

When discussing a file transmission project, Relevant will typically request a file spec that describes the required fields, format, and logic. Here’s an example file spec. If the receiving entity does not have a formal file spec, something simpler that describes the format (e.g. “CSV”) and the required fields may be sufficient.