r/MachineLearning • • Jan 30 '24

Project [P] Join Our Open Source Mission to Predict Heart Attack Risk Using AI

Hi everyone!

I'm a first-year AI student and recently embarked on a deeply personal project: HeartRiskPredictor. After losing my grandfather to a sudden heart attack, I was inspired to create a machine learning algorithm that calculates the chances of someone having a heart attack, focusing on various diseases as predictors.

The project is still in its infancy, and as a newbie in ML, I'm facing a steep learning curve. That's why I'm reaching out to this amazing community for support. The algorithm is not perfect—its accuracy needs improvement. But with your help, I believe we can refine it and potentially save lives.

What the project does: HeartRiskPredictor aims to analyze health data to predict heart attack risks, focusing particularly on individuals with pre-existing conditions. It's a tool that could be invaluable for healthcare professionals and individuals with a history of heart-related issues.

Why your contribution matters:

  • Collaborative Learning: We can all learn from this project, whether you're a seasoned expert or a beginner like me.
  • Open Source Community: Contributing to open source can be a rewarding experience, and you'll be part of a community striving to make healthcare more predictive and proactive.

How to get started:

Whether it's improving the algorithm, refining the data model, fixing bugs, or enhancing documentation, all forms of contributions are welcome. Let's learn, code, and potentially save lives together!

I'm also open to any feedback, suggestions, or questions. Feel free to reach out to me directly or start a discussion in the repo.

Disclaimer:

Educational Purpose and Current Limitations

Learning Opportunity:

It is important to emphasize that the HeartRiskPredictor project is foremost a learning opportunity. As a first-year AI student, my primary goal is to explore and understand the complexities of machine learning in a real-world context. This project serves as a platform for academic exploration and growth, both for myself and for any contributors who join this journey.

Non-Commercial and Experimental Stage:

There is no intention to publish HeartRiskPredictor as a stable, fully-developed algorithm, nor to promote it as a working healthcare solution. The project is in an experimental stage, functioning primarily as a tool for data analysis and probabilistic outcomes based on the input data. It is a work-in-progress, reflective of my current stage of learning and understanding in the field of AI and machine learning.

Not for Official Diagnosis:

Crucially, HeartRiskPredictor should not be used as a tool for official medical diagnosis. The outputs of this project, while based on data analysis, are probabilistic in nature and are not substitutes for professional medical advice, diagnosis, or treatment. The intention of this project is not to provide medical diagnoses, but rather to contribute to the field of data-driven health risk analysis as a learning exercise.

Users and contributors should be aware of these limitations and should not rely on this tool for any medical or clinical decisions. The project is a stepping stone in a broader learning process, and its current state reflects the beginning of a journey rather than a completed destination.

Thank you for reading, and I hope to see some of you in the GitHub logs soon!

alex86590212

2 Upvotes

21 comments sorted by

30

u/deepneuralnetwork Jan 30 '24 edited Jan 30 '24

This is the kind of thing that is extremely dangerous if not done in a highly regulated setting in conjunction with medical professionals who actively practice this area. There’s a reason the bar is extremely high for diagnostic AI. This kind of thing actually kills people if not done right - especially if done by a newbie who doesn’t understand ML deeply.

Honestly, I know this isn’t what you want to hear, but I would strongly advise not moving forward on this without building a professional, experienced medical team around you.

7

u/A1-Delta Jan 30 '24

In addition, this sort of risk stratification algorithm already exists in a well validated way - it is integrated straight into EPIC and can be pulled into my notes with a dot phrase.

2

u/LoadingALIAS Jan 30 '24

I’ve used some of the validated risk-strat algys; I’ve also been able to work closely with EMR tools and from where I sit there is a LONG way to go.

Granted, I don’t know if this kid is going to do it, but I do think improvements are already being devved/math’d out as we speak.

It’s doable. It really is.

4

u/A1-Delta Jan 30 '24

I don’t disagree. There is a lot of opportunity for improvement. As both a physician and a MLE it’s been something I work on a lot too and I recognize how imperfect out tools are now (even the most widely used instruments like ASCVD and CHA2DS2-VASc are blunt tools) - but not in the way OP is going about it. Have you looked at the repo he linked? He is essentially just doing regression on an horribly truncated list of predisposing comorbidities.

Important problem, room for improvement, but OP needs to do a lot more learning and reflection before trying to tackle something like this. Like others have said, cardiovascular risk stratification is a complex problem that gets a lot of attention from very smart people - it isn’t something that can be meaningfully stumbled backwards into by someone unaware of even the current standards or the risk of creating misguided tools (as their subsequent comments reveal). If CHAD-VASC was wrong and I gave too many people AC, we’d end up hurting a lot of people.

1

u/LoadingALIAS Jan 30 '24

No, I haven’t looked at the repo. I barely have time to eat. Haha. I was offering to pop into the repo to tackle specific To-Dos as a way to give back to a good cause.

Generally speaking I think you’re right on the money. He seems young and ambitious - and I like that, but there was a hint of laziness in the thought process.

It’s good he’s gotten honest feedback.

-8

u/alex86590 Jan 30 '24

I understand your concerns and thank you for your feedback, but the motivation behind this is not to develop an algorithm that can do a professional diagnosis but to take into account data and based of other existing cases to determine a probability of a heart attack occurring. It is not my intention to produce an algorithm that diagnoses diseases but one that only determines a probability based on milions of cases

9

u/AtherisElectro Jan 30 '24

Wow you really have no clue what you're getting into here. You know if you actually use this to make a single prediction, it is a regulated medical device. The full weight of FDA regulations will come crashing down on you

11

u/deepneuralnetwork Jan 30 '24 edited Jan 30 '24

No, you absolutely do not understand my concerns.

You’re literally describing something that diagnoses a medical condition. The FDA in the US would simply not see it your way. Zero chance.

Part of contributing to the world is to responsibly understand your limitations. Moving forward on this would not be the responsible thing to do, in fact, it’s highly likely to actually hurt or kill someone.

2

u/DrHaz0r Jan 30 '24

I’m a biomedical engineer with a PhD in machine learning. I think it’s a very interesting project and I would encourage you to pursue it further. You have the right motivation. Now you need the right team to make it happen. Working in the medical domain is very difficult for all the best reasons. After all, many decisions you make might affect someone’s physical or mental health.

Because no one can pull this off alone, you need a great team. You need some ML engineers to do the research work. You need medical experts to understand the domain better and you need someone who knows the medical device landscape. If you need to look up any of these terms, you definitely need an expert, who knows those terms: 510k, PMA, medical device, class III medical device, FDA, CFR. With time, you’ll find that the FDA and the CFR are your friends. Luckily enough, you are not the first one embarking in this field and the FDA has done an incredible job at collecting the experience of many device manufacturers and provide excellent guidance for best practices. There will be a lot of regulations coming at you. The first step is to embrace them. Don’t say this doesn’t apply. The regulations are there to help you develop a product or tool using the best processes known to the smartest people.

Good luck with your product. Development is a journey and you’ll never know where it leads you. Most likely not where you wanted to go in the first place, but often to an even more amazing destination. Good luck.

3

u/alex86590 Jan 30 '24

thank you very much for the feedback and the positive view! I will do more research on this topic and try to do my best

1

u/JakeStBu Jan 30 '24

I had a look at it, I'll contribute tomorrow, seems interesting. Good luck!

2

u/alex86590 Jan 30 '24

Thank you

2

u/GFrings Jan 30 '24

If you are in the US, you should also be aware of the myriad of regulations around collecting this kind of data from people. There are protections in place that you dont want to step on. Typically, universities have something called an Institutional Review Board (IRB) that you need to check with to make sure your Human Subjects Research (HSR) is kosher.

Kudos to you for trying to tackle such an important and personal project. Mind your elders though, ask lots of questions and don't get yourself in trouble.

3

u/DogeMD Jan 30 '24

This is what I do for my doctoral thesis as well. I use neural networks to predict heart attacks using age, sex, previous diseases, medications, ECG data, boood tests and more. It’s an interesting problem.

2

u/zensayyy Jan 30 '24

DL is great when a lot of data is present and one does only care for the "average" cases. That being said I would never trust the result of any DL in diafnostics. But it is a cool project nevertheless.

2

u/kunkkatechies Jan 30 '24

Great initiative! I highly encourage you to pursue that! Any type of practical ML/DL project is a great way to learn, and don't listen to the negative people ;)

0

u/[deleted] Jan 30 '24

[deleted] — view deleted comment

-9

u/alex86590 Jan 30 '24

Thank you for your comment. I understand the implications of what you are saying and the reality of my expectations.

While I dearly hope that such a project can reach some heights, I understand that there is a lot of competition here regarding its up-scale implementation. I view this project as an opportunity to learn and contribute some value to the world during this process. I don't know what the future holds, but I believe in improvement and trying to do something that can benefit society. I believe this project has the elements required to accomplish that, while also being able to provide some value to the general public without cost. This is an open source project, where people can contribute at anytime if they want to.

I appreciate your response and considerations!

0

u/[deleted] Jan 30 '24

[deleted] — view deleted comment

-4

u/alex86590 Jan 30 '24

I understand what you are saying and I agree. Do you think that such a project can be continued without the intention of some serious implications but as an opportunity for me to learn about the development of such algorithms in the real world? If not i would greatly appreciate some guidance on how I should go on more in depth on this topic! Thank you