What this pilot is
A 30-day focused employer pilot. We measure startability timeline events against your current workflow on 10–30 real clinician NPIs and hand you a signed scope document before any measurement starts.
Employer pilot
Cut credentialing uncertainty before the start date slips.
VitalCV turns four source-backed lanes of clinician evidence into a deterministic proof pack and an auditable trust container, so your reviewers can see what is ready, what is missing, and what must wait for primary source verification — without changing your existing compliance stack.
Avg time to first signal
1.8 min
Internal simulation · not a customer pilot result
Automated source lanes
4
NPPES · OIG LEIE · PECOS public · state-board adapter
Proof-pack export formats
JSON · ZIP · PDF
Manifest references in every export
Audit record per export
ARTIFACT_EXPORTED
Records an audit event before the bundle returns
What you provide
A roster of 10–30 clinician NPIs, a named review operator, and your current baseline numbers (time-to-start days, applications per month) — or an honest "we don’t track this yet" so we can capture it from scratch.
What VitalCV measures
Submit → first view → first action → advanced → start-ready → started timeline deltas, refresh and missing-info request counts with owner attribution, and proof-tier distribution at submit time.
What success looks like
You see documented source coverage, packet status, and limitation notes per clinician before the formal committee process. We do not replace your credentialing committee — we shorten the days-at-risk window before committee review.
The proof pack
Every clinician review generates a deterministic evidence packet with canonical source coverage, per-lane freshness, and a sha256 artifact hash. When your reviewer exports the packet, VitalCV writes an ARTIFACT_EXPORTED audit event before the bytes leave the platform.
What is live now
- NPPES, OIG LEIE, and PECOS public checks with canonical source coverage
- Proof-pack exports (JSON and ZIP) with deterministic artifact hashing
- ARTIFACT_EXPORTED audit event every time a packet leaves the platform
- Partial-proof limitation notes preserved verbatim through every export
What remains partial or pending
- Configured state-board PSV adapters for launch-state authority checks
- Additional payer and organization source adapters after source agreements
- Production credential-container issuance after provider configuration
- Continuous monitoring outside the configured pilot lanes
The trust container
The trust container is a hidden backend record that binds the credential envelope id, artifact status, and issuer metadata to the proof pack. It is provider-pluggable — a deterministic mock today and a production-provider scaffold ready for future wiring.
- Records the evidence packet’s credential envelope and artifact status.
- Does not replace primary source verification.
- Does not upgrade partial evidence to decision-grade.
- Mock/dev containers are not production credentials.
- Limitations shown in the packet remain controlling.
Limitation honesty
- NPPES identity checks confirm NPI registration only; they do not replace licensure proof.
- OIG LEIE covers federal exclusion scope only; state Medicaid exclusion lists are out of scope until they are adapter-connected.
- PECOS public data reflects the public release, not the real-time enrollment portal.
- State board coverage depends on institutional access agreements; uninstrumented states remain an adapter gap, not a verified claim.
- The trust container records packet metadata and artifact status; it does not replace Primary Source Verification (PSV).
- A partial proof stays partial. Container issuance never upgrades partial evidence to decision-grade.
The next step
Request a 30-day PSV readiness pilot
We review every submission within two business days. If the scope is a fit, we schedule a scoping call to confirm your baseline metrics, the pilot NPIs, and the measurement window.
No auto-provisioning. You will see a signed scope document before anything is measured.