eOSCE

The description states that eOSCE is a platform designed to deliver an online, structured clinical examination experience for medical residents preparing for the Objective Structured Clinical Examination (OSCE). It is self-reported as being built by one individual developer, Ahmed AlFayaa, MD, using technologies such as Next.js, LiveKit, and Cloudflare Workers. The author claims the platform supports five user roles—administrators, examiners, participants, standardized patients, and observers—and aims to replicate in-person OSCEs virtually.

The project is positioned as solving a problem of accessibility and cost for medical residents seeking practice exams, but there is no evidence of actual users, revenue, or traction beyond preliminary discussions with a college assistant. The platform appears to be in early development, with technical challenges noted around user experience and scheduling delays.

The description states that eOSCE is a platform designed to deliver an online, structured clinical examination experience for medical residents preparing for the OSCE. It supports five user roles:

• Administrators
• Examiners
• Participants
• Standardized Patients (SPs)
• Observers

It is described as enabling station-based examinations with automated timers, voice prompts, and seamless transitions between stations.

The platform is built using:

• Next.js
• TanStack Query
• Better Auth
• LiveKit (for WebRTC)
• Cloudflare Workers via OpenNext
• Hyperdrive
• Durable Object scheduler

It is claimed to be a virtual replacement for in-person OSCEs, allowing users to participate from anywhere.

Inference The platform appears to be an online simulation tool for medical training, not a commercial product with revenue or customers yet.

The description states that eOSCE was inspired by the author's personal experience during board certification in Preventive Medicine. It is positioned as solving the problem of difficulty organizing in-person mock OSCEs due to cost and logistics.

The author claims:

• The platform delivers a complete, structured clinical examination experience entirely online.
• It allows residents to practice communication, clinical reasoning, and history-taking under time pressure.
• It aims to make regular practice accessible by removing venue and coordination requirements.

There is no indication of how the product evolved from an idea to its current form beyond self-reported development using AI tools like ChatGPT. The positioning is focused on accessibility and simulation for medical trainees.

Inference The positioning reflects a personal solution to a niche problem, not a market-driven evolution or validated demand.

The description states that eOSCE targets:

• Medical residents preparing for OSCEs
• Specifically, those in Preventive Medicine (initially)
• Potential future users: other medical boards, med schools, and non-medical professions requiring simulation exams

It is claimed that the platform is designed to be simple enough for anyone to use, regardless of technical ability.

Inference The ICP appears to be early-stage medical trainees in a specific specialty (Preventive Medicine), with potential expansion into broader medical education or other sectors. No evidence of actual customers or user base.

The description does not state any business model or pricing information. It is self-reported that the platform is being considered for soft-launch to prepare residents for an upcoming exam, but there is no mention of monetization, subscription tiers, or fees.

Inference No evidence of a defined business model or pricing strategy exists in the provided description.

The description states that eOSCE was built using:

• Next.js
• TanStack Query
• Better Auth
• LiveKit (for WebRTC)
• Cloudflare Workers via OpenNext
• Hyperdrive
• Durable Object scheduler

It is claimed that the platform uses AI to provide voice prompts and help during exams, although this feature is not yet built in.

Challenges noted include:

• A non-clicky user journey for less technical users
• Delays in scheduling and rotation start times

Inference The platform is technically complex but appears to be in early development with known UX issues. No evidence of production deployment or scalability.

The description states:

• Talks are underway with a college assistant who wants to soft-launch the platform.
• Planning for an October launch, a couple of months before the actual exam set date.
• The project was submitted to the OpenAI 2026 hackathon on Devpost.

There is no evidence of:

• Actual users or participants
• Revenue or monetization
• Customer feedback or adoption metrics

Inference The platform is in early development with limited traction. No evidence of real-world usage or market validation.

The description does not mention any competitors or existing solutions in the OSCE simulation space. It only states that organized mock OSCEs exist but are expensive and offered by a few organizations.

Inference No competitive landscape is described, nor is there evidence of prior market analysis or differentiation from existing tools.

• No traction or revenue: The platform has not yet launched or demonstrated usage.
• Single founder: The project is built and maintained by one person (Ahmed AlFayaa, MD).
• Unproven scalability: Technical challenges with scheduling and user experience suggest early-stage development.
• Lack of business model clarity: No pricing or monetization strategy is described.
• No third-party validation: The only evidence of interest comes from a single college assistant.

Inference The project lacks commercial viability indicators, and the author’s claims about product-market fit are unverified.

1. What specific feedback have you received from the college assistant who is interested in soft-launching?
2. How do you plan to scale beyond a single specialty (Preventive Medicine)?
3. What is your strategy for monetization and customer acquisition?
4. Are there any technical limitations or scalability concerns that could impact the platform’s performance during high-usage periods?
5. Have you identified any regulatory or compliance requirements specific to medical simulation platforms?