Crafting experience...
3/8/2026
A Project Made By
Submitted for
Built At
HuddleHive's WIT Hackathon #5
Hosted By
What is the problem you are trying to solve? Who does it affect?
Have you ever left a doctor's office more confused than when you walked in?
Many patients struggle to understand their diagnoses, lab results, and discharge instructions because these documents are often filled with highly technical medical terminology. For clinicians, this creates an unintended burden: patients return for clarification visits, call for follow‑up explanations, or fail to adhere to recommended care plans simply because they didn’t fully grasp the information provided.
 From an investment perspective, this communication gap represents a significant inefficiency in the healthcare system—driving avoidable appointments, increasing operational costs, and contributing to poorer health outcomes.Â
What is your idea? How does it fix the problem?
Empowering patients with a true understanding of their diagnosis, lab results, and discharge instructions does more than just alleviate their anxiety; it initiates a powerful chain reaction of improved health outcomes across their entire journey.
ClariMED has been built to :
Clarifies and simplifies medical terminology into clear, patient‑friendly languageÂ
Tailor explanations to the patient’s context and condition
Reinforce key actions (medications, follow‑ups, red‑flag symptoms)
Reduce the cognitive load on clinicians
Integrate seamlessly into existing workflow
Our platform directly addresses the challenge of medical complexity by ingesting clinical documents or structured data to pinpoint specific medical terminology, abbreviations, and critical risk factors. It then automatically transforms this data, generating clear, actionable explanations that allow patients to understand their health status. Crucially, the system highlights precisely what the patient needs to do next, what symptoms to watch for, and exactly when to seek help, bridging the comprehension gap
For Clinicians
Fewer clarification visits
Reduced administrative burden and Patient Backlogs
Improved adherence and outcomesMore time for complex cases
For Health Systems
Lower avoidable utilization
Reduced readmissions
Better performance in value‑based care models
Higher patient satisfaction scores
For Investors
A large, underserved market
Clear ROI tied to reduced utilization
Strong alignment with digital health, AI, and population health trends
Scalable across primary care, specialty care, and emergency medicine
How do all the pieces fit together? Does your frontend make requests to your backend? Where does your database fit in?
Robust History Management: Added the ability for users to delete individual analysis records or clear their entire history.
Enhanced History UI: The history section now displays more detailed information for each past diagnosis, including the identified condition, date of analysis, and whether an audio explanation is available.
Secure Data Persistence: Integrated deleteDoc from Firebase to ensure users have full control over their stored medical data.
Visual Polish: Improved the history layout with a more scannable grid, hover effects, and clear status indicators.
Login: Users can sign in using their Google account via the "Sign In" button in the header.
Automatic Saving: Once logged in, every new diagnostic analysis is automatically saved to the user's private history in Firestore.
Accessing History: Click the History icon in the header to view past analyses. Clicking any item will instantly reload that specific diagnosis, including the AI summary, recommendations, and audio explanation.
Data Control: Users can now remove specific items using the trash icon on each history card or use "Clear All" to wipe their history.
The application is now fully equipped to help users track their medical journey over time while maintaining privacy and control.
What did you struggle with? How did you overcome it?
Initially we struggled with ideation, coming up with ideas that we believed could be impactful particularly from the patient lens. Once we had some ideas we pitched them to our team members then voted on what idea we liked the best. This honed our collaboration skills and helped us listen to our team members' ideas better. Once we narrowed down to a couple of ideas, focusing on the scope of possibility with regards to the time constraint was another challenge. We met this challenge head on, zeroing in on the MVP feature, then as time allowed, added more functionality.
Another challenge we faced was translating a conceptual idea into a clear user interface and user journey. We had to think carefully about how a patient would interact with the tool and how to present complex medical information in a simple, understandable way. This required several iterations of the design and discussion about what information was truly essential for the user.
What did you learn? What did you accomplish?
Our team designed and built a full-stack web application that empowers patients to truly understand their diagnoses — no matter their abilities or background. We prioritised accessibility at every layer: users can interact via voice input, upload medical documents as PDFs, hear responses read aloud through text-to-speech, navigate with full screen reader support, and communicate in multiple languages. Paired with clean, patient-first UI design and technically innovative features that translate complex medical information into plain-language explanations, we built an inclusive, polished, and fully functional product entirely within the hackathon window.
The primary goal achieved during this hackaton was to find a solution that can enable us to reduce the health‑literacy challenges that prevent patients from fully understanding their diagnoses, lab results, and care instructions. By making medical information clearer and more accessible, we can empower patients to take an active role in their health, support clinicians by reducing unnecessary clarification visits, and ultimately improve outcomes across the system.
As a team our personal achievements were the ability to collaborate and come together, especially in the start and last hour when we were all stressed and pushing towards the deadline. It took us a while to get going with the idea (5 hours before we settled on an idea) but after we did we felt that the democratic approach meant we could all be happy with what we made .
What are the next steps for your project? How can you improve it?
ClariMED Phase 2:
To better serve diverse populations and individual patient needs within the UK, ClariMed is set to introduce additional output tones, including 'Friendly and Simple' for accessibility, 'Direct and Concise' for efficiency, and 'Detailed and Clinical' for deep context.Â
Additionally , ClariMed is rapidly adding extensive language support, ensuring critical health information is truly understandable for non-native speakers across the country.
We can also add more accessibility options for users such as enlarged text, and alternative fonts to make the information as easy to understand as possible.
ClariMED Phase 3:
ClariMED can integrate directly with NHS systems to provide patients with a user‑friendly, accessible interface for navigating the NHS Conditions A–Z and other approved medical libraries. This phase enables patients to access trusted clinical information in a simplified, easy‑to‑understand format, improving comprehension while reducing the burden on clinicians who currently spend time re‑explaining standard guidance.