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.
HEALTHCARE CREDENTIAL INTELLIGENCE
Credentials change.
Trust needs to
keep up.
Evidence-backed credential intelligence for healthcare. Designed to connect provider identity, verification, and ongoing monitoring through a network on Bittensor.
THE PATH TO A RELIABLE ANSWER
01Start with the source
Licensing boardsProvider recordsExclusion lists
Start with provider identity, credentials, and jurisdiction.
02Do the verification work
MINERS
Match the provider.
Collect the evidence.
VALIDATORS
Test known answers.
Measure reliability.
03Make the answer accountable
Credential statusSource evidenceObservation time
Evidence before confidenceIndependently measured performanceBuilt for changing credentials
01 / WHY VALIDITYA credential check is
A credential check is
a moment in time.
A provider’s credentials need attention at onboarding and throughout their work in healthcare. A record checked yesterday can change tomorrow. Validity’s goal is to connect provider identity, credential evidence, and relevant changes in a form healthcare teams can inspect.
Changing status
Licenses can lapse and exclusions can appear after an initial check. Ongoing monitoring means revisiting source records and surfacing relevant changes.
Answers need evidence
A “clear” result should have support. Validity is designed to keep source references and observation times with each answer, and flag uncertainty for review.
02 / HOW IT WORKSVerification is the work.
Verification is the work.
Evidence is the standard.
Validity brings independent verification operators into one measurable network. The design separates the work customers need from the benchmark used to evaluate miners.
01MINERS
Find the evidence.
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.
The work: identity resolution + source collection
02VALIDATORS
Measure the work.
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.
The benchmark: correct answers before fast answers
03BITTENSOR
Connect performance to incentives.
Bittensor is the blockchain network that coordinates subnet participants. Validity’s scoring design connects benchmark performance to on-chain weights that inform network rewards.
The distinction: network rewards ≠ customer revenue
THE CUSTOMER PATH
A useful answer, without the network complexity.
The customer workflow is designed to 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.
- 01Provider check
- 02Eligible miners
- 03Evidence + review
Only known-answer evaluation tasks determine miner scores. Customer queries do not directly change emission weights.
03 / STARTING WITH RN CREDENTIALSDifferent questions.
Different questions.
The right source for each.
Our first use case is RN verification for travel nursing agencies. These source categories show how identity, licensing, practice privileges, and exclusions fit into a broader healthcare credential workflow.
01
Nursys / nursing boards
RN license evidence
RN license status, expiration, and public discipline through nursing sources. Each state requires clear coverage, source freshness, and authorized access.
02
Practice privileges
Evidence for the assignment state
Distinguish the issuing state, license scope, and evidence of permission to practice in the destination state. Keep unresolved findings visible for review.
03
OIG exclusions
Supporting exclusion screening
Screen for potential matches in the published exclusion list, with source-version context and identity review. Exclusion screening remains separate from RN license verification.
04
NPI / NPPES
Optional identity enrichment
An NPI can help link identity records. RN checks can also use the nurse’s license number, issuing state, and license type; an NPI is optional.
Source freshness sets the pace. Credential changes become visible when the underlying source publishes them.
04 / WHO IT’S FORBuilt around the people
Built around the people
responsible for trust.
For staffing agencies, hospitals, health systems, and insurers: provider identity, credential evidence, and meaningful changes in the workflows teams use to make decisions.
Confidence beyond placement.
Help teams review provider credentials before placement, track changes over time, and retain the source behind each finding.
A clearer view of the roster.
Bring supported credential checks into workforce review, with source context and a visible path for ambiguous or conflicting results.
Evidence across the network.
Help provider-network teams review identity and credential status across their roster, without losing the source behind an answer.
From a one-time check to ongoing monitoring.
A monitoring workflow designed to recheck customer rosters on a source-aware schedule, record observations, and flag meaningful changes for human review.
05 / ROADMAPBuilt in stages.
Built in stages.
Proven before scale.
Our goal is credential intelligence across healthcare. We begin with RNs and travel nursing agencies, then expand across provider types and the organizations that depend on their credentials.
- 01 / CURRENT STEP
RNs prove the loop
Local testing: five fictional RN cases verified, with results preserved across restarts. Next: scoring and rewards, qualified source integrations, and travel nursing agency pilots in California, Texas, Florida, New York, and Illinois.
- 02 / NEXT EXPANSION
NPs and PAs prove the revenue model
After the RN loop is proven, add nurse practitioners and physician assistants. Qualify their sources separately and test paid usage, retention, and sustainable service costs.
- 03 / LONGER TERM
Physicians prove the moat
Expand to physicians after commercial validation. Build lasting value through deeper source coverage, reliable matching, and evidence that stays useful across hospitals, health systems, and provider networks.
A WINDOW INTO THE NETWORK
Open the leaderboard See what measurable verification looks like.
Explore mock miner performance and validator details. Rankings, stake, and identities are illustrative.
06 / A FEW MORE DETAILSGood questions.
Good questions.
Clear answers.
What is Validity, in plain English?
Validity is a credential intelligence network for healthcare, built on Bittensor. It is designed to connect provider identity, credential verification, source evidence, and ongoing monitoring for the organizations that rely on them.
Where is Validity starting?
The first use case is registered nurses at travel nursing agencies in California, Texas, Florida, New York, and Illinois. RN verification is the starting point for a broader healthcare network serving more provider types and organizations.
Why build this on Bittensor?
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.
Are the leaderboard and validator details live?
The explorer uses illustrative records for 12 miners and 4 validators. Identities, stake, blocks, trust, and evaluation results are mock data, not live network measurements.
Does every customer query change a miner’s score?
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.
Will Validity continuously monitor credentials?
The monitoring workflow is designed to revisit customer rosters, preserve source observations, and surface relevant changes. Timing depends on how often each source publishes updates and the access it supports.
TRUST STARTS WITH EVIDENCE.Get to know the network