NHID-Clinical v1.3 Specification

The Problem This Addresses

AI voice agents in healthcare payer–provider administrative calls frequently operate without disclosing their automated nature at the outset of a call. Staff share operational data — provider credentials, claim details, eligibility information — before realizing they are talking to a machine.

This creates a window of ambiguity — what this proposal calls impersonation latency — where sensitive information changes hands without informed consent or clear accountability.

The problem is not that AI is making these calls. It is that AI is making these calls while appearing to be human.

The Core Idea

An AI voice agent should identify itself as automated before any operational data is exchanged. That disclosure should be clear, immediate, and not contingent on being challenged.

Everything else in this proposal flows from that single principle.

Suggested Behaviors

The proposal suggests four behaviors for AI voice agents in these workflows. These are not mandatory requirements — they are a starting point for shared expectations.

Sequence of Interaction

The following diagram illustrates the disclosure gate in a standard eligibility workflow.

Why These Four

These behaviors address the specific operational friction that motivated this proposal. They are observable, testable in context, and achievable without significant architectural changes in most systems.

They are also the minimum set that would meaningfully change the impersonation latency problem — not a comprehensive AI governance framework.

Scope

This proposal applies to B2B administrative voice workflows — AI systems calling payer offices on behalf of providers, vendors, or plan administrators. It does not apply to patient-facing calls, clinical decision support, or internal tooling.

What This Is Not

This proposal does not define a compliance program. There is no certifying body, no audit process, and no enforcement mechanism. NHID-Clinical evaluates declared identity, authorization context, and interaction policy; it does not replace an underlying identity provider or cryptographic identity infrastructure. The Implementation Registry is self-attestation only — vendors list themselves and link their own live conformance metrics; NHID-Clinical does not verify or certify entries. The full proposal document (PDF below) contains more detail for interested practitioners.

Known Gaps (v1.3)

v1.3 addresses observable behavior — disclosure timing, deceptive artifacts, escalation path, audit logging. It does not address caller authorization. Because NPIs are public, a malicious AI can trivially impersonate a provider unless a cryptographic authorization handshake is enforced — NHID-Auth v2 (released June 2026, CC BY 4.0) addresses this with Ed25519 provider-signed agent passports and NPI binding. NHID-Clinical v1.3 tells you the caller was automated; NHID-Auth v2 tells you the caller was authorized.