Security & governance

What holds

Six answers, each one a mechanism.

None of these is a policy statement. Each is something in the system that can be inspected at a pilot, and should be. Each card says what it is, and what your team would look at.

Database

The record cannot be rewritten

Every recommendation and every decision on it is appended to a log whose entries commit to the one before, so an alteration anywhere breaks the chain from that point and stays visible.

What your team inspects

The log carries each entry's own digest and the digest of its predecessor. A database trigger rejects updates and deletes on it, including ours. Ask to see the trigger, then ask an engineer to try an update in front of you.

Application

Turning it off is a first-class feature

Kill switches at facility level and at individual clinician level. One click turns V3ra off for a clinician without touching a colleague, reversible at any time, needing no approval from us.

What your team inspects

Both switches are state your side holds, not a request queue on ours, and each is read on every request. Ask for the admin console and turn yourself off while a colleague keeps working.

Contractual

A BAA before a single chart moves

V3ra operates as a business associate under HIPAA. That applies to an evaluation sample exactly as it applies to a contracted deployment: there is no lighter-weight path for “just taking a look”.

What your team inspects

The executed agreement, before anything is sent, with the retention term written into it. If anyone at V3ra ever offers you a faster route for a sample, that is the moment to stop and tell us.

This website

No upload path on this site

Not behind a login, not as a convenience. Charts move under an executed agreement through a channel your team has reviewed, never through a form on a marketing page.

What your team inspects

There is no file input on any page of this site, and no endpoint behind one. It is the cheapest control to verify: read the page source, or point your own scanner at it.

Retrieval

A citation is found inside the deployment

The literature corpus and the embeddings that search it run in the deployment. An encounter is not sent out to a search service in order to find the papers a recommendation rests on.

What your team inspects

The embedding model runs locally against a corpus held on the deployment, refreshed on a schedule you can see. Ask what leaves the network during an analysis, and ask to watch it with the network traced.

Data handling

Your charts train nothing

Charts sent for evaluation produce your findings and nothing else. They are not pooled across customers and are not kept beyond the term in the agreement.

What your team inspects

What V3ra learns from is the clinician's override: held at your site, counted at your site, and reported back to you about your own site. Ask where that signal is stored and who else can read it.

Try it

Move one, and the stack stops fitting.

An encounter is not a row that can be edited. It is a stack: every entry rests on the digest of the one under it. Take a slab out of the middle and nothing above it lines up again.

Selected Recommendation written

at09:41:14

byClinical Intelligence

digest3ac9 10f7

resting onb1d0 6e35

The switch

A clinical tool that is hard to switch off is one nobody should switch on.

Off is a state your side holds. Turn a single clinician off, or the whole department, without asking us and without waiting for us.

Facility AEmergency department

Attending · bays 1–6
Attending · bays 7–12
Resident
Physician assistant
Charge nurse

V3ra is on for everyone in this department.

Where the line is

Nothing is submitted. There is no setting for it.

A system that transmits on a provider’s behalf raises a different set of questions about agency than one that produces a draft. We have stayed on the near side of that line on purpose.

Produces a draft

V3ra Produces a draft

A recommendation, the lines of the chart it rests on, and the rule behind it. Nothing is sent anywhere by writing it.

Decides

A clinician or coder Decides

Accept, change or reject. The decision is written to the log either way. The rejection is kept as carefully as the acceptance, because that is the signal worth having.

Submit, if they submit

Your systems Submit, if they submit

The claim leaves through your own channel under your own credentials. V3ra has no route to a payer and no setting that would give it one.

The Intake Pod

Anonymized at the source. Aggregated at the network.

Each Pod triages on its own and turns the visit into a signal at the point of care. What leaves the Pod carries no name. What the network sees is the pattern across many.

Where compliance stands

Your vendor review, answered before it starts.

Where V3ra stands on each standard your security and compliance teams will check (met, underway or not held), so nothing surfaces late in procurement.

HITRUSTNot held

Not held today

Not held, and not in progress. If your review requires it, you know now rather than at the end of a procurement cycle.

ADAIn progress

The Intake Pod

Built to ADA accessibility requirements, the physical approach and the on-screen flow alike, so no patient is left out of intake by how the unit is reached or read.

SOC 2Underway

Audit in progress

The audit is underway. Until the report is issued, your team can inspect every control on this page directly at a pilot.

HIPAAMet

Under a signed BAA

We sign your BAA before any chart moves and operate as your business associate under it, for an evaluation sample exactly as for a full deployment.

No SOC 2 report is issued yet and no HITRUST certification is held. Nor do we claim that no third-party model is ever involved in an analysis. Where inference runs for your deployment is named in the agreement rather than assumed, and it is a fair thing to make a condition of it.

Send this page to your compliance officer.

If a line here would not survive their review, we would rather hear it now than at the end of a procurement cycle. Bring the hardest question they have.

Request an audit Book a call

What your reviewer gets

The BAAExecuted before anything is sent, retention term written into it
An architecture noteWhere each part runs, and what crosses the boundary
This control listSix mechanisms, each one inspectable
A session with an engineerThey try the update against the log themselves

Ready for your reviewer

Validation Chart Audit