I don't have a good option. If we're going to change it to pull approach later, can't we just ignore rate changes when doing fluid bolus with sub fluid until you implement the pull approach? Are we even able to do sub fluid bolus yet? Do we have HDF tube sets?

Sure

I'll implement the pull approach later, this is temporary fix.
We need to run Sub pump at Qb rate, if Qb is updated, how can we increase Qsub?

Should we check to see if blood sitting timer has not exceeded time limit before we resume (similar to what we do from rinseback stop state before we start an additional)?

So we will command BP every 50ms for saline (okay, but not the pull approach we talked about) and send DD Qsub commands every 50ms for sub fluid (probably not a good idea)?

Move these functions above the test functions and align with .c file, if possible.

add TODO

break this line

break this line

break this line

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

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!

initialized using resetRinsebackFlags()

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

break this line

recircPublishTimerCtr is an output

Add @message MSG_ID_TD_RECIRCULATE_RESPONSE

break this line