[jfarmer]

> If we include this as an option in this list, it will contribute to a nationwide epidemic of opioid abuse and countless deaths?

Give. me. a. break!

At a minimum they should ask, "What are the potential downsides? How extreme are they? How can we determine how likely those potential downsides are?"

I'd expect every junior PM to ask _that_ series of questions about any product decision in any market.

There's a reason clinical trials have protocols for early termination. Not understanding that early termination is a thing when building a social app is one thing, but they're building EMR software!

[mywittyname]

Must be nice to work in a place where a developer has complete influence through the entire process. Every place I've worked has been so large that a single developer can only work on a very minute segment of the code unless they are very senior. I'm guessing the bulk of developers work at large companies and have experiences much closer to mine.

This tool was probably built by several teams of developers working somewhat isolated. Someone built a system that allows for treatments to be suggested for certain ailments, another team did the UI, another testing, then there was probably completely separate team of people in charge of determining what to suggest for as treatments. This treatment team was very likely not staffed by developers at all.

Which of these groups are responsible here? Do I need to be pushing back with every dialog option I create with data from a database? Ask my PO, "what are we going to do to ensure that nobody puts dangerous options in the db?" I'm being serious, if you're blaming the developers for this, then you should make suggestions that are appropriate for the real environment most of us work in; that is: we're often a very small cog in a very large machine with no view of the big picture.