Passport has .xlsx formatted reports that can be scheduled on a daily basis to a client's SFTP Reports folder. The following article outlines the fields for the Monitor Export, which can be delivered to the previously mentioned SFTP Reports folder. From there, clients can utilize the export as they see fit, including ingesting the data back into a system of record, such as an HRIS or EHR. An example report is attached at the bottom of this article.
*Note: The export will include all historical and ongoing verifications. This means, that for licenses, as long as the credential is still present within Passport, the last verification will be exported on the Monitor Export. The last credential verification will be included for a license even if the individual is no longer in a license verification package. If the license is deleted from Passport, the license and its last verification will be removed from the Monitor export. All historical license verifications will be available in the License Verification History report.
The file name will follow a pattern of:
“ClientReportName.passport.monitor.ClientSFTPLoginName-yyyyMMdd-hhmmss”
with the current UTC time in 24-hour format, for example, 4:24:03 PM central turns into 21-24-03.
See screenshot below:
| Column Header | Description |
| Organization | Name of Organization |
| Passport ID | Passport generated unique identifier for each monitored individual by ProviderTrust. |
| Facility | Name of Facility in Passport, determined during Implementation |
| Unit Name | Name of Unit in Passport, determined during Implementation |
| First Name | Data field provided by the client |
| Last Name | Data field provided by the client |
| Job Title |
Provider Data provided by the client. For clients using a bi-directional interface, many opt to use Job Title to represent a unique identifier that can be integrated back into an HRIS. |
| Job Code |
Optional data field provided by the client. For clients using a bi-directional interface, many opt to use a Job Code to represent a unique identifier that can be integrated back into an HRIS. |
| Company User ID |
Optional data field provided by the client. For clients using a bi-directional interface, many opt to use a Company User ID to represent a unique identifier that can be integrated back into an HRIS. |
| Company Dept Code |
Optional data field provided by the client. For clients using a bi-directional interface, many opt to use a Company Dept Code to represent a unique identifier that can be integrated back into an HRIS. |
| Company Dept Name |
Optional data field provided by the client. For clients using a bi-directional interface, many opt to use a Company Dept Name to represent a unique identifier that can be integrated back into an HRIS. |
| Severity | Category of alert and type (Examples: License - Expired, Sanction - Abuse) |
| Alert Color | Red, Yellow, or Green is determined by the severity of the information reported. |
| Alert Progress Status |
The status field updated by the client users to determine the resolution of an alert. Dates will be exported in MM/DD/YYYY format |
| Last Updated |
Passport logic around the most recent meaningful event. This can include an end user changing a progress status, to a status change from the board. This is more focused on alerts needing attention, not ANY change (positive or negative) from the primary source. Dates will be exported in MM/DD/YYYY format |
| Overall Monitor Status | Status of the provider’s monitoring. For example “Error” or “Active”. This is a commentary on the provider and their status as a monitored individual in Passport. This is not related to primary source verification. It is expected that everyone would be in an active status. |
| Overall Color Status | This is a rounded color assessment. A provider with one red license, one yellow, and one green, will have an overall color status of Red since that’s the most severe. |
| Overall Progress Status | Similar to overall color status, this is a rounded progress status assessment. A provider with one license in “Needs Review” and three in “Resolved” will have an overall progress status of “Needs Review”. |
| Category | Type of alert by monitoring service (Exclusion, Sanction, NPI, SSDMF, License, OFAC) |
| Date of Last Status Update |
Corresponds with the last date the alert was updated with new information OR when the last note or progress status was updated by the client user, whichever was most recent. Dates will be exported in MM/DD/YYYY format |
| User Updating Status | The user who made the last change to the progress status |
| User Status Note | The last note made by the user on this alert |
| Confidence |
Level of confidence that client-provided data matches the alert information. Options include: Match – This result is a confirmed match. **This interpretation for Sanctions and Exclusions means that we are 100% positive the employee has a sanction or a matched exclusion. For a license - this means we confirmed the license information provided to us matches the individual. Suspected No Match – This record is a highly suspected no match but does not meet our full confidence. **For licenses, this generally means there is a number mismatch from what was the client-provided license number compared to the verified number on the Primary Source. |
| Sanction Verification Method | Piece of data used to match the sanction information to the monitored provider (Examples: address history, license number, personal identifier.) |
| Sanction Source Name | Primary Source Name for Disciplinary Action |
| Sanction First Name | First Name of Disciplined Individual |
| Sanction Middle Name | Middle name of Disciplined Individual |
| Sanction Last Name | Last name of Disciplined Individual |
| Sanction License Number | License Number of Disciplined Individual |
| Sanction Action Type | Type of sanction or disciplinary action. (Examples: Board Action, Administrative Complaint, Board Order, Consent Order, Findings of Fact, Disciplinary Action) |
| Sanction Date of Action |
Date of discipline provided by primary source Dates will be exported in MM/DD/YYYY format |
| Sanction Action Text | Text found on primary source for disciplinary action. |
| Sanction Original Document | Link to the primary source document (if available) |
| Sanction Verification Date | N/A - this field is not currently in use |
| Submitted License Type | Passport standardized License Type. (Example “Registered Nurse”) |
| Submitted Credential Tag | Optional Client-specific License Identifier provided on credential file. |
| Submitted License Identifier | Optional Client-specific License Identifier provided on credential file. |
| Submitted License Issue Date |
IN DEVELOPMENT: Optional Client-specific License Issuer provided on credential file. Dates will be exported in MM/DD/YYYY format |
| Returned License Type | Primary Source language for license type. (Example “RN – Registered Nurse Permanent”) |
| License Issuer Name | Passport standardized issuer. (Example “California”) |
| Client Input License Number |
License Number provided by the client. License numbers can be any alphanumeric string, including special characters such as hyphens. There is a 255-character limit. |
| Verified License Number | Primary Source verified license number. May be slightly varied in format from what the Client sent. (Example Client sent “#440” but the primary source reports “OT440”) |
| Verified Licensee First Name | Primary Source verified first name of licensee |
| Verified Licensee Middle Name | Primary Source verified middle name of licensee |
| Verified Licensee Last Name | Primary Source verified first name of licensee |
| Verified License Expiration Date |
Primary Source verified expiration date. (Example “09/30/2022”) Dates will be exported in MM/DD/YYYY format |
| Verified Compact License Status |
IN DEVELOPMENT: Verified compact nursing status. Statuses will include: Yes - This result is a confirmation that the license is compact No - This result is a confirmation that the license is not compact N/A - This result means the license does not fall within compact rules (i.e. The license type is NOT an RN or LPN--only these types are able to be compact) Blank - No license information provided OR license was not found during verification process |
| License Verified Status | Primary source-verified license status. (Example: Active, suspended, inactive, expired, probation, revocation, etc.) |
| License Verification Date |
Date of primary source verification. (Example: 10/31/2020) Dates will be exported in MM/DD/YYYY format |
| License Screenshot Link | Secured URL for screenshot image of timestamped verification which can be downloaded and saved. The user must be logged in to Passport to view the screenshot. |
| License Mismatch Content | N/A - this field is not currently in use |
| Exclusion Source | Name of Federal or State Exclusion list - A complete list of sources can be found here. |
| Exclusion First Name | First Name of Excluded Individual |
| Exclusion Middle Name | Middle Name of Excluded Individual |
| Exclusion Last Name | Last Name of Excluded Individual |
| Exclusion Suffix | Suffix of Excluded Individual |
| Exclusion Discipline | Discipline of Excluded Individual |
| Exclusion Specialty | Speciality of Excluded Individual |
| Exclusion NPIS | NPI associated with exclusion |
| Exclusion Start Date |
Date Exclusion Begins per the primary source Dates will be exported in MM/DD/YYYY format |
| Exclusion Reinstate Date |
Date exclusion will be reinstated per the primary source Dates will be exported in MM/DD/YYYY format |
| Exclusion Comments | Exclusion Details provided per the primary source |
| SSDMF First Name | First Name of the individual on the SSDMF list |
| SSDMF Last Name | Last Name of the individual on the SSDMF list |
| SSDMF Date of Birth |
Date of Birth of individual on SSDMF list Dates will be exported in MMM DD, YYYY format |
| SSDMF Date of Death |
Date of Death of individual on SSDMF list Dates will be exported in MMM DD, YYYY format |
| OFAC Organization Name | Name of organization/individual on OFAC list |
| OFAC Comments | Comments provided by OFAC list |
| OFAC First Name | First name of individual on OFAC list |
| OFAC Last Name | Last name of individual on OFAC list |
| OFAC Date of Birth | Date of Birth of individual on OFAC list |
| OFAC Country | Country of Residence of individual or organization on OFAC list |
| NPI Number | Verified NPI Number from NPPES |
| NPI First Name | For Active Type 1 NPIs found on NPPES, will display first name associated with NPI. Inactive NPIs will not display a name as it is not provided by NPPES. |
| NPI Last Name |
For Active Type 1 NPIs found on NPPES, will display the last name associated with NPI. Inactive NPIs will not display a name as it is not provided by NPPES. |