Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Post History

60%
+1 −0
Meta Professional vs Hobbyist advice and potentially dangerous projects

The main problem with a question along the lines of "how do you design a product for medical applications" is that it's way too broad. You cannot reasonably write a somewhat complete answer because...

posted 1y ago by Lundin‭

Answer
#1: Initial revision by user avatar Lundin‭ · 2023-08-23T08:46:09Z (about 1 year ago)
The main problem with a question along the lines of "how do you design a product for medical applications" is that it's way too broad. You cannot reasonably write a somewhat complete answer because it would be a very long one. 

The general approach of all these Q&A sites is that in case an answer to a question needs to be addressed by a whole book/paper/standard, then the question is almost certainly too broad and may get closed as such.

The safety standards for these kind of products do not describe a few but _hundreds_ of things to consider, including things like general quality and documentation procedure beyond the pure technical aspects. All of this is woven together so you can't really separate the technical implementation from the standards. In general it goes like:

- Analyze the project and gather requirements.
- Write down requirements in a specification.
- Tie each requirement to a technical part in the product, like a certain circuit.
- Document how the certain circuit fulfills the specific requirement, as well as general requirements for the product (clearance/creepage distances, EMC standards or whatever might apply). You might have to list technical parameters like number of operations, temperature range, mean time to failure etc etc.
- Design a test that demonstrates how to circuit fulfills the requirement. Both engineering tests as part of product development and production tests, where applicable.

If we were to answer to leave out most of this and just say something like "use a hall effect sensor with 3.3V supply" then the answer is by no means complete and probably not helpful. Potentially dangerous too.

---

> Should we use "hobbyist" and "professional" tags to specify what kind of answer we are looking for?

There are no such thing as "hobbyist med-tech" or "hobbyist safety-related" applications. There are only legal and illegal applications.

We also have a reaction feature next to the voting buttons where we can pick "dangerous". This should definitely be used on answers proposing "hobbyist" solutions to things like med-tech applications or the mentioned "use Arduino to control fireworks" topic. It can only be used on answers though - questions that aren't specific enough should be closed for that reason.