What to Build

We encourage participants to think outside the box, explore new possibilities, and push the boundaries of innovation to create tangible and impactful STI prevention and control/sexual health promoting technology-centered solutions. However, the solution should be implementable—that is, not something that cannot be achieved in the current landscape (think privacy laws, Health Insurance Portability and Accountability Act [HIPAA] compliance, etc.). To make sure your solution is implementable, you can follow a framework for quickly learning how to develop and refine your idea, such as the customer development process (link). STIs also impact different populations disproportionately, so keep health equity at the forefront.

Any idea in the area of STI prevention and control to improve sexual health that incorprotates the use of technology will fit for this competition! See the Resources tab for more inspiration.

Project Requirements

• What to Create: Entrants must create a working software application that helps prevent and control sexually transmitted infections (each a “Project”).
• Sponsor Prizes: Projects being submitted for the Sponsor Awards must also follow the specific requirements listed in section 8. Awards.
• Functionality: The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description.    
• Platforms: A submitted Project must run on the platform for which it is intended and which is specified in the Submission Requirements.
• New & Existing: Projects must be either newly created by Entrant or, if Entrant’s Project existed prior to the Hackathon Submission Period, must have been significantly modified after the start of the Hackathon Submission Period.
• Third Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them.

What to Submit

Submissions to the Hackathon must meet the following requirements:

• Include a Project that aims to help prevent and control sexually transmitted infections and meets the above Project Requirements.
• Include a text description that should explain the features and functionality of your Project.
• Include a demonstration video of your Project. The video portion of the Submission:
  • Should be less than three (3) minutes.
  • Should include footage that shows the Project functioning on the device for which it was built
  • Must be uploaded to and made publicly visible on YouTube, Vimeo, Facebook Video, or Youku, and a link to the video must be provided on the Submission form on the Hackathon Website; and
  • Must not include third party trademarks, or copyrighted music or other material unless Entrant has express written permission to use such material.
• Additional Document Presentation including the following:
  • Brief synopsis of your solution (max 600 words). Include key points to address judging criteria. The description should also cover the project's objectives and any obstacles encountered during development.
  • An explanation of the technical aspects, methodologies, and algorithms used in the solution (no word limit).
  • An explanation of why you are the right team to be building this solution, and a description of who (if any) other people you might need involved in the future to successfully implement this project (e.g., support from a technology administrator at the CDC to implement a solution into CDC technology frameworks).
• URL to a functional demo app OR URL to public code repository
  • Access to Your Prototype: Entrants must submit any relevant source code, design assets, or datasets necessary for the evaluation process. Provide necessary details for judges to access your solution, whether it's a test account or a website. Make sure the instructions are clear and straightforward and easy to access. Entrants  can use any format necessary to communicate the idea. 

Language Requirements

All Submission materials must be in English or, if not in English, Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted. 

For additional submission details (e.g., multiple submissions & testing), see the full rules and eligibility.