So it jumps into detail quickly and is written by a vendor but this is a pretty good guide handling the architecture and detail. See how read and writes use device and register addresses to issue requests, and responses are managed with clock pulses and bus arbitration.
Yes, well, some. To gain certification, often something customers require, medical devices must comply with standards such as ISO60601 (hardware) ISO62304 (software) and ISO13485 (process, quality management).
The alarm waveforms described are within the scope of the hardware standard guidelines, sufficiently common that application notes such as this exist.
https://www.ti.com/lit/pdf/slaaec3 [ti.com]
It can be indirectly. Addons exist to for instance convert the mathematical models described in Simulink to code (C, VHDL..) deployable to hardware targets. So, algorithms can be developed in simulink and then integrated into an embedded application without manual translation.
Try the Robot Operating System documentation for the software and control side. If you can write the low level drivers then the ROS stack abstracts the IK and other middleware layers allowing you to focus on app and problem spaces.
Old thread now. But often a minimum load is needed for an LDO, particularly on older parts, to work correctly. Such that these are given in datasheets. This is continuously required so is effectively quiescent current. I think this is what the OP was trying to get at.
But failed capacitor reulting in instability seems much more likely.
https://www.ti.com/lit/pdf/sbaa565 [pdf]