Summary
This article explains what exclusion labels mean in ProviderTrust exclusion monitoring and how to interpret the related result labels you may see in the ProviderTrust Application. Exclusion results do not all mean the same thing. Some indicate a possible risk that needs review, while others mean there was not enough information to reach a final conclusion.
Overview
In exclusion monitoring, ProviderTrust reviews available client data and source data to determine whether a monitored subject is connected to an exclusion record. Sometimes the result is not a simple yes or no. Instead of showing one broad label, PT App displays clearer result labels that explain why a final conclusion was not reached and whether the result should be treated like an alert.
Exclusion Result Labels
PT App uses six exclusion monitoring result labels:
- Excluded — a confirmed exclusion result.
- Possible Exclusion — the result may be a true exclusion and needs human review.
- Insufficient Client Data — the subject record did not contain enough usable information to complete verification confidently.
- Insufficient Source Data — the exclusion source did not provide enough information to complete verification confidently.
- Suspected No Match — available research points away from a true match, but a definitive no-match could not be confirmed through unique identifiers.
- Not Excluded — the result was resolved as not excluded.
Result Labels and Alerts
Not every result becomes an alert.
| Result label | Alert? | What to understand |
|---|---|---|
| Excluded | ALERT | Confirmed exclusion outcome requiring review and follow-up per your process. |
| Possible Exclusion | ALERT | Potential exclusion that needs investigation. |
| Insufficient Client Data | ALERT | There was not enough client-provided information to verify the result confidently. |
| Insufficient Source Data | NO ALERT | The source itself did not provide enough information to reach a final determination. Visible in subject/population context, but no alert. |
| Suspected No Match | NO ALERT | The result appears unlikely to be a true match, but not enough unique data was available for a definitive conclusion. |
| Not Excluded | NO ALERT | The subject was determined not to be excluded. |
How to Interpret Exclusion Results That Do Not Trigger Alerts
The labels that do not create alerts include: Insufficient Client Data, Insufficient Source Data, and in some cases Suspected No Match.
- Insufficient Client Data: the subject record may be missing enough detail to support verification. This is generally the most actionable outcome because updating client data may help future monitoring resolve more clearly.
- Insufficient Source Data: ProviderTrust could not confirm the result because the exclusion source did not provide enough detail. In this case, the limitation is with the source information available.
- Suspected No Match: Research suggests the exclusion record is probably not the same person or entity, but a fully definitive no-match could not be proven through unique identifiers.
A simple way to remember it: client data issue means you may be able to improve the subject record; source data issue means the source lacked the needed detail; suspected no match means risk appears low, but not conclusively closed by unique identifiers.
Where These Results May Appear
Depending on your PT App experience, these labels may appear in places such as:
- Subject detail views
- Alert workflows for alert-eligible outcomes
- Dashboard alert counts for alert-eligible outcomes only
- Supported reports and exports
Non-alerting outcomes can still be visible on the subject record even when no alert is created.
Recommended Actions
- Review the exact result label rather than treating all unclear outcomes the same.
- Prioritize alerting outcomes: Excluded, Possible Exclusion, and Insufficient Client Data.
- Improve subject data when possible if the outcome is Insufficient Client Data.
- Document your review according to your internal compliance workflow.
- Use reports and filters to monitor alert-eligible outcomes over time.
Frequently asked questions
Comments
0 comments
Please sign in to leave a comment.