Scenario Builder - Shock triggers not working while previous step is still playing
When creating a scenario, the ventricular tachycardia rhythm automatically shocks into a sinus rhythm without following pre-triggered actions. This should not occur and should follow the triggered actions.
Log in to comment and vote
Comments2
Apr 7, 2025
PinnedWe’ve updated scenario builder to fix this issue - so that the ‘upcoming’ trigger doesn’t get overridden by any defib responses from the instructor screen. Performing a shock during a playing scenario step will now count towards the ‘trigger’ of the subsequent step, allowing you to skip forward if the correct defibs are performed.
This feature is now available for early demo via TestFlight.
Please get access by following the instructions here, and we welcome your feedback.
https://app.trucorp.com/trumonitor/beta/
trucorp
Jan 10, 2025
Hello Matthew!
The issue is one we are aware of and is related to how scenario builder works at the moment.
Currently the ‘pre triggered actions’ only work if the scenario step is stopped and waiting for that trigger specifically. On the scenario player screen you would see ‘waiting for 1 Shock over 150J’ for example.
While the scenario player is at ‘waiting for X shocks’ trigger, the shock will not convert into sinus and the scenario trigger is respected.
However if you are still playing the previous step and haven’t reached the end of that step yet, the ‘trigger’ from scenario builder isn’t active, and the default is used (usually sinus!)
We are aware this is an issue and are going to fix this soon.
In the mean time, you can work around this by either skipping to the end of the VT step or shorten the VT step down to 15 seconds so it reaches the ‘waiting for X shocks’ stage quickly.
I hope this makes sense but if you need more help we can give you more specific tips on this.