WHAT TO BUILD

Entrants should aim to create digital, scalable solutions that improve patient care while also potentially accelerating clinical research, examples include but are not limited to consented data for observational research, or a warm base of patients for clinical trial recruitment. Entrants can either submit a project to Track 1 or Track 2.  More examples of types of apps and digital solutions are available on the Tracks link.

WHAT TO SUBMIT (SEE OFFICIAL RULES FOR MORE DETAIL)

 URL to the Working Project. Include a URL to your Project, e.g. to a website, functioning demo, or test build. Judges will need access to demo your app or project (e.g. login credentials in testing instructions). Source code is not required but may be included (e.g. URL link to GitHub repository) as additional support for Technical Implementation judging criteria. Judges must be provided with a way to interactively test the submission.  See the official rules for more details for mobile app submissions.

Submission Track.  Clearly identify either Track 1 or Track 2.

Entrant Category: Clearly identify the submission as Non-Commercial Enthusiast (e.g. new to the field, experimenting, learning, not commercially-available at time of submission) or Commercial (e.g. companies who have a commercially-available product offering).

 Demo Video. Include a URL to a video (about 3 minutes) that demonstrates your app and explains how it is useful. If applicable, the video should show the project functioning on the device for which it was built.  Videos must be uploaded to YouTube or Vimeo and made public, but may be an unlisted URL.  Please include your team name/identifier, track, and entrant category.  Additional video over 3 minutes may be included, but may not be reviewed by judges.

 Written Description. Provide a summary of your app, explain the features and functionality, why someone would find it useful, and how it includes modeled consent for recontact.

Slide Deck. Include a slide set that explains your Project in detail, ideally 10 slides or less. More slides may be included, but may not be reviewed by judges.  The preferred file format is PDF.  The slides should focus on how the entry satisfies the judging criteria and aims of the challenge (e.g. how the solution is original and creative, how it is useful and will have potential impact, and how it demonstrates technical readiness).  The slide deck should be 10 slides or less.

 Your complete submission form on Devpost before the final deadline.

SUBMISSION MODIFICATIONS

Entrants may save draft versions on Devpost on your portfolio before submitting for evaluation.  But once the submission period has ended, entrants may not make any changes or alterations to the submission, but may continue to update the project in the Devpost portfolio.

EARLY SUBMITTER BONUS

Awarded to up to 10 eligible Projects that are submitted early.  These projects may be updated before the final deadline, but must include a PDF/Slide Deck summarizing the entry by April 24.

RESUBMISSIONS ARE ALLOWED FROM PRIOR CHALLENGES, HACKATHONS

Entrants are allowed to submit their own creations from prior challenges, hackathons or other efforts, if they are authorized and have permission to do so.  An entrant may submit more than one submission, but each must be unique and substantially different from each of the entrant's other submissions.

BE HELPFUL AND COOPERATIVE WITH EACH OTHER

Although not a requirement for submission, participants and community members may also receive prizes for how active and helpful they were as a community contributor, e.g. in online discussions or other ways of helping the entire field of entrants and participants.  See "Most Helpful Community Members" prize for more details.