From what I see in UI, it is just a range value not an enum/index

Is it an enum/index like Denali then?

No we are not getting conv factor from UI on it
I will have to confirm with Nick to see if we will get the bicarbConvFactor

Align comments.

Can we just remove this?

Can we just remove this?

F suffix.

Is bicarbonate also a conversion factor?

Can we just remove the old enum now?

blank line before return.

Blank line after declarations.

Added

Updated

Add a blank line after declarations.

What I meant was that we don't care which blood prime state we're in - what we care about is that we are in treatment mode and priming blood - otherwise this message doesn't make sense and we should reject it because we're not in the right state.
if ( ( MODE_TREA == getCurrentOperationMode() ) && ( TREATMENT_BLOOD_PRIME_STATE == getTreatmentState() ) )

Removed

Added

Yes, Updated

Replaced

This should be invalid state (or something like that).

These are the correct min/max values, but we can't use literals like this. Our coding standard calls these "magic numbers". What we want to do is call getU32TreatmentParamLowerRangeLimit() and getU32TreatmentParamUpperRangeLimit() functions from the TxParams service.

I think what matters is that we are in Treatment: Blood Prime state. I think any of the 3 blood prime states is ok for this message.

I think result and accepted are essentially the same. We should just have one flag and only set to TRUE if everything is correct.