Summary:
This article explains how organizations can securely submit their NPI population for Dynamic NPI monitoring using flat file transfer. Clients receive unique SFTP credentials and access to designated upload and download folders. The guide outlines required file naming conventions, monthly processing timelines, and what to expect in the returned output files. It also covers error handling, including validation checks and missing license information. This resource is intended for technical users responsible for securely setting up and managing flat file transfers to ProviderTrust.
If your organization would prefer to submit your NPI population as a flat file for monitoring, this guide outlines how to send your file securely to ProviderTrust and receive your Dynamic NPI profile files in return.
Setup
During implementation, your organization will be provided with unique credentials to a dedicated SFTP folder on:
SFTP Server: sftp.providertrust.com
Clients receiving Dynamic NPI flat files will have the following folder structure set up in their root SFTP folder:
Folder Path:/Dynamic_NPI_flat_files/
├── DNPI_upload/ → For uploading your input files
├── DNPI_download/ → For retrieving processed output files from our system
File Naming Conventions:
Please follow these naming conventions to ensure your files are processed correctly:
Input File (uploaded by client)
npi_list_[client_name]_[YYYY-MM-DD].csv
[client_name]Client name, use underscores instead of spaces[YYYY-MM-DD]Date of the file upload
Output Files (returned by ProviderTrust)
dnpi_npi_[client_name]_[YYYY-MM-DD].csv→ NPI table output
[client_name]Client name, use underscores instead of spaces[YYYY-MM-DD]Date of the file generation
dnpi_license_[client_name]_[YYYY-MM-DD].csv→ License table output
[client_name]Client name, use underscores instead of spaces[YYYY-MM-DD]Date of the file generation
dnpi_license_[client_name]_[YYYY-MM-DD]_npi_missing_license_creds.csv→ License table output for NPIs missing license credentials
[client_name]Client name, using underscores instead of spaces[YYYY-MM-DD]Date of the file generation
dnpi_exclusion_[client_name]_[YYYY-MM-DD].csv→Exclusion table output
[client_name]Client name, using underscores instead of spaces[YYYY-MM-DD]Date of the file generation
Processing the Data Timeline
Step |
Action |
Responsible Party |
|---|---|---|
1 |
Client uploads the input data file to |
Your organization |
2 |
Upload must occur before the agreed processing date each month.
Note: This lead time allows ProviderTrust to collect the necessary license and credential data for new NPIs before monitoring begins. |
Your organization |
3 |
On the agreed processing date, a scheduled job will run and process the most recently uploaded file..
Example: If your organization uploaded a file on June 1 and did not upload anything before the July processing date, the July job will run using the June 1 file. |
ProviderTrust |
4 |
Processed output files are placed in |
ProviderTrust |
5 |
Download the output files for your records. |
Your organization |
Error Handling
Scenario |
Result |
|---|---|
Empty Input File Folder |
No data will be returned on the scheduled job date |
Invalid File Format |
An error file is generated: |
The file is missing credentials for some NPIs |
ProviderTrust will create an output file of NPIs with no credential data returned. Note: This output file will be |
Upload Template Samples
Data Dictionary:
Upload file Sample:
Output Files returned from ProviderTrust
NPI Data Dictionary:
DNPI NPI Sample File:
License Data Dictionary:
DNPI License Sample File:
No License Credential File:
Exclusion Data Dictionary:
Exclusion Sample format:
Comments
0 comments
Please sign in to leave a comment.