Preventive Medicine Application

The description states that Preventr is a responsive web application built with React 19, TypeScript, and Next-compatible Vinext app router. It uses Supabase for authentication and persistence, PostgreSQL for data storage, and GPT-5.6 via Codex to assist in development.

It allows users to complete a five-section assessment covering:

• Cardiometabolic health
• Movement
• Nutrition
• Sleep
• Substance exposure
• Cancer screening
• Immunizations

The system outputs:

• One Core Action Score and seven health-area scores
• A completeness measure
• Point-by-point explanations of score deductions
• Ranked plan showing three most valuable next steps
• Searchable health data and unit-safe trends
• Personalized average-risk screening guidance
• An AI Health Companion (designed to explain context without diagnosing or prescribing)

The public demo works without an account or personal health information.

Inference This is a self-contained, web-based tool for individuals to assess their own health using structured inputs and AI-assisted interpretation. It is not described as integrating with EHRs or real-time lab systems at this stage.

The author positions Preventr as a preventive medicine platform aimed at making preventive care more accessible by turning fragmented health data into an actionable score and plan.

Key claims:

• Preventr turns health data into an “actionable health score” with a personalized prevention plan.
• The score is based on genetics, physiology, and resources.
• Users can understand why their score is what it is and what to do next.
• It provides guidance across lab results, lifestyle habits, screening schedules, and vaccine history.

Inference The positioning reflects an intent to democratize preventive medicine through digital tools. However, the description does not indicate any shift from a prototype or demo toward a scalable product or service offering.

The description states that Preventr targets everyone, aiming to make preventive medicine accessible to all users regardless of their current health status or access level.

It includes:

• Individuals completing assessments
• Users who want clarity on why their score is what it is
• People seeking a ranked plan showing the three most valuable next steps

There is no mention of specific customer segments beyond general consumers, nor any indication that the product is tailored to particular demographics, conditions, or healthcare providers.

Inference The ICP appears to be broad — individuals interested in self-assessing their health and receiving personalized recommendations. No clear segmentation into high-value or niche markets is evident.

There is no evidence of pricing tiers, monetization strategies, or business model details in the description.

The author mentions:

• Free and Plus tiers use the same score
• Missing information is not silently imputed
• Urgent safety information is never paywalled
• Future capabilities are never presented as live

Inference While there is a reference to “free” and “plus” tiers, no actual pricing structure or revenue model is described. The business model remains undefined.

The application is built using:

• Frontend: React 19, TypeScript, Next.js-compatible Vinext app router
• Backend: Supabase (authentication and persistence), PostgreSQL with Row Level Security
• AI Tools: GPT-5.6 via Codex for development assistance
• Deployment: Cloudflare through OpenAI Sites

Key technical features:

• Deterministic scoring engine written in TypeScript
• Rules are versioned, testable, and independent from AI
• Score deductions traceable from current value to target, available points, explanation, next action, and evidence source
• Server-controlled GPT context boundary with explicit medical-safety limits
• No-login path for judges to explore the product using demo data

Inference The technical stack suggests a modern, scalable architecture. The use of deterministic scoring implies a focus on reproducibility and transparency over AI-driven inference in core logic.

There is no evidence of revenue, customers, or adoption beyond the author’s own demonstration.

The description states:

• Public demo works without an account
• No login required for judges to explore the product
• The scoring system is still in the beginning and requires further validation
• It was submitted as a hackathon project

Inference This is a prototype or proof-of-concept, not a mature product with traction or market adoption.

The description does not reference any competitors or existing solutions in the preventive medicine or health scoring space.

There is no mention of:

• Similar platforms
• Market positioning relative to others
• Differentiation from existing tools

Inference No competitive context is provided. The author does not describe how Preventr compares to other health apps, wearables, or digital therapeutics.

1. Lack of clinical validation: The scoring engine requires further validation before being used in real-world healthcare.
2. AI dependency for core functionality: While the scoring is deterministic, AI is used primarily for interpretation and workflow layering — raising questions about how much of the system relies on unverified AI outputs.
3. No monetization strategy: No pricing or business model described.
4. Unproven safety boundaries: The AI companion requires training and API costs; it's currently only an example.
5. Hackathon origin: Submitted as a hackathon project, suggesting early-stage development with limited testing or production readiness.

Inference The product is in a very early stage of development and lacks any commercial or clinical validation. Risks include regulatory uncertainty, safety concerns, and unclear path to monetization.

1. What clinical validation has been performed on the scoring engine?
2. How will Preventr ensure data privacy and consent compliance in a real-world setting?
3. Is there any plan for integrating with EHRs or lab systems?
4. What are the actual costs associated with running the AI companion, and how does that factor into pricing?
5. Are there any plans to test the scoring system with real users outside of the demo environment?
6. How will Preventr handle edge cases like missing data or conflicting health indicators?
7. Has the team considered regulatory requirements (e.g., FDA, HIPAA) for a product that interprets health data?