Back to the finding brief

Invented engagement example. No real provider finding.

UNVERIFIABLE

Is the provider's NPI entry in the buyer directory established by the CMS NPPES registry?

Your directory: 1467459891 · Published source: 1881234567

Supported action: The retained evidence does not establish the provider’s NPI entry in the buyer directory by the CMS NPPES registry — no completed NPPES search record (query, result set, completeness) is delivered for the NPI the buyer card publishes (1467459891; binding not established).

Limit: Whether the provider holds a registry registration — absence of a match is not absence of a registration. Missing subject-binding/search precondition: no search record. Evidence that would permit evaluation: a completed NPPES search record (query, result set, completeness).

Evidence & verification

The readings used

Your directoryThe claimed registry listing reading.

1467459891

Observed Sep 18, 2026 10:00 UTC · excerpt sha256 6ff850d19c98efb33d82b845d31be48fe57887b726f714b9ea686fc79384d708

NPPES registryThe published authority for the registry listing.

1881234567

Observed Sep 22, 2026 09:00 UTC · excerpt sha256 6eee71e12a595756b582648954319c84f5ace5cea0351f736bf75b47829471ba

Comparison preconditions

binding not established — no search record: the registry reading's extract is not a search record (query, result set, completeness); a single record, unrelated, establishes only that binding failed (extractor nppes-json@v2)

Both readings address the same field: the provider’s registry listing.

Subject binding NOT established — the readings must not be combined.

The readings are dated: Sep 18, 2026 (directory) and Sep 22, 2026 (registry).

Rule: REGISTRY-SEARCH-COMPLETE, version 1

Check this finding in your browser

Integrity

Not run.

Issuer recognition

Not checked.

Currentness

Not established.

Not run — invented example; fixture material with no real-world provider finding. The reproduction case package is Ed25519-signed by the fixture key whose computed pin the verifier checks — delivery integrity, never real-world authority.

An intact signature establishes that the signed material has not changed. It does not establish that the authority is right.

Signature checking is local. No checkpoint is included with this evidence.

Technical evidence +

Digests

Claimed excerpt sha256 6ff850d19c98efb33d82b845d31be48fe57887b726f714b9ea686fc79384d708

Authority excerpt sha256 6eee71e12a595756b582648954319c84f5ace5cea0351f736bf75b47829471ba

Canonical recipe

Canonical form: stableStringify — one canonicalisation, no second recipe (published on the Technical page with the downloadable verifier).

Signature

Signed scope: not established

Public key: not established

Dependency manifest sha256: not established

Issuer configuration

Issuer keys: /.well-known/woc-issuer-keys.json

Checkpoint reference: Currentness not established.

Technical evidence — the downloadable verifier, issuer keys, canonicalization and raw views.