Version: 2.0.0 Date: February 13, 2026
This directory contains formal RFC-style specifications for the HAVEN Protocol.
HAVEN (Health Asset Value & Exchange Network) is a value exchange protocol for patient-controlled health data. It defines how health data is referenced, consented, audited, and valued—without prescribing storage, computation, or payment mechanisms.
- Data structures for health assets, consent, provenance, and contributions
- Consent verification semantics
- Provenance chain construction and verification
- Value calculation formulas (reference implementation)
- Exchange format for interoperability
- Data storage mechanism
- Encryption scheme
- Key management / recovery
- Identity verification
- Computation model
- Payment / compensation mechanism
| Document | Primitive | Status | Description |
|---|---|---|---|
| 001-health-asset.md | Health Asset | Draft | Governed data reference with quality scoring |
| 002-consent-protocol.md | Consent Protocol | Draft | Programmable authorization |
| 003-provenance-record.md | Provenance Record | Draft | Append-only audit trail |
| 004-contribution-model.md | Contribution Model | Draft | Value quantification |
| 006-exchange-bundle.md | Exchange Bundle | Draft | Interoperability format |
| Document | Extension | Status | Description |
|---|---|---|---|
| 005-psdl-integration.md | PSDL Integration | Draft | Declarative policy language (optional) |
Each specification follows this structure:
- Overview - Purpose and scope
- Data Model - Type definitions, field constraints, invariants
- Operations - API contracts, pre/post conditions
- Cryptographic Requirements - Hashing, signing, verification
- Serialization - Canonical form, wire format
- Conformance - MUST/SHOULD/MAY requirements (RFC 2119)
- Security Considerations - Threat model and mitigations
- Examples - Concrete usage examples
- Test Vectors - Reference inputs/outputs for conformance testing
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in these documents are to be interpreted as described in RFC 2119.
- Protocol, not platform - HAVEN specifies data structures and semantics only
- Built on standards - FHIR R4, OMOP CDM for data; Ed25519/SHA-256 for crypto
- Value exchange focus - How to quantify and track value, not how to distribute it
- Economics are open - Formula specified, payment mechanisms left to community
- Minimal and deterministic - Clear semantics, predictable behavior
- Whitepaper - Protocol overview and design rationale
- Implementation Guide - How to implement HAVEN
- TypeSpec Definitions - Machine-readable type definitions (source of truth)
- Test Vectors - Conformance test data
- PSDL Repository - Patient Scenario Definition Language (optional)
Specifications use semantic versioning:
- Major: Breaking changes to data models or semantics
- Minor: Backwards-compatible additions
- Patch: Clarifications, typo fixes, examples
Current version: 2.0.0
These specifications are released under CC BY 4.0.