Thank you for the clarification!

break into two lines

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

Add newAlarmIndicateStop to output

Add newAlarmIndicateStop to input and output.

Arpita, we don't want to use doxygen style comments for function prototypes since we cover functions with the function headers. so this is the proper type of comments.

Bubble status, Low and high level level sensors.

Input : Blood pump door status?

To be restored?

Are these being initialized in the init function?

Need to resolve the merge issues?

pauseBolusResumeState is input

add alarm

Replace // to ///< for line 56 to 60

Use // comments for function prototypes.

Either no comment or // comment for function prototypes since doxygen captures function details from function headers.

These were fine (and preferred) as // because doxygen gets function details from function headers in the .c file.

Should we be looking at tubing set type instead of modality here?

Can we not determine this now? Why TODO?

Shouldn't we be checking tubing set type instead of modality here?

verify given type is valid (< NUM_OF_TUBE_SET_TYPES) and trigger s/w fault if invalid.

Initialize to UNKNOWN type. Remove TODO.

Consider adding TUBE_SET_TYPE_UNKNOWN = 0 as first enum so you can initialize a type variable to something before we install/identify the type.

Use /// when above, use ///< when to the right.
Also remove extra space before Tube

Change // to ///<