.png)
APPLY TO SPEAK AT NEXUS 2026
Digital-Native Care Activation: Share Your Transformation Story
The infrastructure is built. The teams are trained. The evidence is clear. NEXUS 2026 is where healthcare leaders flip the switch on digital-native care delivery—and we want your activation story to power the transformation.
This isn't about future possibilities or incremental improvements. This is about live implementations, proven results, and ready-to-scale solutions that are transforming healthcare delivery right now
Submission Deadline for Priority Consideration: October 3, 2025
Submissions received by this date will be given first-round consideration. Rolling acceptance will continue after October 3, with priority given to early submissions.
Questions? Contact DeAnna Grosbaum, Vice President of Content & Programming, at dgrosbaum@americantelemed.org.
What We ARE Looking For:
- Live implementations with measurable ROI - systems that are operational and delivering results
- "How we built it" playbooks - step-by-step frameworks others can replicate immediately
- Health system-led transformation stories - real organizations sharing honest lessons learned
- Ready-to-scale solutions - proven models moving from pilot to enterprise deployment
- Clinical evidence and safety data - outcomes that prove quality and effectiveness
- Multi-stakeholder collaboration - partnerships between providers, payers, and technology
- Digital-native workforce models - teams and training approaches that actually work
- Sustainable financial frameworks - business cases that CFOs approved and funded
- Policy wins and advocacy success - regulatory changes that enabled transformation
- Interactive problem-solving sessions - workshops that produce tools attendees take home
What We're NOT Looking For:
- Product demos without customer implementation stories
- "Future vision" presentations without current deployment
- Vendor-only panels without health system perspectives
- Case studies from 2020-2022 (we've moved beyond pandemic response)
- Research without clear implementation pathways