Thanks for writing this fantastic book. I think it is a must read for any software PM or engineer looking to "disrupt" healthcare. That chapter about paper-base

Thanks for writing this fantastic book. I think it is a must read for any software PM or engineer looking to "disrupt" healthcare. That chapter about paper-based workflows was really eye opening for me as someone who has never worked in that kind of environment. I think another big area here is that regulations concerning medical software (such as the design controls needed for FDA Software-as-a-medical-device) are simply outdated and do not reflect software development best practices. Instead of things like testing, fast deploys, monitoring, redundancy, scalability, etc the regulations strongly push people to emphasize up-front specification and documentation, which takes an incredible amount of time and energy out of a project.