Loading...

Reset Password

NDAR provides a single access to de-identified autism research data. For permission to download data, you will need an NDAR account with approved access to NDAR or a connected repository (AGRE, IAN, or the ATP). For NDAR access, you need to be a research investigator sponsored by an NIH recognized institution with federal wide assurance. See Request Access for more information.

Warning Notice

This is a U.S. Government computer system, which may be accessed and used only for authorized Government business by authorized personnel. Unauthorized access or use of this computer system may subject violators to criminal, civil, and/or administrative action.

All information on this computer system may be intercepted, recorded, read, copied, and disclosed by and to authorized personnel for official purposes, including criminal investigations. Such information includes sensitive data encrypted to comply with confidentiality and privacy requirements. Access or use of this computer system by any person, whether authorized or unauthorized, constitutes consent to these terms. There is no right of privacy in this system.

You have logged in with a temporary password. Please update your password. Passwords must contain 8 or more characters and must contain at least 3 of the following types of characters:

Subscribe to our mailing list

Mailing List(s)
Email Format

You are now leaving the National Database for Autism Research (NDAR) web site to go to:

Click on the address above if the page does not change within 10 seconds.

Disclaimer

NDAR is not responsible for the content of this external site and does not monitor other web sites for accuracy.

Selected Filters
No filters selected

The filters you have selected from various query interfaces will be stored here, in the 'Filter Cart'. The database will be queried using filters added to your 'Filter Cart', when multiple filters are defined, each will be executed using 'AND' logic, so with each filter that is applied the result set gets smaller.

From the 'Filter Cart' you can inspect each of the filters that have been defined, and you also have the option to remove filters. The 'Filter Cart' itself will display the number of filters applied along with the number of subjects that are identified by the combination of those filters. For example a GUID filter with two subjects, followed by a GUID filter for just one of those subjects would return only data for the subject that is in both GUID filters.

If you have a question about the filter cart, or underlying filters please contact the help desk at The NDA Help Desk

Description
Value Range
Notes
Data Structures with shared data
No filters have been selected

Change in Study Status

cssp

01

Download Definition as
Download Submission Template as
Element NameData TypeSizeRequiredDescriptionValue RangeNotesAliases
subjectkeyGUIDRequiredThe NDAR Global Unique Identifier (GUID) for research subjectNDAR*guid
src_subject_idString20RequiredSubject ID how it's defined in lab/projectpid
interview_ageIntegerRequiredAge in months at the time of the interview/test/sampling/imaging.0 :: 1260Age is rounded to chronological month. If the research participant is 15-days-old at time of interview, the appropriate value would be 0 months. If the participant is 16-days-old, the value would be 1 month.
interview_dateDateRequiredDate on which the interview/genetic test/sampling/imaging was completed. MM/DD/YYYYRequired field
genderString20RequiredSex of the subjectM;FM = Male; F = Female
phase_ctsIntegerRecommendedPhase I (12-weeks) Phase II (6-months)1;21 = Phase I - Participants were randomly assigned to receive sertraline (Zoloft), cognitive behavioral therapy, a combination of these treatments, or a placebo. 2 = Phase II - Maintenance period for participants who responded to any of the three active treatments.phase, phase_ct, phase_p
change_sIntegerRecommendedType of study status change1;2;31 = Study Dropout;2 = Treatment Dropout;3 = Pre-mature Terminationchange
stdateDateRecommendedStudy Treatment stop datedaypmt, daytxdr
daydropIntegerRecommendedStudy Dropout - day of study drop
wkstdropIntegerRecommendedStudy week subject drops out of study0::360 = prior to Week 1;1 = Week 1;36 = Week 36wkpmt, wktxdrop
sd_othrsString80RecommendedStudy Dropout - description of other reason
erlrsmdsString255RecommendedDescribe reason for early terminationtx_othrs, whatothr_p
trminatnIntegerRecommendedPremature Termination - Nature of the premature termination1;21 = Assigned study treatment discontinued all or in part;2 = Study treatment continued but out-of-protocol intervention added
whatfxString60RecommendedDescription of intolerable side-effects
daylasttxIntegerRecommendedStudy day last regular treatment session was completed
daymstrecntIntegerRecommendedStudy day most recent scheduled assessment was completed
cssyornIntegerRecommendedWas a change in study status assessment completed?0;10 = No;1 = Yes
daycssIntegerRecommendedStudy day change in study status form was completed
dayfinlIntegerRecommendedStudy day final assessment was completed
asapformIntegerRecommendedWas an ASAP form completed?0;10 = No;1 = Yes
dayasap_pIntegerRecommendedStudy day ASAP initiated
asapanelIntegerRecommendedPresented to cross-site ASAP Panel?0;10 = No;1 = Yes
daypanlIntegerRecommendedStudy day of ASAP Panel
daychangeIntegerRecommendedStudy day of change in study status assessment
changewkIntegerRecommendedStudy week of change in study status assessment
stdor1IntegerRecommendedDropout -subject moved and participation is no longer possible0;11 = Yes; 0=Nosd_moved
stdor2IntegerRecommendedDropout - lost to follow-up1;01 = Yes; 0=Nosd_lost
stdor3IntegerRecommendedDropout-consent withdrawn1;01 = Yes; 0-Nosd_wthdr
stdor5IntegerRecommendedDropout-adverse event1;01 = Yes; 0=Nosd_advev, tx_advev
stdor6IntegerRecommendedDropout-subject' death1;01 = Yes; 0=Nosd_died
stdor8IntegerRecommendedDropout-unknown reason1;01 = Yes; 0=Nosd_unkn, tx_unknw
stdor7IntegerRecommendedDropout-other reason1;01 = Yes; 0=Nosd_other, tx_other
tx_attndIntegerRecommendedUnable to attend treatment sessions0;10 = No;1 = Yes
tx_nointIntegerRecommendedNo longer interested in participating0;10 = No;1 = Yes
pregIntegerRecommendedpatient become pregnant0;1;-70=No; 1=Yes; -7=RefusedTX_PREG
tx_cnsntIntegerRecommendedChild/parent withdrew consent for treatment0;10 = No;1 = Yes
tx_nocbtIntegerRecommendedDo not want to participate in CBT0;10 = No;1 = Yes
tx_nopboIntegerRecommendedDo not want to risk possibility of taking PLACEBO0;10 = No;1 = Yes
tx_nomedIntegerRecommendedDo not want to risk possibility of taking meds0;10 = No;1 = Yes
psycoticIntegerRecommendedSubject became psychotic0;10 = No;1 = Yes
manicIntegerRecommendedSubject became manic0;10 = No;1 = Yes
hypomancIntegerRecommendedSubject became hypomanic0;10 = No;1 = Yes
agitatedIntegerRecommendedSubject displayed agitation/disinhibition0;10 = No;1 = Yes
nosucontIntegerRecommendedSubject became suicidal0;10 = No;1 = Yes
chrt_que2IntegerRecommendedPatient made a suicide attempt0;10=No; 1=Yessuiatmpt
chronillIntegerRecommendedChronic medical illness0;10 = No;1 = Yesillness
medintefereIntegerRecommendedUse of medications that interfere with study0;10 = No;1 = Yesmeds
subabuseIntegerRecommendedcurr substance abuse or depend0;1;-70=No; 1=Yes; -7=Refused
pregnantIntegerRecommendedPatient is currently pregnant0::2;-7; 9990=No; 1=Yes;2=DK;-7= Refused; 999=Legimately skipped
nocontctIntegerRecommendedUnable to contact0;10 = No;1 = Yes
worscondIntegerRecommendedCondition substantially worse0;10 = No;1 = Yes
norespnsIntegerRecommendedLack of clinical response0;10 = No;1 = Yes
anclrytxIntegerRecommendedSubject requires ancillary treatment0;10 = No;1 = Yes
sidefxIntegerRecommendedIntolerable side-effects0;10 = No;1 = Yes
otherrsnIntegerRecommendedPremature termination. Other reason0;10 = No;1 = Yes
comments_miscString4,000RecommendedMiscellaneous comments on study, interview, methodology relevant to this form data
studyString100RecommendedStudy
trtgroupString2RecommendedTreatment GroupN1;N2;R1;R2;R3N1=Non-Responder Entering Fluvoxamine; N2=Non-Responder Entering Fluoxetine; R1=Maintenance; R2=Responder Entering Fluvoxamine; R3=Responder Entering Fluoxetine
q18_8dIntegerRecommendedBlind broken0; 1; -7; -8; -9Complete only if q18_8 = 1
medication1_nameString100RecommendedName first medication that the participant has taken999= Legitimately skipped;
medication2_nameString100RecommendedName second medication that the participant has taken999= Legitimately skipped;
medication3_nameString150RecommendedName third medication that the participant has taken999= Legitimately skipped;
medication4_nameString100RecommendedName fourth medication that the participant has taken999= Legitimately skipped;
weekFloatRecommendedWeek in level/study99=week 10-week 14
siteString100RecommendedSiteStudy Site
ancitx1String100Recommendeddescription of treatment
ncpillIntegerRecommendedNon-compliance - Pill count0;10=No; 1=Yes
schprbIntegerRecommendedSubject has scheduling problems0;10=No; 1=Yes
lengassIntegerRecommendedSubject has problems with length of assessment0;10=No; 1=Yes
movedIntegerRecommendedPatient has moved away0;1;-70=No; 1=Yes; -7=Refused
personnIntegerRecommendedSubject doesn't like research staff0;10=No; 1=Yes
nrespdIntegerRecommendedSubject is a non-responder0;10=No; 1=Yes
ieevalIntegerRecommendedSubject agreed to IE evaluation?0;10=No; 1=Yes
nc3sesIntegerRecommendedSubject missed 3 sessions without rescheduling0;10=No; 1=Yes
aescodeIntegerRecommendedStaff code number of person completing this form
ctf_1IntegerRecommendedSubject received extension phase packet0;10=No; 1=Yes
compprotIntegerRecommendedCompleted treatment protocol0;1;-70=No; 1=Yes; -7=Refused
violateIntegerRecommendedProtocol Violation0;10=No; 1-Yes
hardcodeString1,200RecommendedSignificant Protocol ViolationTextual description of the protocol violation
stdor3_sString100RecommendedStage V: Dropout-consent withdrawn, sp.
termin_dayIntegerRecommendedDays since baseline that clinic officially terminated the subject
aeString250RecommendedAdverse event Description
Data Structure

This page displays the data structure defined for the measure identified in the title and structure short name. The table below displays a list of data elements in this structure (also called variables) and the following information:

  • Element Name: This is the standard element name
  • Data Type: Which type of data this element is, e.g. String, Float, File location.
  • Size: If applicable, the character limit of this element
  • Required: This column displays whether the element is Required for valid submissions, Recommended for valid submissions, Conditional on other elements, or Optional
  • Description: A basic description
  • Value Range: Which values can appear validly in this element (case sensitive for strings)
  • Notes: Expanded description or notes on coding of values
  • Aliases: A list of currently supported Aliases (alternate element names)
  • For valid elements with shared data, on the far left is a Filter button you can use to view a summary of shared data for that element and apply a query filter to your Cart based on selected value ranges

At the top of this page you can also:

  • Use the search bar to filter the elements displayed. This will not filter on the Size of Required columns
  • Download a copy of this definition in CSV format
  • Download a blank CSV submission template prepopulated with the correct structure header rows ready to fill with subject records and upload

Please email the The NDA Help Desk with any questions.

Distribution for DataStructure: cssp01 and Element:
Chart Help

Filters enable researchers to view the data shared in NDA before applying for access or for selecting specific data for download or NDA Study assignment. For those with access to NDA shared data, you may select specific values to be included by selecting an individual bar chart item or by selecting a range of values (e.g. interview_age) using the "Add Range" button. Note that not all elements have appropriately distinct values like comments and subjectkey and are not available for filtering. Additionally, item level detail is not always provided by the research community as indicated by the number of null values given.

Filters for multiple data elements within a structure are supported. Selections across multiple data structures will be supported in a future version of NDA.