Overview: What is Credential Filtering (DNPI)?

Summary

This article explains how ProviderTrust credential filtering limits visible credentials by a fixed lookback window, selected credential categories, and chosen states across both Monitor API and PTApp. It clarifies that filtering reduces noise, keeps results consistent, and affects verification and related board actions, while noting current limits such as no separate alert-only views or per-type lookback windows.

Overview

Credential filtering controls which credentials you see and act on in ProviderTrust.

It helps you:

• Focus on recent, relevant credentials

• Limit to the credential types you care about

• Limit to the states that matter to your organization

Filtering is applied consistently in both the Monitor API and PTApp UI, so the same rules govern what data appears and what is verified.

What Credential Filtering Does 

Credential filtering for DynamicNPI (DNPI) controls which credentials are returned and shown to clients in Monitor API and PTApp:

Time-Based Filtering

Your organization can be configured with a fixed lookback window (typically 5 years) for credential expirations. Five years is the standard, but an organization can elect to have a fixed lookback window of 1 or 3 years. Alternatively, the time-based filtering can be set to ALL, which would not suppress credentials based on a lookback window.

• We look backwards from when monitoring starts for your individual or entity.

• Credentials that expired within that window are in scope.

• Credentials that expired before that window are excluded from what you see and from verification.

Example

• A subject is added to monitoring on March 1, 2026 with a 5‑year window.

• Any credential that expired on or after March 1, 2021 is in scope.

• Any credential that expired before March 1, 2021 is out of scope and will not appear in normal user views or verifications.

Important details

• This is a one‑time suppression at go‑live, not a rolling daily filter.

• After go‑live, you receive all future updates going forward.

• If a license that was long expired is truly renewed with a new expiration date, it will come back into scope with that new expiration.

2. Category-Based Filtering: Which Credential Types Are Visible

ProviderTrust admins can configure which categories of credentials are returned for your organization (for example):

• State licenses (STATE_LICENSE)

• DEA / Controlled Substance registrations (CONTROLLED_SUBSTANCE_REGISTRATION)

• Board certifications (BOARD_CERTIFICATION)

How it works

• Only the allowed categories are returned in the API and shown in PTApp.

• If a category is removed from your configuration, credentials in that category stop appearing in results going forward.

Why this matters to you

• You can exclude categories that are not relevant to your organization (e.g., Board Certifications or DEA) so you’re not flooded with noise.

• This does not mean the data doesn’t exist; it means it is intentionally filtered out based on your agreed‑upon configuration.

3. State-Based Filtering: Which States Are Visible

ProviderTrust admins can configure which states’ credentials you want to include.

How it works

• You select a list of allowed states (for example: North Carolina, South Carolina, Georgia).

• When credentials are returned:

  • Licenses in the allowed states are shown.

  • Licenses in other states (for example, Tennessee in this scenario) are not returned.

Why this matters to you

• You can focus only on states where you operate or care about compliance, reducing noise and confusion.

What Credential Filtering Does Not Do (Current Limits)

Based on the current design:

• You cannot ask for “all data, but only alerts on a subset.”

  • The system is built around alerting; providing full raw data while suppressing alerts would require a different model.

• You cannot:

  • Use different lookback windows per alert type (e.g., 1‑year for DEA, 5‑years for everything else) as a standard configuration.

  • Show more data in the Monitor API than appears in PTApp for the same filters.

Filtering rules are designed to be simple, consistent, and aligned to industry standards first, before layering on complex per‑client custom behavior.

Common Client Questions (FAQ)

Is the 5‑year window fixed or customizable?

• Today, it is treated as a fixed window across credential types for your organization.

• The window is set at the client‑configuration level, not per individual license, and not per individual provider.

What happens if a provider leaves monitoring and then comes back?

• The logic is still anchored to the original monitoring start date for that provider under your organization.

• Termed then re‑added providers are treated as if they maintained their original “start” for purposes of the window.

What if we don’t want DEA or Board Certification data at all?

• ProviderTrust can exclude those categories for your organization so they do not appear in standard credential views and alerts.

Are Board Actions tied to licenses?

• Board actions are linked to the underlying license. If a license is filtered out, visibility to its related board action will also be affected.

Does this apply to Instant Search?

• Currently, Instant Search behavior may need additional design work to fully align with credential filtering. If that’s important to you, we’ll take it back to the product team for review.