Better to say != TRUE here.

Add TODO comment as to whether we should trigger an alarm/fault here.

Add blank line after declaration.
Fix indent.

We can un-comment syringe pump stop now.

I think this function should be private (called by public message handler).

Should this be static (private)?

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)?

Can we combine this state with prior state? Wait for DD response and mode change in same state?

Only need second condition I think.

This should be switch on requested selection and, in each case, we set next state to wait for disinfect state and set the appropriate command (if not skip) or set next state to wait for treatment (if skip).

I think this should be more general start disinfection function that takes a specific disinfection command enum as a parameter.

Shouldn't this be UI REQUEST message? Why would we need to receive/handle a message that we send?

Do we need to send UI a response? Accept/reject?

Is this a message handler? If so, parameter should be a message and option should be extracted from message payload.

Does this command cause DD to transition to standby? It looks like the command to give when we transition into post treatment mode to tell DD to transition to post-gen dialysate mode.

Switch not needed here. Just signal standby mode with the received selection.

Should be disinfection selection type, not command type.
Also, move this down into if statement scope.

Why are we signaling a command to standby mode? We should signal the selection that we received from UI. Standby mode (later when we get there) will then look at the selection and decide there which command to send to DD.

Remove blank line.

Won't this happen when we transition to auto-eject state? Why do it here?

Shouldn't auto-eject state handle this BP homing?

Why are we worried about "handled"? Once confirmed, should we just go to auto eject state?

Why is this if statement separated from the one above? Why not just do this stuff in that if statement?

There should be function(s) in DDInterface to tell DD what we want (bypass, Qd, etc...).

This publish code should be in a publish function and we just call that function here.