Introduction

The Cascade Protocol is a developer-first framework for building secure, interoperable health and wellness applications where patients own and control their data. It provides a modular ontology framework for representing personal health data using Linked Data standards, along with a suite of tools to aid in development.

Data lives in encrypted Solid Pods on the patient's own device. No backend services are involved in core protocol operations. AI agents and applications access data through a consent-gated MCP server interface, with every interaction audit-logged.

Established standards first

FHIR, SNOMED CT, LOINC, and PROV-O before any Cascade-specific term. New vocabulary is only created when no standard exists.

Three-layer architecture

Every data type maps from clinical codes (Layer 1) → domain vocabulary (Layer 2) → patient-facing summary (Layer 3).

Privacy-first, local-first

AES-256-GCM encrypted Solid Pods with keys stored in the device keychain. No data leaves the device during normal operation.

Provenance on everything

Every record carries W3C PROV-O metadata distinguishing clinician-generated, device-generated, and patient-reported data.

Specification

The Cascade Protocol is organized into three vocabulary layers, each serving a distinct role. This architecture is the foundation of the formal specification.

1

Established Standards

Canonical clinical codes from FHIR, SNOMED CT, and LOINC — the universal language of healthcare systems. Cascade data is always traceable back to these codes.

2

Cascade Domain Vocabulary

Domain-specific properties (health:, clinical:, pots:, coverage:) that link to Layer 1 codes and add context for wellness devices, EHR records, screening protocols, and insurance data.

3

Patient-Facing Summary

Aggregated summaries and visit-prep documents (checkup:) designed for people, not systems — combining EHR data, device readings, and patient-reported information into a coherent picture.

Semantic Vocabularies

Seven interlinked OWL vocabularies covering core identity, health device data, clinical records, patient summaries, specialized screening protocols, insurance coverage, and chronic disease management. Every vocabulary includes SHACL validation shapes, JSON-LD contexts, and human-readable documentation.

Browse all vocabularies

Vocabulary Specification

The authoritative source for all Cascade Protocol ontologies — OWL class definitions, SHACL validation shapes, and JSON-LD contexts for every vocabulary. Versioned using MAJOR.MINOR with backward compatibility guarantees within a major version.

Versioning policy View on GitHub

Conformance Suite

Fixture-based test suite for validating SDK implementations against the specification. Covers all data types across clinical v1.7, coverage v1.3, and core v2.8 with both positive (happy path) and negative (constraint violation) cases. Used to verify that serialized Turtle output is SHACL-valid.

View on GitHub

Serialization Spec

Formal specification for RDF/Turtle serialization format, required namespace prefixes, and canonical ordering rules.

View spec

Pod Structure

Directory layout, file naming conventions, storage organization, and discovery conventions for Cascade data pods.

View spec

The protocol is expressed through seven semantic vocabularies. Browse all vocabularies →

Tools & SDKs

All Cascade Protocol tools are open source and available on npm and PyPI. Choose the stack that fits your project.

Jump to TypeScript · Python · CLI · Agent · Swift

TypeScript SDK

Full SDK for building Cascade Protocol applications in TypeScript and JavaScript. Includes typed models for all 21 health record types, RDF/Turtle serialization, SHACL validation, and Pod management.

npm install @the-cascade-protocol/sdk
Read the guide View on GitHub

Python SDK

Python library for reading and writing Cascade Protocol Pods. Includes Turtle serialization, RDF deserialization, SHACL validation, and pandas integration for data analysis and research workflows.

pip install cascade-protocol
Read the guide View on GitHub

CLI

Command-line interface for managing Pods, validating data against SHACL shapes, converting FHIR records to Turtle, and running a local MCP agent server. The foundation all other tools build on.

npm install -g @the-cascade-protocol/cli
Read the guide View on GitHub

Cascade Agent

Natural language interface for the Cascade Protocol CLI. Describe what you want in plain English — the agent plans and executes the right sequence of CLI commands, streaming results in real time, with the option to use local LLMs.

npm install -g @the-cascade-protocol/cli
Read the guide View on GitHub

Swift SDK Early Access

Native Swift SDK for iOS, watchOS, and macOS. Provides local encrypted Pod storage with AES-256-GCM, automatic RDF/Turtle serialization, HealthKit data ingestion, WebID-based identity, and audit logging. Currently in active development.

Contact for early access

Agent Integration

The Cascade Protocol is designed from the ground up to be agent-readable. Every record carries semantic type information, standard clinical codes, and provenance metadata — giving agents the context they need to reason about health data without requiring custom parsing or brittle prompt engineering.

How It Works

Agents access Cascade Pods through the MCP server interface provided by the CLI. All queries are consent-gated, executed locally, and audit-logged. The agent sees a structured graph of typed health records — medications linked to conditions, lab results to reference ranges, diagnoses to clinical codes — not a flat document.

Agent guide View examples Security model

Working Examples

Three end-to-end examples with full agent prompts, expected outputs, and security documentation: medication interaction review (correlating ACE inhibitor + potassium supplement + K+ lab value), health trend analysis (blood pressure patterns over 3 months), and visit preparation (aggregating clinical, wellness, and patient-reported data).

Browse examples

Security & Compliance

Security and regulatory compliance are built into the protocol architecture, not layered on top. The Cascade Protocol is designed to support HIPAA-ready applications without requiring backend infrastructure.

Security & Compliance Guide

Covers encryption at rest, consent-gated agent access, audit logging, PHI handling, provenance model, threat model, and regulatory considerations including HIPAA and the 21st Century Cures Act.

Read the security guide

Protocol Comparison

How the Cascade Protocol compares to FHIR R4, Apple HealthKit, OpenEHR, and ad-hoc JSON across seven dimensions: data model expressiveness, provenance support, agent readability, local-first capability, patient ownership, format conversion, and ecosystem maturity.

Cascade vs FHIR, HealthKit, OpenEHR, Ad-hoc JSON

Side-by-side comparison table, code examples for the same data in each format, and an honest assessment of where Cascade excels and where established alternatives remain the better choice.

Read the comparison

Case Studies

Real-world examples of the Cascade Protocol in production.

POTS Check — Cascade Protocol in Production

How POTS Check (App Store, December 2025) uses the full Cascade Protocol stack: pots: vocabulary, HealthKit data ingestion, per-record provenance tracking, AES-256-GCM encrypted Pod storage, and Solid-compatible Pod export. One app, one condition, end-to-end proof of concept.

Read the case study All case studies

Resources

Ontology Explorer

Visualize relationships between all Cascade Protocol vocabularies interactively. Explore the three-layer architecture, class hierarchies, and cross-vocabulary links as graphs and sortable tables.

Open Ontology Explorer

Interactive Guide

Ask questions, get explanations, and explore the vocabularies through conversation. Powered by Google NotebookLM — a Google account is required to access.

Open in NotebookLM

Developer Guides

In-depth guides covering advanced CLI usage, multi-source data import, and deterministic identifier generation.

CLI Reference

Complete reference for every Cascade CLI command, flag, and subcommand. Covers Pod management, SHACL validation, FHIR conversion, MCP server, and conformance testing.

Read the guide

Multi-Source EHR Import

How to import and merge health records from multiple EHR sources (Apple Health, FHIR R4, C-CDA) into a single Cascade Pod, including deduplication and provenance tracking.

Read the guide

Deterministic IDs (CDP-UUID)

How Cascade Protocol generates stable, collision-resistant record identifiers from content hashes, enabling safe deduplication and cross-source merging without a central registry.

Read the guide

Technical Blog

Deep dives into the technology and design decisions behind the Cascade Protocol.

RDF/OWL for Health AI

Why RDF/OWL is the right foundation for health AI agents — semantic grounding, three-layer architecture, and a concrete medication interaction example.

Read post

Provenance as a Compliance Primitive

How Cascade's five provenance classes and W3C PROV-O turn data lineage into a compliance artifact for HIPAA and the 21st Century Cures Act.

Read post

Local-First Health AI Architecture

The case for running AI agents on-device with zero health data leaving the machine — compliance, privacy, and the practical MCP setup.

Read post

View all posts →