Our sixth episode is all about ISCoS! Dr Jennifer Coker takes the host's seat once more to chat with Daniel Graves, Editor-in-Chief of Spinal Cord and Spinal Cord Series and Cases, the official journals of ISCoS, and chair of the ISCoS Education Committee, Stephen Muldoon.
Join them as they discuss their own history with ISCoS, when and why they became members, their roles within the society today and what you can expect at this year’s 60th Anniversary Scientific Meeting, from the programme to the virtual networking opportunities. They discuss the beginnings of ISCoS, the evolution of the society, and the new strategies and innovations which will take this society and its members into the future, connecting with a global community.
Thank you for listening.
If you have any questions or suggestions for future episodes or would like information on becoming an ISCoS member, please email firstname.lastname@example.org. If you would like to register for the 60th Anniversary Annual Scientific Meeting this September, click here.
*The opinions of our host and guests are their own.--- Send in a voice message: https://anchor.fm/scicare/message
The opinions of our host and guests are their own; ISCoS does not endorse any individual viewpoints, given products or companies.
If you enjoyed this podcast, please rate, review and subscribe with the podcast provider of your choice.
The SCI Care: What really Matters podcast aims to provide valuable insights and the most up-to-date information for those providing care to people with spinal cord injury (SCI) worldwide. The vision of the International Spinal Cord Society (ISCoS) is to "facilitate healthy and inclusive lives for people with spinal cord injury or dysfunction globally".
Partnership and collaboration are key to achieving this vision. Our episodes include expert guests, persons with lived experience and representatives from the industry supporting SCI care.
We invite you to SAVE the DATE.
ISCoS 2024 will take place in Antwerp, Belgium 22 - 25 September 2024
Contact us directly with any questions or comments at email@example.com