Add to inputs : heparinSetupResumeRequested

Add @alarm

Add to inputs : interruptedPreTxHeparinSetupState

Does default mean invalid state (s/w fault) or does it mean it's a state that we don't need to do anything for? If latter, add a comment here saying that.

Use if else or ternary operator to set BOOL to TRUE or FALSE explicitly.

Add a TODO comment to adjust this when new syringe pump assembly is ready.

Is this still necessary? Comment out before merging to staging.

Why are registers being repeated? Sync w/ latest HDD.

Can we remove this commented out line of code?

Why is this commented out?

Why is state transition and publish removed?

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?

While you are updating this file, can please break this line?

Can we align like this
result = u32BroadcastIntervalOverride( message,
&preTreatmentStatePublishInterval,
TASK_GENERAL_INTERVAL );

Add to inputs: preTreatmentStatePublishInterval

Updated to store the result in a local BOOL

Set to local BOOL and then return the BOOL.

Make a #define up top for the 5.

Initialize this in the init function instead of here.

Yes,I Added the Dial-in override function for the publish interval.

Are we going to allow Dialin to override this publish interval?

Add a blank line before return statement.

Try to initialize these broadcast timer counters to different values (between 0 and 19) so that we don't broadcast all data messages at the same time - we want to spread these broadcasts out over each 1 second period of time.

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