I thought Eliza said they wanted to do blood sitting timer even if blood was rinsed back (still a little blood in line).

Why are we doing this in blood prime? Wouldn't it be easier to do this when we're done w/ rinseback & recirc?

break this line

Add @message id MSG_ID_TD_UI_GENERIC_CONFIRMATION_REQUEST

break this line

break this line

Update function name: handleRinsebackAdditionalState

Thank you for clarifying!

Thank you for clarifying!

Add cumulativeBloodPrimeVolume_mL to ouputs.

Optional: While you are updating, can you please also add bloodPrimeRampFlowRate_mL_min and bloodPrimeState to the inputs?

Add recircAllowed to outputs.

Thank you for clarifying!

What if we're in paused state (because your alarm has stop property set)? Should we return TRUE here if in paused state and interrupted state was the await syringe load confirmation state?

Right now, the load syringe alarm indicates stop so we will go to paused state. Is that what we want to do? Don't we want to stay in this state and wait for confirmation?

Should this alarm have stop property set to FALSE?

initialized using resetRinsebackFlags()

those are initialized in resetTreatmentRecircFlags() and that is called in init

Set "Stops" property back to TRUE like the other reserved UI alarms.

break this line

add an empty else block after the last else if block in these functions
handlePreTxHeparinPreloadState
handlePreTxHeparinAwaitSyringeLoadConfirmationState
handlePreTxHeparinSeekState
handlePreTxHeparinPrimeState
handlePreTxHeparinBolusState

break this line

Add initialization for heparinSetupResumeRequested and syringeLoadConfirmed

Align all the function comments

Delete this row.

Should this be the "Load Syringe" alarm that you just added?

break this line

recircPublishTimerCtr is an output

Add @message MSG_ID_TD_RECIRCULATE_RESPONSE

break this line