FTP (File Transfer Protocol) is one of two input methods to add bulk batches of data to the VendorProof system. You may also opt to upload manually in VendorProof. You can follow the instructions here: Uploading a Vendor File
The Vendor File is the same whether automating the process via FTP or manually uploading the file through the User Interface.
Access the Server
The URL to access the SFTP server is: http://sftp.providertrust.com
Data Mode Folder
Under each home directory (/), there is an integration directory with 9 sub-directories. The names of the sub-directories are pre-defined, and correspond to the combination of the 3 import modes (add, add/update and replace) and 3 import data file types (provider data, credential data and user data). The program will ONLY download the files under these 9 sub-directories and IGNORE all other files stored under other directory names (including the root directory of the organization).
|sub-directory name||import data file type||import mode|
|vendor_add||vendor data||Add mode|
|vendor_update||vendor data||Add/Update mode|
Example SFTP Directory Structures
Assume that account Hospital A has been setup for access, then logging in with this username and its appropriate password will place the user in that account’s home directory:
There are three typical ways of transferring data using FTP: the command line interface found in nearly every system, a transfer agent or library built into an application, or a client application such as FileZilla. The use of the library approach will be highly dependent on the specific agent or library being used. The command interface, shown below, is universal:
For example, if the user ‘user1’ wanted to connect and be placed in the integration/ provider_update directory, the command would be as follows:
The user would be prompted for the password for the account, and then placed in the target remote directory.
The information required for establishing an sftp connection is:
Username and password, as created by the VendorProof administrator
Optionally, the target directory (other than the root of the user’s account) where the user is to be placed on successful logon.
If a client application, such as FileZilla, is used, the information required is consistent but the manner of supplying the data differs.
Uploading Files via FileZilla:
- Once FileZilla is running, click on the left-most icon in the command bar to bring up the Site Manager:
- Fill in the account information. Then click the Advanced tab:
- On this screen, fill in any default remote directory to be placed in on startup. Click the Connect button on the bottom of the window.
- Connection is made and the following main screen is displayed:
- The user can then drag and drop files from the local machine into the target directory on the server.
- After the data is processed, the file will be automatically deleted from the VendorProof server for an added layer of security. A status email is sent informing the original designated user(s) reporting whether the data was processed successfully or not. If the import was not successful, the email will contain an overview of the issues and how to correct them. Additionally, the Integration, Submitted Files user interface provides details about both successfully and unsuccessfully submitted files.
- For unsuccessful files, once corrected, please upload the file again and it will be processed during the next scheduled job.
Article is closed for comments.