Approval gates
Any write to a system of record pauses for a named operator. Nothing material commits unattended.
Every demo shows what the patient asked, what Verigence checked, what changed, and what needed staff review. Demo data is synthetic; production PHI, live connectors, SMS, and writebacks require tenant approval, eligible services, BAAs where required, audit logging, and human-review gates.
Routine workflow steps can be automated, but identity uncertainty, clinical risk, coverage ambiguity, and system writes are gated, disclosed, and recorded.
Any write to a system of record pauses for a named operator. Nothing material commits unattended.
Synthetic demos show AI disclosure and review routing. Production disclosure and consent behavior is configured and validated for each workflow and applicable requirement.
Identity uncertainty, clinical risk, coverage ambiguity, and unavailable connectors create explicit staff-review states instead of a fabricated success.
A finalized supported workflow can produce a signed evidence pack with the recorded conversation, work item, tool timeline, approval or gate events, outcome, and explicit completeness status.
Explicit completeness
Captured events and known gaps stay visible with the work item and outcome metadata.
Tamper-evident when signed
A signed ed25519 pack exposes changes to the recorded payload during verification.
Evidence Trail
EP-2026-0517-40192
e3b0c44298fc1c149afbf4c8996fb924·27ae41e4649b934ca495991b7852b855
Verifiable receipt
Each connector's mode — demo, sandbox, live, degraded, or unavailable — is shown with an icon, a label, and a color. Never color alone.
Fully simulated. No external system is contacted — safe for walkthroughs and training.
reads: mock · writes: mock
Connected to a non-production environment. Real shape, no production data touched.
reads: test · writes: test
Connected to production only after contract and compliance gates pass. Healthcare PHI and writes require BAA/product eligibility plus operator approval.
reads: gated · writes: gated
Partially available — e.g. outbound only, or read-only. The limit is shown explicitly.
partial capability
Not reachable (auth expired, outage). Dependent actions are blocked and surfaced, not retried silently.
blocked
At any moment you can see what the system is doing with data and what's waiting on a human. States are explicit — including the empty, pending, and blocked ones.
Reading
Pulling context from a connector to inform the call. Logged.
Pending review
A write is staged and waiting on operator approval.
Committed when configured
An approved write is recorded only on a supported, configured execution path.
Blocked
Connector unavailable or declined. Surfaced, never retried silently.
We design toward the controls regulated buyers expect — disclosure, human approval, least-privilege connectors, and a complete audit trail. We describe certifications and program status honestly: what is in place today, what is in progress, and what is on the roadmap. We don't imply a certification we don't hold, and we don't position Verigence as a substitute for licensed professional judgment.
Voice demo workspace
Demo onlyUses simulated records and demo-safe tool results; no production systems are contacted.
Evidence pack shape
Live todaySession events, approvals, transcript, and result artifacts follow the production workflow shape.
Healthcare production controls
RoadmapA BAA path is on the roadmap; we do not operate production PHI under a BAA today. Customer-specific data terms are scoped in the pilot agreement.
External certifications
RoadmapSOC 2 and additional formal attestations stay labeled as roadmap until complete.
We'll walk your security and compliance teams through the controls, the evidence format, and the connector model.