HealthBridge

The company appears to be a hackathon project named HealthBridge, developed by a team of three individuals for the OpenAI 2026 hackathon. The project is described as a privacy-first tool that helps Filipinos prepare for healthcare conversations by comparing medicine packs, calculating price differences, and generating questions for pharmacists or care teams. It uses AI to organize user notes into practical questions but does not recommend switching medicines.

What changed: The description indicates this was built as a hackathon submission, with no evidence of prior development or commercial traction. The team states they used Next.js, React, TypeScript, and Tailwind CSS, along with GPT-5.6 for AI assistance in organizing notes.

The single most important open question: Is there any evidence of user adoption, revenue, or post-hackathon development beyond the initial prototype?

The description states that HealthBridge is a privacy-first care preparation tool for Filipino families. It helps users:

• Compare medicine packs only when ingredient, strength, form, and pack quantity match.
• Calculate savings from observed prices.
• Block unsafe comparisons when any matching field differs.
• Prepare questions for pharmacy, clinic, laboratory, and hospital discharge visits.
• Create a shareable and printable Care Relay handoff.
• Continue using the core experience with local demo data, even without API keys or camera access.

The system calculates price difference as:

$$

\Delta P = P_{\text{brand}} - P_{\text{alternative}}

$$

It presents this as evidence for discussion—not as a recommendation to switch medicines.

Inference: The product is described as a frontend application with local data handling and AI-assisted question generation, but no backend services or APIs are mentioned. It appears to be a prototype built for demonstration purposes.

The description states that HealthBridge was inspired by the author’s personal experience of needing to buy medicine for family members, where recognizing similar-looking medicines is difficult.

It positions itself as:

• A privacy-first tool.
• A preparation aid, not a decision-maker.
• An AI-assisted assistant for healthcare conversations, not a replacement for professionals.

The claim evolution shows a focus on user empowerment through information, rather than clinical guidance or product recommendation.

Inference: The positioning reflects an intent to avoid clinical advice while offering support in navigating pharmacy and care-team interactions. It emphasizes safety and clarity over automation.

The description states that HealthBridge is designed for Filipino families who need help preparing for healthcare conversations, particularly around medicine purchases and care team interactions.

It targets users who:

• Need to compare medicines.
• Want to prepare questions before visiting a pharmacist or clinic.
• Are concerned about safety in medicine selection.

There is no evidence of segmentation beyond this broad demographic.

Inference: The ICP appears to be health-conscious Filipino consumers, possibly with limited access to healthcare information or support, who seek clarity and confidence in their medication choices.

The description does not provide any information about:

• Revenue streams.
• Pricing models.
• Monetization strategy.
• Customer acquisition costs.
• Any commercial relationships or partnerships.

Not evidenced: No indication of how the project intends to generate value or sustain itself beyond its hackathon prototype.

The team built HealthBridge using:

• Next.js, React, TypeScript, Tailwind CSS
• GPT-5.6 for organizing user notes into questions
• Local storage and Web Speech API
• Codex for implementation assistance

Key technical features include:

• Deterministic medicine matching.
• Safety fallbacks (e.g., AI fallback to templates).
• Responsive UI for mobile devices.
• Automated tests and evaluation fixtures.

The system supports offline use with demo data, even without camera or API access.

Inference: The product is built as a frontend-only prototype with limited backend functionality. It uses AI primarily for organizing user input into structured questions, not for clinical decision-making.

There is no evidence of:

• Revenue.
• Customers.
• User adoption.
• Product usage metrics.
• Post-hackathon development or iteration.
• Any form of product launch or market entry.

The project was submitted to a hackathon and described as a prototype.

Not evidenced: No data on traction, growth, or user engagement beyond the initial build.

The description does not mention any competitors or similar tools in the market. It does not reference:

• Existing medicine comparison apps.
• Healthcare preparation tools.
• AI-powered question generators for medical contexts.

Not evidenced: No competitive analysis or positioning relative to other solutions.

• No commercial viability or monetization strategy is evident.
• The product is described as a hackathon prototype with no indication of further development.
• The use of AI raises concerns about safety and accuracy if not properly validated in real-world settings.
• The system relies on local data storage, which may limit scalability or long-term utility.
• The team size (3) and lack of prior traction suggest limited experience or resources for scaling.

Inference: Without a clear path to monetization or user adoption, the project is at high risk of remaining a prototype without real-world impact.

1. What is the intended long-term vision for HealthBridge beyond this hackathon submission?
2. Are there any plans to iterate on the product post-hackathon?
3. How will the team ensure that AI outputs remain non-clinical and safe?
4. Has the team considered legal or regulatory compliance in healthcare contexts?
5. What are the key assumptions about user behavior or adoption?
6. Is there any plan for integrating with existing healthcare systems or databases?