Vera Health — the reference of the clinical evidence engine.
Thirty sheets. Every subsystem of the clinical evidence engine — Council governance, Enterprise deployment, Mobile point-of-care, Evidence taxonomy, Refusal states, Reconciliation, Benchmarks, Security — rendered as a live, interactive surface. Not described. Operated. Every control writes to a state contract. The state contract is what Vera's endpoint consumes on activation. The reference is the system.
"Gray's Anatomy is not a book about the body. It is the body, laid open, sheet by sheet. This reference is not a site about the clinical evidence engine. It is the engine, laid open, sheet by sheet. Every cut working. Every layer live. The reference is the system."The Gray's Anatomy frame · ESAN Network
- Sheets
- 3016 live · 14 rebuild
- Subsystems
- 12all wired
- Query layer
- 100curated · live
- Contract
- v1endpoint ready
What are the subsystems of the clinical evidence engine?
Twelve subsystems. Each is one or more sheets. Each sheet is a live surface. Select a subsystem to enter its sheet.
The clinical evidence engine has twelve subsystems: Governance, Enterprise Deployment, Mobile Point-of-Care, Evidence Taxonomy, Refusal States, ACEP Reconciliation, Benchmarks, Security, Category, Trust Surface, Specialty Contexts, and Citation Interaction. Each subsystem is rendered as a live sheet. Each sheet is operated, not described. The sheets together are the reference.
Governance
The Vera Clinical Council. Nine seats. Quarterly blinded calibration. Rubric, model, and refusal authority. Dated resolutions. Public record.
Subsystem 02 · Sheet 17Enterprise Deployment
Four-layer deployment inside health systems. Engine · compliance · integration · governance. SSO · SCIM · HL7 FHIR R4 · SMART on FHIR. Six-week activation.
Subsystem 03 · Sheet 12Mobile Point-of-Care
The trust surface at the bedside. 375px. One-thumb. Tap-first. Grade visible before the claim is read. Four viewports. Four phases.
Subsystem 04 · Sheet 03Evidence Taxonomy
The five-axis grading system. Study design · journal quality · citation impact · recency · contestedness. Every source scored on every axis.
Subsystem 05 · Sheet 05Refusal States
The designed surface element that renders when no source clears the threshold. R-01 through R-04. Refusal is a design surface, not an error state.
Subsystem 06 · Sheet 06Reconciliation · ACEP
The reconciliation layer. ACEP policy and literature grade rendered side by side when they diverge. Aggregate divergence signal. Non-voting liaison.
Subsystem 07 · Sheet 07Benchmarks
Replayable benchmark record. Contamination posture. Published results against the current model version.
Subsystem 08 · Sheet 08Security
Zero PHI retention. Stateless query pipeline. HIPAA-aligned. SOC 2 Type II. Every pipeline stage documented.
Subsystem 09 · Sheet 02Category
The clinical evidence engine category, defined by four tests and a quadrant map. Adjacent competitors named. Category moat established.
Subsystem 10 · Sheet 09Trust Surface
The visible layer of the evidence engine. Pages, tokens, citations, refusals. Makes the engine's rigor legible to a clinician.
Subsystem 11 · Sheet 13Specialty Contexts
Five specialties. Emergency Medicine · Oncology · Cardiology · Pediatrics · Pharmacy. Same grammar. Different evidence.
Subsystem 12 · Sheet 11Citation Interaction
The tap-first citation pattern. Opens the passage in place. Context preserved. Reading position restored on close.
What defines the clinical evidence engine category?
Four tests. Binary membership. A system either passes all four, or it is not in the category. Vera passes all four.
Four tests define the category. Test 01 — Claim-Level Grading: every rendered claim traces to at least one graded source. Test 02 — Designed Refusal: the engine refuses when no source clears the threshold. Test 03 — Five-Axis Composite: study design, journal quality, citation impact, recency, contestedness. Test 04 — Point-of-Care Constraint: ten to eleven seconds between question and action. A fails all four. A passes all four. The boundary is binary.
Claim-Level Grading
Every rendered claim traces to at least one graded, admissible source. Not every answer — every claim inside every answer.
Designed Refusal
The engine refuses when no source clears the threshold. Refusal is a designed surface, not a failure. R-01 through R-04.
Five-Axis Composite
Study design · journal quality · citation impact · recency · contestedness. Five independent axes weighted into one composite.
Point-of-Care Constraint
Ten to eleven seconds between question and action, per cofounder Taieb Bennani. Every element placed to the window.
Category membership is binary. A system either passes all four tests, or it is not in the category. There is no partial credit. A retrieval engine that ranks sources without grading them fails Test 01. A system that renders every claim without a refusal surface fails Test 02. A model that grades on a single axis fails Test 03. A reference tool that tolerates a sixty-second answer fails Test 04.
The category was coined and defined by LeadReadySite under trademark USPTO #63/502,991. The definition is dated. The vocabulary is canonical. The category boundary is the moat.
What makes this reference a working model instead of a documentation site?
Five pillars. Every page in the reference carries all five. Remove any one and the reference stops being a working model.
Five pillars: (1) Sheet Index — the spine. Every page carries it. Thirty sheets. Current one marked. (2) Live Interactives — every concept is a control. Nothing is described that cannot be operated. (3) State Contract — every control writes to one JSON object. The object is what crosses the wire. (4) Data Source Panel — the page declares whether it is running on the or an . (5) Activation Handoff — paste the endpoint. Test the handoff. See the exact bytes that will cross. Every page carries all five. The reference is the system.
Sheet Index
The spine. Every page carries it. Thirty sheets. Current one marked. Every sheet deep-links with state.
Live Interactives
Every concept is a control. Nothing is described that cannot be operated. Twelve interactives on this sheet alone.
State Contract
Every control writes to one JSON object. The object is what crosses the wire on activation. Copy · Download · Share URL.
Data Source
Local layer today. Endpoint tomorrow. The page always declares which side is answering. One chip. Two states.
Activation Handoff
Paste the endpoint. Test the handoff. See the exact bytes that will cross. Contract spec below for engineering.
The five pillars are the difference between a documentation site and a working model. A documentation site describes the system. A working model is the system. When Vera's endpoint arrives, nothing on this page changes. The source chip flips from sky to green. The data source panel updates. The state contract panel begins posting to Vera's API. The handoff card confirms the wire. Every other pixel is identical.
That is what Pre-Wired for the Next Scale means. The page was built for the endpoint that does not exist yet. When it arrives, the page is already correct.
A system that retrieves, grades, refuses, and renders. Defined by four tests: claim-level grading, designed refusal, multi-axis composite, point-of-care constraint.
A system that returns ranked results without grading, without refusal, without audit. The category defined by contrast. Fails all four tests.
A single subsystem of the clinical evidence engine, rendered as a live interactive surface. Thirty sheets form the reference. Every sheet carries the five pillars.
The spine of the reference. Lists every sheet, marks the current one, deep-links with state. Visible on every page. Collapsible on mobile.
The page runs on a local layer today. On activation, the same queries run against the client's backend. Nothing on the front end changes. Only the source of answers changes.
The ~100 curated queries bundled with the reference. Runs the page today. Replaced by the endpoint on activation. Same shape, same contract.
The JSON payload the page produces that Vera's endpoint will consume on activation. Method, path, headers, body, response shape.
The moment the local layer is replaced by the client's endpoint. The page becomes the production front end. Nothing else changes.