Fragmented records
Names, identifiers, and source formats don’t always line up. Reliable verification starts by making sure the records belong to the same provider.
Validity is building a decentralized network to verify healthcare provider credentials against source evidence—and measure how reliably that work is done.
Distinct sources. One provider to resolve.
Find the provider.
Collect the evidence.
Test known answers.
Measure reliability.
A provider’s identity, license, exclusion status, and registrations live in different systems. A record that was checked yesterday can change tomorrow. Validity’s goal is to connect those pieces with evidence you can inspect.
Names, identifiers, and source formats don’t always line up. Reliable verification starts by making sure the records belong to the same provider.
Licenses can lapse and exclusions can appear after an initial check. The planned monitoring service will revisit source records and surface relevant changes.
A “clear” result should have support. Validity is designed to keep source references and observation times with each answer, and flag uncertainty for review.
Validity brings independent verification operators into one measurable network. The design separates the work customers need from the benchmark used to evaluate miners.
Miners are independent operators that build provider lookups and source integrations. They resolve identities, check supported credential records, and return answers with the evidence behind them.
Validators evaluate miners against assignments with known answers. The goal is to reward evidence-backed accuracy, account for failed or missing responses, and measure timeliness separately.
Bittensor is the blockchain network that coordinates subnet participants. Validity’s proposed scoring policy translates benchmark performance into on-chain weights that inform network rewards.
A customer gateway will route a provider check to up to three available, eligible miners, compare evidence, and return a result. Conflicting or insufficient evidence should trigger review, rather than an unsupported “clear” result.
Only known-answer evaluation tasks determine miner scores. Customer queries do not directly change emission weights. The first gateway is planned as a centralized service on top of the decentralized subnet.
Identity, licensure, exclusions, and registrations answer different questions. Validity’s proposed coverage starts with NPI identity and OIG exclusions, then expands as additional integrations are validated.
Link a provider to their National Provider Identifier and resolve identity across records. An NPI match does not establish an active license.
Check for a match against the published exclusion list from the Office of Inspector General, with source-version and observation context.
Verify licensing records through source-specific integrations. Initial license-change testing uses controlled fixtures; live coverage depends on each board integration.
Planned verification of applicable registrations, subject to authorized source access. Checking a number’s format is not registration verification.
Source freshness sets the limit. A change can only be detected after the source makes it available; this website does not claim instant detection or nationwide live coverage.
Healthcare teams need understandable results, not blockchain expertise. The planned product will turn network verification into provider checks, source evidence, and change alerts that fit a review workflow.
The initial customer focus: help credentialing teams revisit provider records after placement, identify changes, and retain the evidence needed for follow-up.
The longer-term goal: bring supported credential checks into workforce review, with source context and a visible path for ambiguous or conflicting results.
The longer-term goal: help provider-network teams review identity and credential status across their roster, without losing the source behind an answer.
The planned monitoring service will recheck customer rosters on a source-aware schedule, record observations, and flag meaningful changes for human review. Customer pilots follow network qualification and validated coverage.
Validity is in development. The website shows the product direction and an interactive mock network. Live chain data, production verification, and customer monitoring are not connected yet.
Define the protocol, source evidence, evaluation policy, and initial NPI / OIG integrations.
Test the full evaluation loop, verify scoring behavior, and expand coverage through source-specific checks.
Pilot the customer gateway and monitoring with staffing agencies before broader rollout.
Explore mock miner performance and validator details. Rankings, stake, and identities are illustrative.
Validity is a proposed network for checking healthcare provider credentials against evidence from supported sources. Independent operators do the lookup work, validators measure their performance on known-answer tests, and a planned customer service turns that work into useful verification results.
Bittensor provides a network for coordinating miners, validators, and performance-based incentives. Validity aims to apply that structure to credential verification: operators compete on the quality of their work, while evaluation results inform network weights. A blockchain record alone does not prove a credential is valid—the evidence still matters.
No. The explorer currently uses deterministic mock records for 12 miners and 4 validators. Identities, stake, blocks, trust, and evaluation results are fictional. The application has a separate data-provider layer for a future chain connection, but it is not connected today.
No. The design scores only evaluation assignments with known answers. Customer queries use the verification network, but their volume and results do not directly enter the emission-scoring calculation. This keeps product usage separate from the benchmark used to reward miners.
That is the planned product direction. A scheduler will revisit customer rosters, preserve source observations, and surface relevant changes. Timing depends on source publication and supported access. Continuous monitoring and live customer alerts have not launched.
Not yet. Source integrations, evaluation, network qualification, and customer pilots still need to be completed. The website explains the intended product; it does not provide live provider verification or replace the review process of a credentialing team.