Do people from the Jewish community prefer ancestry-based or pan-ethnic expanded carrier screening?

Kim C. A. Holtkamp*, Merel C. van Maarle, Maria J. E. Schouten, Wybo J. Dondorp, Phillis Lakeman, Lidewij Henneman

*Corresponding author for this work

Research output: Contribution to journalArticleAcademicpeer-review

Abstract

Ancestry-based carrier screening in the Ashkenazi Jewish population entails screening for specific autosomal recessive founder mutations, which are rarer among the general population. As it is now technically feasible to screen for many more diseases, the question arises whether this population prefers a limited ancestry-based offer or a pan-ethnic expanded carrier screening panel that goes beyond the diseases that are frequent in their own population, and is offered regardless of ancestry. An online questionnaire was completed by 145 individuals from the Dutch Jewish community (>= 18 years) between April and July 2014. In total, 64.8% were aware of the existence of ancestry-based carrier screening, and respondents were generally positive about screening. About half (53.8%) preferred pan-ethnic expanded carrier screening, whereas 42.8% preferred ancestry-based screening. Reasons for preferring pan-ethnic screening included 'everyone has a right to be tested', 'fear of stigmatization when offering ancestry-based panels', and 'difficulties with identifying risk owing to mixed backgrounds'. 'Preventing high healthcare costs' was the most important reason against pan-ethnic carrier screening among those in favor of an ancestry-based panel. In conclusion, these findings show that people from the Dutch Jewish community have a positive attitude regarding carrier screening in their community for a wide range of diseases. As costs of expanded carrier screening panels are most likely to drop in the near future, it is expected that these panels will receive more support in the future.
Original languageEnglish
Pages (from-to)171-177
JournalEuropean Journal of Human Genetics
Volume24
Issue number2
DOIs
Publication statusPublished - Feb 2016

Cite this