Pick what you need to verify. We'll show the integration path, real effort estimates, and exactly what your team owns versus what we handle.
Most healthcare orgs start with one of these. You can run all four side-by-side once the first is live.
Honest scope: Valyd is identity, verification, and authorization. It is not these things, and we'll tell you upfront.
| Capability | Valyd does this | You'll need elsewhere |
|---|---|---|
| Verify a clinician's identity at login | ✓ Yes | — |
| Check a license is current at point of care | ✓ Yes | — |
| Require human approval before AI acts | ✓ Yes | — |
| Audit who did what, when, with proof | ✓ Yes | — |
| Patient EHR storage | No | Your EHR vendor |
| Clinical decision support logic | No | Your CDS layer |
| HIPAA-compliant infrastructure hosting | No | Your cloud (we run inside it via API) |
| HR / credentialing source-of-truth | No | We verify against it, don't replace it |
All four paths share the same five-step shape. Once you've done one, the rest are variations on the same flow.
Realistic effort, not marketing math. Numbers assume one familiar dev, no surprises.
| Path | First integration | Per workflow after | Security review |
|---|---|---|---|
| SSO sign-in | ~30 min | ~10 min | Standard OAuth review |
| OIDC enterprise | ~1 hour | Config-only | Existing SSO review |
| MCP approval | ~2 hours | Add tool to agent | Webhook + agent policy |
| Step-up verify | ~3 hours | ~1 hour per action | Action-binding review |
30-minute architecture call. We'll map your integration in a shared doc you keep.