MediThon

Submission Requirements

1. Mandatory Deliverables

Each team must submit a working, functional prototype that the jury can interact with during evaluation.

• A PPT, video, or architecture diagram may be used to support your explanation, but cannot replace a working demo.

During your pitch or demo, you should clearly explain:

• What works end-to-end
• The frontend, backend, and any integrations (if applicable)
• Data sources, references, or databases used
  • Best practice: use public or synthetic data wherever possible
  • Avoid uploading or using any confidential or proprietary data in prompts, logs, screenshots, demos, or submissions
• Key assumptions, constraints, or known limitations of your solution

2. Tooling Policy

• There are no restrictions on the technology stack or tools used
• Teams are encouraged to use AI-assisted development and rapid prototyping tools to build faster
• Teams must be transparent and mention which tools were used and where (e.g., UI generation, API wiring, workflow automation, debugging)

3. Submission Readiness

To ensure smooth evaluation, teams are strongly encouraged to be prepared with:

• A hosted URL or a clearly runnable local build
• Simple setup or run instructions (README-level)
• API keys configured safely using environment variables (no hardcoding)
• Test credentials or sample data required for evaluation
• A short “How to Evaluate” checklist outlining what the jury should click through or test