Questioning my own SEND vocabulary

This week’s reflections explore how the words we use, like “dataset” and “conversion”, can shape our understanding of SEND, sometimes in misleading ways.

This week I’ve been thinking about some of the verbiage that we use to describe how we work with SEND. I’m worried that sometimes this may be misleading, misused or misunderstood.

An obvious example that springs to my mind is the use of the word ‘dataset’. The correct use of this term in the context of SEND is to describe a single xpt file of data. However, the word is often misused to describe the entire SEND package, which itself could contain 20 or 30 datasets, plus the define.xml and nonclinical study data reviewer’s guide.

Another word which causes me some discomfort in the context of SEND, is ‘converting’ as in ‘converting the study data to SEND’. I must admit that I try to avoid this and instead I try to use the phrase ‘representing the study data in SEND’.  The data are not converted. They are the same data whether they are shown on a PDF table in the appendices of study report, or if they are shown in a SEND xpt file. These are just 2 different representations of the same data. To me the most accurate description would be ‘to render data in SEND’, however this is not a phrase I’ve heard anyone else ever use.

I am fully aware that I’m likely being overly fussy here. While I strive for a level of accuracy in how I describe the way we work with SEND, I understand that language evolves, and I am a strong believer in the idea that language is correct by usage. So, I accept that most people understand and are comfortable with the phrase ‘converting data to SEND’. And so, from time to time I find myself using it too.

This week was one of those times as I’ve largely been focused on discussing the comprehensive range of services we are offering regarding SEND. Like other organizations that offer services around SEND, our mainstay has always been our ability to ‘convert data to SEND’. That term has become a useful shorthand to describe our main service. So, despite my reservations with the term, I’ve found myself using it quite a lot this week with the various industry presentations I have been involved with.

So, yes, spending a week talking about the services we offer has got me questioning the vocabulary we use to describe the work.

‘till next time

Marc

Marc Ellison

Marc Ellison is the Director of SEND Solutions at Instem and has been a CDISC volunteer for 12 years. He has 3 decades of experience creating nonclinical software and working with researchers on how to best collect and organize their data. Marc refers to himself as a “SEND nerd” and is truly passionate about the concepts, debates, and evolutions around the SEND standard. Being a strong advocate for the importance of SEND in accelerating research, Marc launched his own educational blog at Instem called “Sensible SEND” to help educate and prepare researchers with cutting-edge details and explanations about the ever-developing process.

Share This Article

Stay up to Date

Get expert tips, industry news, and fresh content delivered to your inbox.

Request a Demo Today

Unsure which product to choose? Select ‘other’ from the form and let us know your research aims in the message field and our experts will recommend a solution for you.