Skip to content

A shared operational picture in mass-casualty incidents

Guardian Chain links physical triage tags to a digital patient record, so everyone in the chain of care sees the same picture, in real time.

  • Works without a connection
  • One tag ID through the whole chain
  • Encrypted on site
Operational pictureExercise
Live
3
Priority 1
7
Priority 2
12
Priority 3
2
Expectant
Positions
Events
  • GC-5DN714:05
    assigned to transport
  • GC-8VR214:04
    vital signs recorded
  • GC-3KX914:03
    scanned at collection point

Håll muspekaren över eller tryck för att vända

  • Offline-first on the device, syncing when a connection is available

  • Built for faster triage and a shared operational picture for every responder

  • The patient's history follows them throughout the chain of care

  • The receiving hospital sees the patient before the ambulance arrives

  • A minimalist interface with clear roles

Paper, whiteboards and radio only go so far

In a mass casualty incident, police, healthcare, fire and rescue services and the Armed Forces work at the same time – with different tools and each with only part of the picture.

Today

Command post

Police
Paper tags
Whiteboard
Radio
Healthcare
Paper tags
Whiteboard
Radio
Fire and rescue
Paper tags
Whiteboard
Radio
Armed Forces
Paper tags
Whiteboard
Radio
? ? ?

With Guardian Chain

Command post

Police
Healthcare
Fire and rescue
Armed Forces
radio for voice
Guardian Chain
triage card + app
One shared picture

Information is lost between teams

What is noted at the scene does not always reach the next link in the chain of care.

No shared operational picture

Command lacks a combined view of patients, priorities and where they are.

Decisions are delayed

As casualties increase, priorities and transports are planned on incomplete information.

One tag follows the patient all the way

The tag ID connects the scene, the collection point, transport and receiving care. Every link sees the same record.

  1. Step 1 · Haemorrhage

    ✓ Tourniquet · 14:03…

    PRIO 1

    Scan or tap the card

    MCI-000042

    1

    Triage

    Scene

    The patient gets a pre-printed triage tag with a QR code and an NFC chip. The priority is visible on the tag.

  2. PATIENT RECORDMCI-000042PRIO 1

    I — INJURIES

    Status:At incident site

    HR

    –

    —

    SpO₂

    –

    —

    BP

    –

    —

    T — TREATMENTS

    X

    TQ14:03

    A

    B

    C

    D

    E

    Timeline

    • 14:04Card scanned, record createdIncident site
    • 14:03Tourniquet left thighIncident site
    • 14:02Triaged Prio 1Incident site
    2

    Scan

    Collection point

    The tag is scanned or tapped with a phone and linked to a digital record. Nothing is written down twice.

  3. PATIENT RECORDMCI-000042PRIO 1

    I — INJURIES

    Status:At incident site

    HR

    –

    —

    SpO₂

    –

    —

    BP

    –

    —

    T — TREATMENTS

    X

    TQ14:03

    A

    B

    C

    D

    E

    Timeline

    • 14:04Card scanned, record createdIncident site
    • 14:03Tourniquet left thighIncident site
    • 14:02Triaged Prio 1Incident site
    3

    Follow

    Transport

    The record travels with the patient. Treatments and vital signs are logged in transit, even without coverage.

  4. PATIENT RECORDMCI-000042PRIO 1

    I — INJURIES

    Status:At incident site

    HR

    –

    —

    SpO₂

    –

    —

    BP

    –

    —

    T — TREATMENTS

    X

    TQ14:03

    A

    B

    C

    D

    E

    Timeline

    • 14:04Card scanned, record createdIncident site
    • 14:03Tourniquet left thighIncident site
    • 14:02Triaged Prio 1Incident site
    4

    Receive

    Receiving care

    Receiving care sees who is on the way, at what priority and what has been done – before arrival.

  5. COMMAND
    HUB ● CONNECTED5G ● CONNECTED14:24

    ⚠ 1 RED PATIENT EXCEEDING 15 MIN THRESHOLD

    MCI-000042 — 00:15:11

    5

    AWAITING EVAC

    0

    EVACUATED

    15

    AVG DWELL (MIN)

    5

    TOTAL CCP

    INCIDENT MAP

    1 HUB · 4 NODES

    IN DEVELOPMENT
    NODE-01Entrance ANODE-02Entrance BNODE-03Collection pointNODE-04Ambulance staging3 minHUB-01Command post

    3/4 nodes active · LoRa 868 MHz · GNSS

    2P1
    1P2
    1P3
    1EXPECTANT
    AWAITING EVACUATION5 PATIENTS
    1
    MCI-000042P1

    00:15:11

    TIME AT CCP

    2
    MCI-000043P1

    00:14:43

    TIME AT CCP

    3
    MCI-000044P2POLICE

    00:14:28

    TIME AT CCP

    4
    MCI-000045P3

    00:13:52

    TIME AT CCP

    5

    Lead

    Command post

    A shared operational picture of the scene, updated in real time for all involved responders, provides the basis for faster decisions and better resource allocation.

Built to work when the network doesn't

Small nodes in the field, a hub on site and the cloud when there is a connection. Each layer works on its own.

Hub · Mesh
Field nodesHub0Cloud
0queued, syncs when connected1 284synced

Field nodes

Share position and reports over an encrypted LoRa mesh, with no mobile coverage at all.

On-site hub

Keeps everything local and encrypted, runs the operational picture and uses 5G when available.

Cloud

Syncs when a connection is available and gives command and follow-up a combined view.

Works where the mobile network falls short

The hubs use 5G and mobile networks when they are available. When they are not, their own encrypted mesh network takes over – LoRa, with up to 10 km between hubs and nodes depending on terrain.

  • 5G and mobile networks when available
  • Encrypted LoRa mesh, up to 10 km
  • Switches automatically
Cities

When cell towers are overloaded

In a major incident, thousands of calls compete for the same towers. The mesh runs alongside and is not affected by the congestion.

Metro

Underground

Mobile coverage does not reach tunnels and platforms. Nodes pass reports on hop by hop until they reach a hub.

High-rise buildings

Behind concrete walls

Concrete and rebar block signals. Nodes in stairwells and on each floor form a chain up and out of the building.

Mountains and archipelago

Where coverage is thin

Long distances and few towers. With up to 10 km per hop, one hub can cover a large area on its own.

Map support for coordination

The people in charge see where hubs and nodes are and how they reach each other – so resources can be placed where they are needed.

  • Hub
  • Node
  • Mesh link
  • Range

Built for darkness, rain and gloves

Few steps, large touch targets and clear roles. The system supports the tags – it does not require paper to disappear.

Baksidan av triagekortet med MIST-fältrapport

CCP

The tag always works

The physical tag carries the information even when the technology does not.

Works offline

Everything works on the device and syncs when a connection is available.

Encrypted local storage

Patient data is stored encrypted, on site too.

Every action is logged

The record is event-based, so every action can be traced afterwards.

For the people who work in the chain of care

Regions and prehospital care

From first assessment to the receiving hospital.

Fire and rescue services

An overview of casualties during the response.

Police

The same picture of the situation as everyone else.

Defence

Works where regular infrastructure is missing.

In development

We welcome agencies to run pilots with us

We invite agencies to run pilots with Guardian Chain and evaluate the system in their own operations. If your organisation wants to run a pilot or learn more, get in touch.

  1. Prototypes

    Done

  2. Verification

    In progress

  3. Pilots and exercises

    Next