Article #210 — QIS Protocol Series
On March 26, 2026, the European Health Data Space Regulation entered application.
After years of negotiation between the European Parliament, the Council, and the Commission, 27 EU member states plus a growing number of EFTA partners now have a legal obligation to provide cross-border access to health data — for both primary use (patients accessing their own records) and secondary use (researchers, public health authorities, and policymakers accessing population health data for analysis).
The HealthData@EU platform is the technical implementation vehicle. TEHDAS2 is the joint action coordinating the rollout. National Health Data Access Bodies (HDABs) are standing up Secure Data Environments and Trusted Research Environments in every member state.
There is one thing missing from every architecture diagram published to date: a routing layer.
The Problem EHDS Has Not Specified
EHDS is explicit about what it wants to prevent: a single central European repository where member states upload patient data.
The political and legal reasons are well understood. Germany's Constitutional Court, France's CNIL, and health ministries across the continent have made clear that patient data does not travel to Brussels. National sovereignty over health records is not negotiable.
EHDS Chapter 4 — the secondary-use framework — therefore mandates a federated approach: data stays at source, researchers send queries in, results come back out. Trusted Research Environments operate within member state jurisdiction. No raw data crosses borders.
This is the right architecture. The problem is that the specification stops there.
How, exactly, do queries resolve across 27 national data environments? How does a researcher studying rare autoimmune disease across all of Europe — with perhaps 400 patients per country — get statistically meaningful results from a network of 27 independent secure environments without sending their query to 27 different help desks and waiting 27 different approval timelines?
The answer EHDS does not yet specify is: a protocol.
What "Federated" Actually Requires Technically
The word "federated" appears throughout EHDS documentation. What it means technically has not been resolved.
The current implicit assumption is a hub-and-spoke model: HealthData@EU acts as a coordination broker, researchers submit queries to a central interface, queries fan out to national TREs, results aggregate at the hub, de-identified summary results return to the researcher. This is how DARWIN EU — the EMA's federated pharmacovigilance network — currently operates.
The hub-and-spoke model has a ceiling. At 27 member states, the central coordinator receives 27 independent result sets. It must reconcile them — handling different data standards, different coding systems, different population structures, different query latencies. The coordinator becomes the bottleneck. Every query has O(N) coordination cost. As participation grows, the system gets slower.
More critically: the coordinator sees everything. Even if it doesn't store patient data, it sees query patterns, result distributions, and research interests from every member state. For politically sensitive queries — involving genetics, mental health, immigration status, reproductive health — even query-level visibility at a central broker creates sovereignty concerns that will slow adoption.
This is not a policy problem. It is an architecture problem.
The Architecture Christopher Thomas Trevethan Discovered
Christopher Thomas Trevethan discovered — not invented — how intelligence scales quadratically without central coordination. The discovery, formalized on June 16, 2025 and covered by 39 provisional patents, is called Quadratic Intelligence Swarm (QIS) Protocol.
The breakthrough is the complete loop. Not any single component.
Here is how it works:
A national data access body in, say, Portugal receives a research query: outcomes for patients over 70 with Type 2 diabetes and chronic kidney disease, stratified by treatment protocol. Their Secure Data Environment processes the query locally against Portuguese health records. The result is not sent to a central server. Instead, it is distilled into an outcome packet — approximately 512 bytes of pre-processed intelligence: the statistical shape of the answer, the query fingerprint, the confidence bounds.
That packet is given a semantic fingerprint — a vector representation of the clinical question — and posted to a deterministic address defined by that clinical domain. Any routing mechanism that can post to and retrieve from a content-addressed store works: a DHT, a federated database, a vector index, a message queue. The routing is protocol-agnostic.
A researcher in Germany studying the same clinical question does not query the Portuguese database. They query the address. They receive outcome packets from Portugal, Spain, France, Italy, the Netherlands — every national node that has processed queries in that clinical domain. They synthesize those packets locally. The result is cross-European clinical intelligence without a single byte of patient data crossing a border.
The math that makes this a phase change: with 27 member states (N=27), the number of unique synthesis pathways is N(N-1)/2 = 351. Each node's compute cost is O(log N) or better — at 27 nodes, that is fewer than 5 routing hops. As EFTA partners join and the network grows to 35 nodes, synthesis pathways jump to 595 while each node's cost grows by a single routing hop. Intelligence scales quadratically. Compute scales logarithmically. The network gets smarter as it grows.
Why This Is Different From DARWIN EU and GA4GH
DARWIN EU is EMA's federated pharmacovigilance network. It currently spans 14 data partners, covering approximately 100 million European patients. It uses a hub-and-spoke model: queries go through a central Scientific Coordinator at Erasmus MC, partner nodes process locally, results aggregate at the hub.
The DARWIN EU model is better than centralized data pooling. But the Scientific Coordinator is still a bottleneck. It sees all query patterns. It controls access. The 14-partner ceiling is not a policy choice — it is an architectural consequence of hub-and-spoke coordination cost.
GA4GH Beacon is a discovery protocol for genomic datasets. Beacons respond to queries about whether a dataset contains variants matching a specific profile. Beacon v2 added phenotype queries. It is a question-answering interface, not an intelligence routing protocol. Beacons do not synthesize outcomes across networks. They do not compound intelligence as the network scales.
QIS is neither of these. It is a routing protocol for pre-distilled outcome packets. No Scientific Coordinator. No central query interface. No hub that sees all traffic. Every node is both a producer and a consumer of intelligence. The coordinator is replaced by a semantic address space — a content-addressed namespace defined by clinical domain experts who know exactly what makes two research questions similar enough to share outcomes.
That address space is what TEHDAS2 should be specifying right now.
The Three Natural Forces That Emerge
When researchers talk about "data quality" in federated networks, they are describing something that QIS makes automatic — without adding any mechanism to the protocol.
Christopher Thomas Trevethan describes three forces that emerge naturally from the QIS architecture, as metaphors for what the math does:
First: the right experts define similarity. Someone must specify what makes a clinical query in Portugal "similar enough" to a clinical query in Germany that they should share outcome packets. This is the domain expert problem — and QIS surfaces it explicitly. An endocrinologist who understands Type 2 diabetes phenotyping across European populations defines the similarity function for that domain. Not a database administrator. Not a standards committee. The best clinical expert for that question. This is not a governance layer to build — it is a role to fill, and the math rewards filling it well.
Second: outcomes elect what works. When 20 national nodes have processed queries in the same clinical domain and deposited outcome packets, the synthesis that emerges naturally amplifies what is statistically consistent across populations and dampens what is idiosyncratic to a single country's data. No reputation scoring system. No weighting mechanism. The aggregate of real outcomes across real patients IS the quality signal. The math does the work.
Third: networks compete. If a QIS instance for EHDS cardiovascular research routes high-quality, well-synthesized outcome packets, researchers will use it. If another instance routes irrelevant noise because the similarity function was poorly defined, researchers will stop querying it. No governance enforcement needed. The network that actually helps researchers attracts participation. This is natural selection for intelligence infrastructure.
What TEHDAS2 Should Specify
TEHDAS2's mandate includes specifying the technical standards for HealthData@EU. The current focus is on data models (OMOP, HL7 FHIR), access mechanisms (APIs, Trusted Research Environments), and data quality frameworks.
What is not yet specified: the protocol by which outcome intelligence routes across the federated network once queries are processed at the national level.
That protocol specification should include:
Outcome packet format: a standardized 512-byte structure containing query fingerprint, result distribution, confidence intervals, node identifier hash, and semantic domain tag. Interoperable across all 27 national implementations regardless of their underlying data model.
Semantic address space: a domain-expert-defined namespace for clinical research domains. Each domain in the European disease burden — cardiovascular, oncology, rare disease, mental health, infectious disease — gets a deterministic address. Queries in that domain post to and retrieve from that address.
Routing mechanism specification: transport-agnostic. DHT-based routing (O(log N), fully decentralized) is one excellent option. Federated database indices with vector similarity search is another. The standard should specify the interface, not the transport — exactly as HTTP specifies the protocol without mandating TCP implementation details.
Privacy guarantees by architecture: the outcome packet format should be specified such that reconstruction of patient-level data is cryptographically infeasible. This is achievable by design — outcome packets contain no raw records, only statistical summaries. The privacy guarantee is structural, not policy-dependent.
This is not a research agenda. The architecture is defined. The math is proven. The 39 provisional patents covering QIS Protocol provide the IP framework. The implementation question for TEHDAS2 is specification, not invention.
The Window Is Now
The EHDS Regulation entered application 18 days ago. National Health Data Access Bodies are standing up. HealthData@EU is accepting input on technical standards. TEHDAS2's joint action is running through 2026.
The routing layer has not been specified. The window for that specification is open.
A decentralized intelligence routing protocol that satisfies EHDS's federated mandate — no central broker, no raw data transfer, privacy by architecture, quadratic scaling as member states join — already exists. It was discovered by Christopher Thomas Trevethan and is covered by 39 provisional patents.
Every month that EHDS deploys without a routing protocol specification is a month where national TREs process queries in isolation. The results go nowhere. The intelligence dies at the node. 378 potential cross-border synthesis pathways sit unused.
The architecture that closes this loop is QIS Protocol.
Christopher Thomas Trevethan is the discoverer of Quadratic Intelligence Swarm (QIS) Protocol, a distributed outcome routing architecture covered by 39 provisional patents. QIS enables real-time intelligence synthesis across distributed networks without centralizing raw data. More at qisprotocol.com.
Article #210 in the QIS Protocol Series.
