BreakAI

BreakAI is a simulated clinical reasoning platform for medical learners, built as a full-stack application using React, FastAPI, and Supabase. The platform allows educators to create anonymized clinical cases and define authoritative answer keys, which are then used to generate AI-assisted "Clinical Pressure" scenarios that learners must evaluate for trustworthiness. The system is designed exclusively for educational use, not real patient care.

The description states that BreakAI was built by one team member (Pongkhun Siwalaiphong) and submitted to the OpenAI 2026 hackathon. No evidence of revenue, customers, or traction is provided. The platform's core functionality centers on preserving educator authority in defining clinical truth while using AI to simulate realistic reasoning pressures.

The description states that BreakAI is a "simulated clinical reasoning platform for medical learners." It functions as a full-stack educational platform where:

• Educators create fictional or anonymized clinical cases
• AI converts these into realistic "Clinical Pressure" scenarios
• Learners assess whether the presented reasoning should be trusted or untrusted
• The system supports both trustworthy and flawed reasoning scenarios
• Learners construct differential diagnoses and management plans
• Feedback includes qualitative debriefs linked to educator-defined priorities

The platform separates three layers:

1. Educator-authored clinical truth (case, diagnosis, management)
2. Educator-approved reasoning patterns (reliable or flawed scenarios)
3. Learner-facing AI facilitation (realistic clinical-pressure language)

The system uses React/TypeScript frontend with FastAPI backend and Supabase for authentication/data storage.

The description states that BreakAI was developed to provide a "safe environment in which learners can practise judgment" about clinical recommendations. The platform's governing principle is: "the educator defines the medical truth, AI facilitates the learning challenge, and the learner retains responsibility for independent clinical reasoning."

Key claims include:

• It helps learners determine whether underlying reasoning is clinically sound
• It teaches learners to assess quality of reasoning, recognize cognitive bias, and identify when clarification or escalation is appropriate
• It is designed exclusively for simulated medical education, not real patient care
• The system preserves educator authority throughout the learning workflow

The platform positions itself as a tool for developing critical thinking skills in clinical decision-making rather than simply delivering content.

The description states that BreakAI targets "medical learners" and is designed for "simulated medical education." It specifically mentions:

• Clinical trainees encountering AI recommendations, protocols, and senior authority
• Medical students who need to practice analytical reasoning
• Educators who create clinical cases and define answer keys

The platform appears to be aimed at medical education institutions or individual educators who want to teach clinical reasoning skills. The description does not indicate whether it targets specific training levels (e.g., undergraduate vs. residency) or specialties.

Not evidenced. The description provides no information about pricing, revenue streams, monetization strategy, or business model. It only describes the educational platform's functionality and design principles.

The description states that BreakAI was built as a full-stack clinical education platform using:

• Frontend: React, TypeScript, Vite, Material UI, Zustand
• Backend: FastAPI, Pydantic
• Database: PostgreSQL with Supabase authentication
• Testing: pytest, testing-library, vitest

Key technical elements mentioned include:

• Role-based access controls
• Schema validation
• Deterministic fallbacks
• Session-state controls
• Automated frontend and backend tests
• Safeguards against answer leakage
• Protected educator and learner routes
• Resumable sessions and controlled workflow progression

The system is described as separating three distinct layers: educator-authored truth, approved reasoning patterns, and AI facilitation that cannot alter the educator's answer key.

Not evidenced. The description provides no evidence of:

• Revenue or customers
• User adoption rates
• Educational institution partnerships
• Usage metrics
• Product maturity beyond initial development
• Market traction or user feedback

The project is described as having been built for a hackathon, with no indication of post-hackathon development or deployment.

Not evidenced. The description provides no information about:

• Direct competitors in medical education platforms
• Similar tools in clinical reasoning training
• Market positioning relative to existing solutions
• Competitive advantages or differentiators

The description states several potential risks and red flags:

1. Educational effectiveness: No evidence that the platform has been tested with real learners or educators, nor whether it achieves measurable improvements in clinical reasoning skills.

1. Scalability concerns: The platform was built by a single team member (Pongkhun Siwalaiphong), raising questions about development capacity and long-term maintenance.

1. AI governance challenges: The description notes that the principal challenge was establishing "appropriate clinical governance around" AI-generated content, suggesting potential risks in maintaining educational quality.

1. Limited validation: The platform is described as being in early stages with planned future work including "structured review with experienced clinical educators" and "validation of the educational workflow."

1. No commercialization strategy: No evidence of any business model or monetization approach beyond its hackathon submission.

1. What specific clinical reasoning skills are you measuring, and how do you plan to validate that learners improve through using BreakAI?

1. How will you ensure consistent quality control across different educators creating cases and scenarios?

1. What is your roadmap for moving beyond the hackathon prototype to a production-ready platform?

1. Have you conducted any pilot testing with actual medical students or educators?

1. What are the specific technical challenges you've encountered in maintaining educator authority while using AI?

1. How do you plan to scale from one developer to support broader educational institutions?

1. What metrics will you use to evaluate the effectiveness of your qualitative debrief system?

1. How do you intend to address potential bias in how educators define "correct" clinical reasoning?

1. What is your timeline for conducting the structured review with experienced clinical educators?

1. How do you plan to integrate with existing medical education curricula or platforms?