TABLE OF CONTENTS
Server
The Patient360 SFTP server information is shown below.
For Firewall Rules if needed - p360sftp.smartbaselink.com resolves to static IP address 216.38.202.75.
Access
Patient360 provisions accounts, as needed, to clients and vendors who wish to use SFTP for measure submission.
If you are having issues accessing the Patient360 SFTP server, please submit a ticket.
Basic Authentication
The SB/P360 SFTP server supports basic authentication (with multi-factor authentication) including username, password, and one of the following:
Verification via Duo mobile application
Verification via phone call
Verification via SMS message
Key-Based Authentication
The SB/P360 SFTP server supports key-based authentication including username, private key file, and a passphrase (optional.)
Folder Structure
Patient360 typically creates a folder for each unique reporting year (this can vary per clinic/TIN.) Within the reporting year folder, a sub-folder is created for each submitter (group practice or individual provider). Files should be delivered to the submitter’s sub-folder.
The folders shown below are automatically created in each submitter’s sub-folder by the SFTP poller.
| Folder Name | Description | File Format |
|---|---|---|
| QRDA-I | ||
| CSV | ||
| CSV | ||
| CSV |
Format and Naming Conventions
Patient360 supports two file formats for quality reporting, QRDA-I and CSV Template. QRDA-I files are .xml files used to convey eCQM data. They are typically packaged into zip file archives. CSV Template files are .csv files used to convey CQM data.
QRDA-I
Patient360 accepts QRDA-I files in compressed .zip format. Files should be named using the following components, separated by underscores:
QRDAI + reporting year Current date as YYYYMMDD Current time as HHMMSS, MeasureID, Provider NPI, or Unique Identifier
For example, a file created for reporting year 2025 on 01/16/2025 at 9am would be named as follows:
QRDAI2025_20250116_090000.zip
Instead of the current time, you could use a measure ID, provider NPI, or a random unique string/UUID to provide a unique filename. Other acceptable file examples would be as follows:
QRDAI2025_20250316_M001_CMS122v13.zip
QRDAI2025_20250520_1234567890.zip
QRDAI2025_20250116_090000_NPI_1234567890.zip
Patient360 recommends a maximum of 5,000 QRDA-I files per .zip file. Be sure the zip files are not encrypted.
Zip File Repackaging
Patient360 offers an optional repackaging of .zip files into .zip files with a maximum of 5,000 QRDA-I files each. To utilize this service, simply deliver .zip files to the subfolder called “split”. The service will automatically process .zip files delivered to this folder. The resulting .zip file(s) created by this service will be automatically moved to the appropriate folder to be imported into Patient360.
If you would like to use the optional repackaging, please contact support at support@patient360.com.
Template/CSV
The SFTP interface accepts comma-delimited .csv files which conform to the template specifications for the given measure. The template specifications for each measure are available in the Learning Center of the Patient360 portal. If you need assistance obtaining template specifications, please contact support at support@patient360.com.
A single .csv file is expected for each measure and can include instances of the measure for all group practices and providers. Template files submitted via SFTP must also include the following 4 additional columns as the 1st 4 columns in the .csv file:
Files should be named using the following components, separated by dashes:
Measure identifier
Current date as YYYYMMDD
Current time as HHMMSS
For example, a file for measure 134 that was created on 01/16/2025 at 9am would be named as follows:
134-20250116-090000.csv
Error Remediation
QRDA-I
For QRDA-I files, Patient360 provides feedback in the Patient360 portal with the status of the zip file(s) along with the import status all the individual QRDA-I files within the zip(s) on a TIN by TIN basis. These details can be found under Imports > QRDA I > History.
Templates
For templates, Patient360 generates an “error.log” file to communicate the reason(s) a file could not be processed. Data submitters should review the error and partially_processed subfolders regularly to ensure that all expected data is successfully processed into Patient360. Any files containing any errors should be corrected and re-uploaded.
Each error.log file indicates the number of encounters that were imported and for each encounter that could not be imported, the row number and reason. Some common reasons and remediation steps are shown below.