Judging & Prizes
For more info on team formation, judging criteria, prizes, and additional details, please read below.
Teams can have a minimum of 1 person and maximum of 6 people. Teams can be formed prior to the event, but no designing, coding, or making is allowed until the event begins (more below). However, feel free to research and get inspired!
Projects ideas can be a service, app, website, or any combination of the above. Teams can pitch their solution by demoing on a computer screen or by sharing whichever type of prototype has been created.
Each team will have 2 minutes to pitch their solution to the judges. There will be at most 1 minute of Q&A.
SUBMITTING YOUR WORK
Coding begins on Saturday, March 23 at 11am and concludes on Sunday, March 24 at 12pm.
All projects must be submitted on our devpost by 12pm on Sunday, March 24 to be eligible for consideration.
PRIZES & CHALLENGES
First Place: Free Annual Sleepio Subscriptions, HMH blog post feature, Meal with HMH team, Connect with Judges
Second Place: HMH blog post feature, Meal With HMH team, Connect with Judges
Third Place: HMH blog post feature, Connect with Judges
Sponsor Challenges & Prizes
To compete in sponsor challenges, please check the corresponding selection from the list of prizes when submitting your hack on our devpost.
Collective Health Challenge: Hacking access to behavioral health care: navigating and paying for care. Prize: $200 Marlowe gift card for your team dinner
HopeLab Challenge: Hacking a solution to address social isolation in young people. Prize: Meet with Hopelab CEO and Director of Research for further development
Joyable Challenge: Hacking a solution to provide more integrated options for those in need of crisis support. Prize: Lunch with the Joyable VP Engineering and other product team members
Judging for projects will take place, with the following 4 criteria. Each factor will be scored out of 1-5 points for a potential perfect score of 20/20.
(1) Clinical Impact: The product/service can meaningfully address a current clinical problem.
Is this product/service able to benefit a clinical issue or sub-issue? What is the scope and degree of impact upon the clinical problem that product/service addresses?
(2) Viability: The product/service serves a function in the healthcare landscape.
How will the product fit into the healthcare system, current technologies, and the political landscape? Does it create a new solution / take a new perspective to a current problem? Or, does it improve upon existing technologies and solutions? What is the business case for the product?
(3) Technical Quality: The technical requirements for the product are feasible, innovative and elegant.
How well-developed is the technology behind the current prototype? Did the team build out their hack using code rather than prototyping design? Is the product technically feasible to develop and deliver? How innovative is the technology?
(4) Product Excellence: The product/service has thought about the end user in its design.
How well did the group think about the user interface (UI) and user experience (UX)? How creative and unique is the solution? Is the solution delightful to use?
All hackathon participants own full rights to their work.
TIME AND PLACE OF WORK
Work may be done on or off site. We encourage you to be at the event while the venue is open, but you are free to work outside of operating hours of the venue. Please remember to sleep.
All work on your team must be your own.
Your team must be present at the event to submit and present your work. Teams not present will forfeit any winnings and their prizes will be awarded to another team.