it will be adjusted when I merge latest staging

not required anymore, forgot to remove

I think a comment here is needed. Keep it and maybe mention rinseback alarm responses too.

Maybe this should be handled in OperationModes exec since it applies to all confirmations (not just alarm related ones).

There will be confirmations that are not handled here (e.g. power off). So we shouldn't fault in default - we should do nothing.

Shutdown would be handled somewhere else (buttons.c probably). It's not related to alarms.

Is this still possible since we're not returning to TxPaused from rinseback anymore?

Is rinseback completed an indication that we've done a blood prime following a temporary break?
If so, I guess this makes sense, but we have to do more than increase the UF volume. We have to adjust the UF rate so that we will reach the new (larger) UF volume when the treatment completes.
We also need to add RB volume to UF volume in pre-tx when treatment parameters are given/validated (for the final rinseback which we will always have so we should just plan for it before treatment starts).

What if multiple confirmations pending? Which ID will this function return?

Align comments.
Should substitution pump data be moved down to 0xBA instead of commented out?

· /firmware/App/Controllers/AirPump.c	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Modes/ModeStandby.c	(-2, +2)	| History	| Source	| Diff
· /firmware/App/Modes/ModeStandby.h	(-2, +2)	| History	| Source	| Diff
· /firmware/App/Modes/StateTxPaused.c	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/AlarmMgmtSWFaults.h	(-2, +2)	| History	| Source	| Diff
· /firmware/App/Services/AlarmMgmtTD.c	(-2, +2)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/FluidBolus.c	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/FluidBolus.h	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/TubeSetAutoEject.c	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/TubeSetAutoEject.h	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/TubeSetInstall.c	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/TubeSetInstall.h	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/SystemCommTD.c	(-2, +2)	| History	| Source	| Diff
· /firmware/App/Services/TxParams.c	(-2, +2)	| History	| Source	| Diff
· /firmware/App/TDCommon.h	(-2, +2)	| History	| Source	| Diff

]]> Thu, 02 Jul 2026 15:06:54 -0700 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-2 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-2 Vendor - TEL - Jashwant Gantyada and Sean Nash finished reviewing LEAHI-TD-FIRMWARE-LDT-4013-2 LEAHI-TD-FIRMWARE-LDT-4013_Fluid Bolus - FW Implementation - 2/4: ]]> Thu, 02 Jul 2026 14:42:11 -0700 Sean Nash https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-2/#c30350 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-2/#c30350 Sean Nash commented on LEAHI-TD-FIRMWARE-LDT-4013-2

Align =

Should modality be an enum type?

Align =

Should this be an enum type?

What is the 3rd modality?

Return type should be an enum (TREATMENT_TYPE_T).

Return type should be an enum (FLUID_BOLUS_MEDIUM_T).

Move after Modes so they are alphabetized.

· /firmware/App/Modes/ModeStandby.c	(-3, +66)	| History	| Source	| Diff
· /firmware/App/Modes/ModeStandby.h	(-0, +11)	| History	| Source	| Diff
· /firmware/App/Modes/StateTxPaused.c	(-5, +2)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/FluidBolus.c	(-25, +5)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/FluidBolus.h	(-1, +0)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/TubeSetInstall.c	(-0, +35)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/TubeSetInstall.h	(-1, +2)	| History	| Source	| Diff
· /firmware/App/Services/TxParams.c	(-9, +18)	| History	| Source	| Diff

]]> Thu, 18 Jun 2026 09:02:33 -0700 Dara Navaei https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4003-1 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4003-1 Dara Navaei started review LEAHI-TD-FIRMWARE-LDT-4003-1 ]]> Mon, 15 Jun 2026 12:26:30 -0700 Vendor - TEL - Praneeth Bunne https://devapps.diality.us/changelog/td-firmware?cs=da286decac70b8da5b369ccca36c05fb5bdb7c73 https://devapps.diality.us/changelog/td-firmware?cs=da286decac70b8da5b369ccca36c05fb5bdb7c73 Vendor - TEL - Praneeth Bunne committed da286de on branch LDT-4013-fluid-bolus-1, LDT-4028-pre-treatment---fw-implementation and 5 more in td-firmware LDT-4013-1: Addressed CR comments

· /firmware/App/Modes/StateTxPaused.c	(-1, +1)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/FluidBolus.c	(-4, +8)	| History	| Source	| Diff
· /firmware/App/Services/StateServices/TubeSetInstall.c	(-0, +1)	| History	| Source	| Diff

]]> Mon, 15 Jun 2026 11:36:28 -0700 Vendor - TEL - Arpita Srivastava https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-2/#c29916 https://devapps.diality.us/cru/LEAHI-TD-FIRMWARE-LDT-4013-2/#c29916 Vendor - TEL - Arpita Srivastava replied to Sean Nash in LEAHI-TD-FIRMWARE-LDT-4013-2

Thank you for the clarification!

break into two lines

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

Add newAlarmIndicateStop to output