Frequently asked questions.

Scramble is a jurisdiction-wide response and data layer for out-of-hospital cardiac arrest: the dispatcher initiates the incident, the platform coordinates verified responders and accessible AEDs, and every action becomes part of an auditable pre-EMS record.

No. Alerting is one component. Scramble is the operating layer around the alert: the register of responders, AEDs and building access; the dispatcher-initiated alerting and tasking; the pre-EMS record produced by the response; and the intelligence layer built on that record.

An alerting app on its own leaves the register, the governance and the measurement with the buyer.

A dispatcher. Scramble does not detect arrests and does not decide that one has occurred. The incident is initiated in the dispatch centre, and the platform coordinates the civilian response around that decision.

Deterministically, by rule. Within 2 km, up to 100 eligible responders enter the rule set, ordered by the shortest combined route — responder to AED where an AED is assigned, then to the patient. Alerts stop once enough required roles have accepted.

No eligible responder is manually excluded and no victim is deprioritised. Every selection decision is auditable.

No. Live response is rule-based and auditable by design. AI is confined to the intelligence layer, which works on aggregated historical data for coverage analysis, AED placement, simulation and policy. It learns from the record; it does not control the response.

No. Scramble is non-clinical operational infrastructure and is procured as public-sector infrastructure rather than as a regulated medical product. It does not diagnose, treat or replace emergency medical services.

The events that make up the response: dispatch, alerting, acceptance, arrival, AED assignment and retrieval, CPR and shock. Each is time-stamped at source and carries a confidence level per field.

The data model follows ADEMSIS v1 and the Utstein 2024 update.

Three precision levels. Directly logged and second-precise: system timestamps for dispatch, acceptance, arrival and AED scans. Derived with validation: for example CPR-start time inferred from in-app metronome sync and checked against responder input. Survey with a confidence band: subjective, retrospective elements captured in a short post-response survey.

Researchers and regulators can therefore see exactly what each data point means, instead of treating every field as equally certain.

Ownership and governance of the register and the record are established with the health authority of the jurisdiction. Scramble operates the infrastructure; the jurisdiction holds the evidence base.

Because what is not counted cannot be improved. Without a centralised, real-time registry linking pre-hospital and hospital data, researchers cannot analyse survival and policymakers have no empirical ground. The true scale of out-of-hospital cardiac arrest in the UAE is currently unknown, and that absence is itself the argument for building the layer.

Scramble is the public jurisdiction layer, sold to a health authority. ERPVE is the private-domain layer, sold per property or portfolio, covering everything beyond the building entrance: access, security, lifts, internal routing and verified on-site AED availability.

They feed each other. ERPVE audits keep the central register accurate; the register makes alerting more precise.

Abu Dhabi is the intended first jurisdiction, with the operating model designed to be repeatable emirate by emirate and then across GCC jurisdictions with comparable high-rise urban form. No pilot or partnership is secured today; that is the outcome we are working towards.

That is the intended shape: the dispatcher starts the incident, automatically when integrated with a CAD system. The specifics depend on the systems in place in the jurisdiction, so we would rather scope it with you than describe it in the abstract.

No. The site sets no cookies and uses no cross-site tracking. If aggregate visit statistics are enabled, they are collected without cookies and without building a profile of you.

It is delivered to us by email through our form provider and used only to answer you. It is not sold, and it is not used for advertising. The privacy policy sets out the detail.