Ordinary Life:
The days were boring. No implementation. No thinking out-of-box. As an Engineering student pursuing Computer Science, attending classes and labs were perhaps the only exposure to the subject. This constant practice drained the motivation that one finds themselves possessing at the initial stages – probably while coding their first “Hello World!” program. The theory, no doubt, was adequate and at times complicated, but in its element, it lacked significance. One at such stage didn’t know the practicality and its real-world operation.
What Happened? ( Sih happened)
Amidst this inactivity, fortunately, we were presented with an opportunity – an opportunity that would go on to change my understanding and improve my skillset. Smart India Hackathon, presented itself around December. I, truly, was excited to know that students were presented with a problem statement that they had to work on in a limited time and offer the best prototype at the national level. In the wake of this occasion, my friends approached me which eventually lead to one of the best teams I’ve had to work with. “Deadsec11” – our team, consisting of 6 members, a blend of branches who brought their own ideas to the table. Each of us were in our own ways capable and contributive towards our project
What we were asked for(Problem statement)
Our Problem Statement was “Voice Prescription” presented by the organization, “Bajaj Fin Serv”. After a week or two of thorough consideration and accommodation of ideas, we set out to develop ‘Doctor’s Voice’ – a one-stop solution for the medical domain that would enhance the understanding of the patient’s problem and improve the mutual rapport. How did we develop the prototype? The application also recognized the doctor’s prescribing suggestions and converted them to text format. Doctor’s Voice took its form as a Flutter-based Application that supported multiple platforms. It integrated Voice Recognition System along with the Voice-to-text conversion algorithm. The text retrieved is formatted into a report with the patient’s details. The progress, each day felt so minute and yet very huge in our path towards the successful execution of the application.
Sih Internal round notice It was at this time around, January when the notice of Internal Round of Hackathon reached us. The internal round evaluation had been declared towards the end of that month. We had to level our schedule and work-progress. Our team leader was well-versed and enthusiastic, his encouragement pulled us through. We realized that learning each concept on our own wasn’t productive to the team or the application itself, as a result, we began explaining what we learned the previous day. Lots and Lots of research: During this process, we were all novices in the area and had made many errors, few even which were not in our scope yet. To correct these errors, each one of us again revisited our concepts, required certain clarification of doubts from our faculty. The Research required was: · Angular JS · FireBase · Google Text-to-Speech API · Type-Script · Dialog Flow · Tensor Flow Understanding the basic routine of doctor prescribing and go through relevant surveys Did we get better? We began understanding each other’s ways of thinking and actually began connecting the concepts to the exercising of application. The first time when we finally executed the voice recognition followed by voice-to-text conversion, I still remember, everyone one of us was surprised, we couldn’t believe it in the first instance. We performed a few test runs with our team members and it did work well What’s our prototype about:
Recording the credentials of the concerned patient Enabling Voice Recognition during Doctor’s consultation.
Retrieving Information from Voice and forming a report.
Converting the report to PDF format and sharing it to the patient.
Editable options to the Doctor concerned.
Patient consulting doctor without demanding physical presence.
Making a proper prescription instead of a doctor’s manual prescription.
Disabling the printing, downloading, and editing of prescription by the patient ( protect health data!)
Authorization through Doctor ID to access previous prescriptions of a patient.
Maybe add a little more: We were excited and thrilled for Doctor’s Voice was our first working prototype that had significance in the real world and welcomed the opportunity to include further modifications that would make the application handling at ease for the users. Doctor’s Voice now had some special features – · Checking history of the patient, · Sharing the report in pdf format through any social platform, · Enabling digital signatures from doctors · Chatbot installed in Whatsapp to help patients directly from home for basic queries. · One of the most economical and medicine-beneficial service on the Social Media Platform. Has it got the scope in the future:
A probable chance of any application deployment in the form of Doctor’s Voice or with much further enhancement would have a future scope in Machine Learning Analytics to observe the health pattern of a patient and would provide Doctors ease for better and quicker comprehension of the Patient’s situation. What happened on the D-Day? The D-Day had finally come upon us, we were all excited and curious. In all honesty, I felt a little tense , maybe nervous about the prototype not working out, but the fact that we cross-checked the application multiple times throughout felt reassuring. The SIH Internal Round begun around 9 am, we initially submitted details and had to present our Prototype to various faculty and the invited delegates. The moment felt inspiring when my teaching faculty had also come to view our problem statement solution and left impressed by our work. I had been curious to see what other teams have developed for their various problem statements and exchanged ideas with few teams. The post-Lunch session that day, the delegates from TCS were going through several team models and we were eagerly waiting for them to approach us. The delegates were friendly and supportive, it was inspiring to see such knowledgeable minds commend our contribution. They further gave certain inputs in order to enhance a few minor aspects of our prototype, in fact, they have given us the idea of approach and resource links to develop the model. It was now the moment of truth. The one moment towards which our team and every other team present in the room had strived for, results of the selection. Our excitement knew no bounds for being selected for the National round of SIH. The Delegates had expressed few words of technicality of the present industry and where we stand in the massive competition and deemed our projects innovative. The day ended with us taking group pictures with the guests from TCS and our team celebrating the achievement. I shared the news with my parents immediately and they were very happy for my team and hoped we give our best for the final round. What is the ultimate gain? The Smart India Hackathon- an amazing opportunity, a thrilling productive experience due to the following traits that I witnessed: Improvement of concept fundamentals. · Approach to application in the real world. · Understanding other’s ideas and sharing their work. · The brightest characteristic of the journey being teamwork. · Learning productively and faster with other’s co-operation. · Recognition of work through friends and family · Collaborating with team members can be fun and long-lasting. Learning has never been so joyous for us before SIH and hence I feel fortunate to be a participant of such an uplifting endeavor. SIH has given me the memories that I will cherish forever and a paramount inspiration with which I look forward to being a part of many such competitions in the future.
Author
Isha Asala
תגובות