RenalRoute is a MOCK project that aims to make travel possible for dialysis patients—safe, simple, and stress-free! We created this project for the EmpHack event.

• About
• Usage
• Development
• Community
  • Contribution
  • Branches
• FAQ
• Gallery
• Credit/Acknowledgment

RenalRoute is a one-stop travel planning platform designed specifically for dialysis patients, making travel safe and stress-free. It connects patients with a global network of dialysis centers by automatically scheduling treatment sessions and handling appointments so they can focus on enjoying their journey. By integrating smart travel planning, easy booking, and direct access to patient reviews and local doctor support, RenalRoute empowers patients to explore new places with confidence and peace of mind.

To use this project, you will have to configure your Google Gemini API Key, and deploy the project onto a webserver. Demo Site: here

Everyone is welcome to make contribution to this project!

follow us on facebook

Your contributions are always welcome and appreciated. Following are the things you can do to contribute to this project.

1. Report a bug
   If you think you have encountered a bug, and I should know about it, feel free to report it here and I will take care of it.

2. Request a feature
   You can also request for a feature here, and if it will viable, it will be picked for development.

3. Create a pull request
   It can't get better then this, your pull request will be appreciated by the community. You can get started by picking up any open issues from here and make a pull request.

If you are new to open-source, make sure to check read more about it here and learn more about creating a pull request here.

I use an agile continuous integration methodology, so the version is frequently updated and development is really fast.

1. stage is the development branch.

2. master is the production branch.

3. No other permanent branches should be created in the main repository, you can create feature branches but they should get merged with the master.

Steps to work with feature branch

1. To start working on a new feature, create a new branch prefixed with feat and followed by feature name. (ie. feat-FEATURE-NAME)
2. Once you are done with your changes, you can raise PR.

Steps to create a pull request

1. Make a PR to stage branch.
2. Comply with the best practices and guidelines e.g. where the PR concerns visual elements it should have an image showing the effect.
3. It must pass all continuous integration checks and get positive reviews.

After this, changes will be merged.

Q: What programming language is used for this project? A: Mainly html and java

Credit goes to Avis Deng and Austin Deng who contribute the ideas and implementation of this project.