Medical Diagnoser

[ramana2074]

Pull Request for PyVerse 💡

Requesting to submit a pull request to the PyVerse repository.

---

Issue Title

Please enter the title of the issue related to your pull request.
Medical Diagnoser

• I have provided the issue title.

---

Info about the Related Issue

What's the goal of the project? To implement a Medical Diagnosis and Prescription System using Deep Learning techniques.

• [X} I have described the aim of the project.

---

Name

Please mention your name.
Venkata Ramana Billana

• I have provided my name.

---

GitHub ID

Please mention your GitHub ID.
ramana2074

• I have provided my GitHub ID.

---

Email ID

Please mention your email ID for further communication.
Enter your email ID here.
billanavenkataramana@gmail.com

• I have provided my email ID.

---

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
Enter your participant role here.
GSSOC Extended Contributor 2024

• I have mentioned my participant role.

---

Closes

Enter the issue number that will be closed through this PR.
Closes: #issue-number
#565

• I have provided the issue number.

---

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified.
This project implements a Medical Diagnosis and Prescription System using Deep Learning techniques. By utilizing the power of Long Short-Term Memory (LSTM) networks, this system is capable of analyzing a patient's symptoms and providing an accurate diagnosis along with the recommended medication. The LSTM model, a variant of Recurrent Neural Networks (RNN), is particularly suited for processing sequential data like patient symptoms and offers significant advantages when dealing with textual data.

• I have described my changes.

---

Type of Change

Select the type of change:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

---

How Has This Been Tested?

**Describe how your changes have been tested.**I
It has been test against different prescriptions and symptoms

• I have described my testing process.

---

Checklist

Please confirm the following:

• My code follows the guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly wherever it was hard to understand.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added things that prove my fix is effective or that my feature works.
• Any dependent changes have been merged and published in downstream modules.

[github-actions]

👋 Thank you for opening this pull request! We're excited to review your contribution. Please give us a moment, and we'll get back to you shortly!

Feel free to join our community on Discord to discuss more!