Identify clinical needs
Teams work with healthcare professionals to uncover real, unmet needs in the clinical setting.
Programme
Sling Health runs one programme, on one national calendar, in every chapter. A clinical need goes in at the top. What comes out the other end is a working prototype, a team that knows how to build, and sometimes a company.
The lifecycle
Every chapter runs the same arc. It is deliberately short — a team that cannot get to something real inside a cycle learns that early, which is itself the point.
Teams work with healthcare professionals to uncover real, unmet needs in the clinical setting.
From sketches to functional prototypes, students build medical technologies using design thinking and rapid iteration.
Teams receive feedback from clinicians, researchers and investors to refine usability, feasibility and impact.
On Demo Day, teams present their ventures to a live audience, gaining visibility, funding opportunities and potential partnerships.
The three experiences
01 Problem Day
The origin point of every Sling Health project. Clinicians bring the things that are harder than they should be. Students bring the disciplines to attack them. Teams form in the room.
02 Design Reviews
Every team stands in front of a panel and defends the work. Clinical reality, technical feasibility, regulatory path, commercial logic. What survives goes to Demo Day.
03 Demo Day
The annual showcase. Chapter pitch competitions feed a national stage, where teams present what they built to clinicians, faculty, sponsors and investors.
Who is on a team
Sling Health teams are interdisciplinary by construction. A team without a clinician does not understand the need. A team without an engineer cannot build. A team without someone thinking about cost, evidence and adoption ends the cycle with a demo and nothing else.