There are currently no news articles for this region. View all Medsin news here.
There are currently no upcoming events for this region. View all Medsin events here.
Whilst most medsin members will know about how Branches, Activities and National Working Groups can work on a local and national level, can the same be said about Regions? Here is a brief round up of what regions are, the potential that they hold and what ...read more
Posted by: Nathan Cantley
Roles of the Midlands Regional Co-ordinators: Hi! We are Haresh and Karthick, regional co-ordinators (RCs) for Medsin Midlands 2012- 2013. RCs act as a bridge of communication between the national committee and the local branches. As the director of ...read more
Posted by: Karthickkumar Selvakumar
This week our branch of the week is Nottingham. Branch president Hunain talks about what they've been doing this year, and how they've found allies in other student groups. _________________________________________________ Medsin at ...read more
Posted by: Cameron Stocks
Midlands regional coordinator - Karthickkumar Selvakumar
Hi! We are Haresh and Karthick, regional co-ordinators (RCs) for Medsin Midlands 2012- 2013. RCs act as a bridge of communication between the national committee and the local branches. As the director of branch affairs in the national committee may be working hard on sorting out individual issues that may be occurring at branches across the UK, it’s our role as RCs offer help and follow up the branches and their activities to give a lending hand. There are 6 Medsin branches you will working with as a Midlands RC: Birmingham, Leicester, Warwick, Keele, Nottingham and Oxford. Working with each branch has inspired me and given me a chance to meet new people with a great passion for international health see how much they want to make a change.
If you need any help/ questions about anything at all, please contact us on midlandscoordinator@medsin.
Karthick and Haresh
If you are interested in finding out more about the region please contact me at email@example.com