The HORNET Center for Autonomic Nerve Recording and Stimulation Systems (CARSS) consists of five distinct NEST Projects responsible for development of the implantable pulse generator (IPG), external charger and controller (NEST 1-2), and selection of interoperable and implantable leads for stimulation and sensing (NEST 3-5). The final goal is to realize a fully functional integrated system with interoperable leads that will be community-supported technology platform. The Technology Integration and Dissemination (TID) Core will support this goal by facilitating the interconnection between the NEST Projects to realize a logical integration plan. NEST 1-2 and NEST 3-5 will run in parallel and achieve module level testing before beginning system integration. Then NEST 1-2 will result in a fully integrated IPG with external charger and controller. Final integration will involve testing different leads and lead configurations with the IPG system. The TID Core will also spearhead the Center’s multi-pronged approach to achieve broad dissemination of CARSS technology. The Center will also employ a collaborative approach, working with other HORNET Centers to facilitate dissemination. CARSS will share content different venues and formats including a newsletter, social media posts (LinkedIn), articles (include special issue contributions), reports, presentations (at meetings, conferences, and seminars), short courses (including recorded and downloadable training modules and tutorials), and on-site training events. The Center will maintain a website, wiki, and online repositories, each providing access to different types of users and addressing different user needs. CARSS will also coordinate with the SPARC Data and Resource Center to share developed materials. The open-source license strategy will allow open collaboration, facilitating derivative hardware and software products.

Not applicable per solicitation. Project Narrative: Do not complete. Note: ASSIST screens will show an asterisk for this attachment indicating it is required. However, eRAsystems only enforce this requirement in the Overall component and applications will not receive an error if omitted in other components.