OpenAI 2026 hackathon

PatientDrive

Never forget what your doctor said

Solo project by Raju Yadav · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,856 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

PatientDrive is a self-reported multilingual health communication tool designed for doctor-patient consultations in South Asia, where conversations often switch between languages (e.g., Hindi, Nepali, English). It records consultations, transcribes them using Soniox STT, summarizes them into plain language with actionable next steps via OpenAI models, and allows patients to share summaries with family or caregivers. The app is built in React Native for mobile platforms.

What changed

The project was submitted as a hackathon entry (Devpost, OpenAI 2026) and claims to have completed an end-to-end patient journey: recording, summarizing, sharing, and preparing for the next visit — all within a multilingual context. It is not evidenced to be live or used beyond this prototype.

Single most important open question

Is there any evidence of real-world use, adoption, or traction by patients or healthcare providers? The description states no revenue, customers, or usage data are available.

Back to contents

What The Product Actually Is

The description states that PatientDrive is a mobile app that:

  • Records doctor-patient conversations.
  • Transcribes them using Soniox STT, which supports multilingual and code-switched speech.
  • Summarizes the conversation into plain-language next steps using OpenAI models.
  • Allows patients to share these summaries with family or caregivers.
  • Enables patients to prep for future visits by jotting down questions and receiving reminders.

It is built in React Native and designed for use in South Asia, where multilingual communication is common.

Evidence

  • The author states it uses Soniox for transcription.
  • It uses OpenAI models for summarization.
  • The app supports a full loop: record → summarize → share → prep.
  • It is built in React Native to support both iOS and Android.

Inference The product appears to be a prototype or proof-of-concept, not a commercial offering. No evidence of live deployment or user base is provided.

Back to contents

Positioning & Claim Evolution

The description states that PatientDrive was created to solve the problem of patients forgetting up to 80% of what doctors say — especially in multilingual settings like South Asia. It positions itself as a solution that works where existing tools fail, due to its support for code-switched speech.

Claims made

  • Patients forget up to 80% of what doctors say.
  • Existing tools only work for English-speaking patients.
  • The app handles multilingual and code-switched conversations in real-world settings.
  • It is built with a full patient journey in mind, not just transcription or summarization.

Evidence

  • The author claims that current solutions assume single-language, English-speaking patients.
  • The product is described as handling “Hindi, Nepali, and English” within one conversation.
  • It was built to support the full loop of recording, summarizing, sharing, and preparing for next visits.

Inference The positioning reflects a niche market need — multilingual healthcare communication in South Asia. However, no evidence is provided that this problem has been validated beyond the hackathon context.

Back to contents

Target Customer & ICP

The description states that PatientDrive targets patients in South Asia (e.g., India and Nepal) who experience doctor visits involving multiple languages, including Hindi, Nepali, and English — often within the same sentence. These patients are described as those who “miss follow-through” due to memory issues.

Claims made

  • The app is built for multilingual, code-switched healthcare settings.
  • It addresses a problem common in South Asia.
  • Patients often forget what doctors say, especially when language switches occur.

Evidence

  • The author states that doctor-patient conversations in South Asia routinely move between languages.
  • It is designed to help patients who “miss follow-through” due to memory issues.
  • The app supports Hindi, Nepali, and English.

Inference The ICP appears to be patients in multilingual South Asian countries, but no evidence of actual users or customer validation is provided.

Back to contents

Business Model & Pricing Evidence

There is no evidence in the description of a business model or pricing structure. The project is described as a hackathon submission and not as a commercial product.

Evidence

  • No mention of monetization.
  • No pricing, subscription plans, or revenue streams are discussed.
  • The app is described as a prototype built for a hackathon.

Inference The business model remains unknown. It is unclear if the team intends to charge users, offer it to healthcare providers, or pursue other monetization strategies.

Back to contents

Technical & Delivery Signals

The description states that PatientDrive uses:

  • Soniox for transcription.
  • OpenAI models for summarization.
  • React Native for mobile app development.
  • A full end-to-end patient journey: recording → summarizing → sharing → preparing for next visit.

Evidence

  • The team used Soniox for multilingual speech recognition.
  • OpenAI models were used to generate summaries in plain language.
  • The app is built in React Native and supports both iOS and Android.
  • It includes a full loop of features, not just transcription or summarization.

Inference The technical stack appears functional for the described use case. However, no evidence of production deployment or scalability is provided.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, adoption, or user data in the description. The project is described as a hackathon submission with no indication of real-world usage or customer feedback.

Evidence

  • The product was submitted to the OpenAI 2026 hackathon.
  • No mention of users, customers, or real-world testing beyond the prototype.
  • No revenue, ARR, or headcount data is provided.

Inference The project is at a very early stage — likely a prototype or proof-of-concept. No evidence of product-market fit or user traction exists.

Back to contents

Competitive Context

There is no mention of competitors in the description. The author states that existing tools only work for English-speaking patients and do not handle multilingual or code-switched speech, but does not name any specific products or companies.

Evidence

  • The author claims that current solutions assume a single-language, English-speaking patient.
  • No competitor names or market analysis are provided.

Inference The competitive landscape is unknown. It is unclear if there are existing tools in this space or how PatientDrive would differentiate from them.

Back to contents

Key Risks & Red Flags

  • No traction or user data: The project is described as a hackathon prototype with no evidence of real-world use.
  • Unproven market need: While the problem is claimed, no validation of customer demand or adoption is provided.
  • Technical feasibility concerns: Multilingual code-switched speech recognition is challenging. No evidence that Soniox and OpenAI models are sufficient at scale.
  • No business model: No indication of how PatientDrive will generate revenue or sustain itself.

Inference The project lacks commercial viability indicators. It may be a promising idea, but it has not been tested in the market.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific multilingual use cases have you tested with real patients?
  2. How do you plan to validate the accuracy of summaries generated by OpenAI models?
  3. Have you conducted any user research or interviews with patients or healthcare providers?
  4. Is there a plan for monetization or scaling beyond the hackathon prototype?
  5. What are the technical limitations of Soniox and OpenAI in handling real-world multilingual conversations at scale?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The project is described as a hackathon submission with no evidence of traction, revenue, customers, or commercial viability. It is not clear whether it has moved beyond the prototype stage or if there is any intention to build a sustainable product.

Confidence level Low This analysis is based entirely on self-reported information and lacks any independent verification or data on users, revenue, or performance.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.