FIRST VAULT PILOT / PLANNED

One question.
A boundary we can test.

Begin with one synthetic dataset class and one bounded collaboration. Validate the route from deposit to anonymized research view to reviewed output before considering an approved real-data pilot.

Review the acceptance gates
INITIAL SCOPE

Synthetic recovery
research data

Question
Compare post-surgery recovery patterns.
Participants
Two hypothetical institutions and named reviewer roles.
First evidence
Reproducible synthetic tests, including denied releases.
No partner or active study claimed
GATE 01Planned

Agree the contract

Define one data class, its research purpose, responsible custodian, recipients, approved locations, retention and review ownership.

Evidence required
A versioned data-flow and responsibility model. No identifiable-record path to another clinic or external AI.
Release is blocked by
Unowned data flow, ambiguous recipient or missing research authority.
GATE 02Planned

Prove preparation at source

Implement artifact-specific filtering, de-identification assessment and reviewer approval inside the custody boundary.

Evidence required
Synthetic fixtures for identifiers in fields, notes, metadata and rare combinations. Documented method and measured disclosure risk.
Release is blocked by
Direct identifiers, reversible keys, unreviewed text or failed assessment.
GATE 03Planned

Enforce release and task limits

Bind permission to the exact reviewed artifact, purpose, environment, recipient and expiry. Validate proof statements and their limitations.

Evidence required
Denied requests for changed artifacts, expired permissions, revoked authority, unapproved recipients and external-model fallback.
Release is blocked by
Any missing check, stale approval or attempted scope expansion.
GATE 04Planned

Review outputs and operations

Evaluate scientific usefulness, small-group disclosure and applicable patient-level model privacy. Test operational access, logging and incident handling.

Evidence required
Reproducible evaluations, reviewer decisions, revocation and deletion tests. Synthetic gate acceptance before any separate real-data review.
Release is blocked by
Unreviewed output, unresolved privacy risk or incomplete operational acceptance.

REAL DATA IS A SEPARATE DECISION

Synthetic acceptance first.
Institutional readiness next.

01

Confirm the responsible organisations

A real pilot needs an actual custodian, research owner, qualified reviewers and an approved purpose. A hypothetical scenario supplies none of that authority.

02

Review the actual deployment

Validate the applicable privacy basis, de-identification method, security controls, agreements, locations and operational responsibilities. No HIPAA status is inferred from this plan.

03

Expand only after acceptance

Clinical, Trials and AI capabilities need their own readiness evidence. The first Vault pilot is a bounded learning milestone, not a general medical launch.

ADVANCE DISCOVERY TOGETHER

Bring a precise question.
Build the evidence together.

Discuss a non-sensitive pilot outline with the Hybrid team.