// runnable playbook

medical device tamper / clinical IoT

device integrity — wrong dose, alarm suppression, unauthorized config. not PHI exfil; evidence is pump, ventilator, monitor, and UDI session logs.

a guided path, not automation — each step opens a tool you run yourself; nothing uploads. progress is saved only in this browser.

// based on the curated pipeline

wraps the medical device tamper — clinical IoT kit preset — drop pump + monitor + UDI session logs → dose anomaly → alarm log → log authenticity → report

methodology guide →worked example →full tool list + 1 more pipeline →

guided steps

0/6 done

01
evidence manifest generator
hash device session logs before parsing — not PHI exfil
open tool →methodology
your note (local only)
02
insulin pump log forensic analyzer
parse pump dose + basal/bolus rows — wrong-dose tamper indicators
open tool →methodology
your note (local only)
03
philips intellivue monitor alarm log forensic analyzer
parse alarm suppression + silence events on bedside monitors
open tool →methodology
your note (local only)
04
medical device udi tracking log forensic analyzer
trace UDI device identity + config change timeline
open tool →methodology
your note (local only)
05
log file authenticity and integrity scorer
score log authenticity — tampered logs invalidate device integrity findings
open tool →methodology
your note (local only)
06
case report generator
draft device integrity report linking dose + alarm anomalies
suggested options · title: medical device tamper — clinical IoT assessment
open tool →methodology
your note (local only)

when you're done

export a run summary — a small JSON record of which steps you marked done, your notes, and a self-hash so the record can't be silently altered. it is your reproducibility note, not a per-tool receipt: each tool emits its own input→output receipt when you run it.