Turning trained people and available AEDs into a measured response.

Thousands of cardiac arrests happen outside hospitals every year. Survival depends on help arriving within minutes. Trained people exist, AEDs exist, dispatch centres exist — but they sit in separate systems, and no layer turns that capacity into a coordinated, measurable response.

What we build

Scramble is a jurisdiction-wide response and data layer. The dispatcher initiates the incident. The platform coordinates verified responders and accessible AEDs by deterministic rule. Every alert, acceptance, arrival, AED retrieval, CPR start and shock becomes a time-stamped record with a confidence level per field.

That record is the part the sector has been missing. Utstein is the international gold standard for cardiac-arrest reporting, but many of its variables originate before EMS arrives — which means they can only be captured by the response itself, not reconstructed afterwards from a run sheet.

ERPVE is the complementary private-domain layer. It verifies readiness inside buildings, where most arrests happen, and feeds that verified property data back into the same register.

Why now

Regulation and a federal training pipeline are arriving together. Abu Dhabi's Department of Health has defined the required capabilities across its 2024 Health Emergency Policy, its 2025 EMS and Ambulance Standard and the 2026 ADEMSIS data standard. Jaheziya has announced an ambition to train one million people in CPR and AED use, with a national responder database.

Training reach is not the same as deployable capacity. A trained person becomes deployable only once they are registered, reached, tasked and linked to an AED. That is precisely the gap Scramble closes.

How we work

Deterministic in live response, analytical only after the fact. Auditable by default: every selection decision and every state change is recorded and can be inspected. Non-clinical: Scramble is operational infrastructure and does not diagnose or treat.

We are explicit about what is known and what is not. Where a figure is an estimate, we say so. Where a partnership is a target rather than an agreement, we say that too.

The team

Stijn Bijker

Founder & CEO

Ten years at HartslagNu, the Dutch national citizen-responder system, from early development to national scale — direct experience with the operational failures, the scaling problems and what makes a citizen-response system work. Policy experience through university-level standards affecting more than 400 organisations.

Sarthak Kalpasi

Co-founder & CTO

Technical owner of the jurisdiction-scale architecture, data model and deployment. Owns the data architecture and Utstein capture pipeline, and builds the rule-based, auditable dispatch engine.

Robin Grit

Advisor

MSc Life Sciences and Technology, combining academic clinical research experience with commercial research pragmatism across medical sensing, remote monitoring, imaging and device research. Advises on evidence design, data validation and device-adjacent collaboration.

Why this, and not something else

A close friend of the founder died of cardiac arrest. The failure was systemic, not medical: the capacity to help was nearby and never reached. That is a solvable problem, and it is an infrastructure problem.

Want the detail?

The full deck covers the architecture, the data model, the dispatch rules, deployment and what remains to be proven.