Show Summary Details
Page of

Large Community-Based Diagnostic Studies in the USA 

Large Community-Based Diagnostic Studies in the USA
Large Community-Based Diagnostic Studies in the USA

John E. Cooper

and Norman Sartorius

Page of

PRINTED FROM OXFORD MEDICINE ONLINE ( © Oxford University Press, 2016. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Medicine Online for personal use (for details see Privacy Policy and Legal Notice).

date: 18 November 2018

After the publication of DSM-III in 1980, the next major diagnostic event in the USA was the NIMH Epidemiological Catchment Area (ECA) study. This aimed to estimate the distribution of DSM-III disorders in the general population .For this, an interviewing procedure, the Diagnostic Interview Schedule (DIS) was developed, which could be administered to selected subjects by specially trained lay interviewers. Five catchment areas were chosen; these were St Louis, (Kansas), Baltimore, Durham (North Carolina), New Haven (Connecticut) , and Los Angeles, each of which contained an already established research centre. The findings of the ECA study, particularly the high rate of co-occurrence of disorders, stimulated the National Co-morbidity Survey ten years later (1990-1992). This used a national probability sample, rather than being restricted to specified catchment areas. The National Co-morbidity Replication Survey ten years after that (2001-2003) confirmed the findings of the previous surveys, although generally reporting somewhat higher rates of occurrence for most of the disorders.

Access to the complete content on Oxford Medicine Online requires a subscription or purchase. Public users are able to search the site and view the abstracts for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.