Verification Notes for Not Found License Alerts
ProviderTrust has made a big leap forward in our license verification process. We already have industry-leading technology built into our License verification process, like being able to verify licenses up to daily even with variations in license number format, prefixes, spaces, and dashes. But, even with those allowances, we occasionally see a small percentage of licenses that are truly unable to be located on the primary source site.
When we have exhausted all other options and return a license as Not Found, we will now be including Verification Notes directly from our verifiers! These notes are available within the application right above your notes section. Verifiers will leave commentary on what steps they took to locate the license, sometimes including items like using the name in addition to license number or searching for other similar license types. If we find a result for a different license type than what was entered, we will comment on any suggested edits to the original license information to get a clear matched result. Further details on the verification notes can be found here: How to: Review "Not Found" License Alerts
We recommend all clients use this opportunity to go into their Monitor Tab, filter severity results to any License - Not Found results, regardless of their resolution status, and review the newly available Verification Notes. This will enable you to truly resolve the issue at the root, correcting the bad data, so that we can re-verify with confidence. Marking a Not Found license as resolved, but failing to correct the root data issue, means ProviderTrust is not able to give your team a clear verification on the real status of this license.
Reduce Unnecessary File Failures
Along with the new Verification Notes field for Not Found License alerts, we are also making some improvements to file processing. We've heard your feedback about opportunities for the files to not fully fail for a minor data issue on one row, and we are taking some meaningful steps towards re-evaluating what data fields are causing files to fail. Instead of failing a full file, we identified some fields of data that are good candidates to skip when they are invalid. We have shifted the following two validations away from causing a full file failure, and instead, we will skip the bad data and process the file successfully with a minor warning:
- Invalid zip codes - For Provider Files, we accept zip codes in US 5 or 9 digit format, as well as Canadian zip code format. Now, if a zip code is added outside of the accepted formats, instead of failing the entire file, we will skip just the invalid zip, and import the rest of that provider's good data, alongside the rest of the data in the file.
- Credentials for unknown providers - For Credential Files, we accept any licenses, certificates, or documents for providers we already have in the system. In the past, if there was an attempt to add a credential for a provider we do not have in your active population, we would fail the entire credential file. Now, if a license comes across for a provider's SSN/Unique ID that is not in your active population, we'll simply skip that credential, and import all the other valid credentials on the file.
There are several items that ProviderTrust may flag as a minor warning on a successful file, and these two items have been added to our list of minor warnings. We have also updated the successful file email so that anytime there is a minor warning on a successful file, we will include a message in the body of the email.
If you are not sure who is receiving those emails, please contact our support team for information on the distribution list. With these improvements, we are able to skip over minor invalid data and prioritize getting more people and credentials into the system. We want you to spend less time fixing files, and more time focused on keeping patients safe!