Page Last Updated: October 10, 2025

Known Issues🔗

The following issues have been identified in the current HBCD data release. We are actively working to address them and will include fixes in either the patch Release 1.1 or Release 2.0 unless stated otherwise. This page will be updated as new issues are discovered. If you have questions or would like to report an issue, please submit a ticket through the Lasso Help Center.

General🔗

Instruction Metadata - Caution, Please Read Carefully🔗

Instruction text in the form's metadata is extracted programmatically from the most recent instruction field in the REDCap Data Dictionary for each form, based on field order. This means:

If an instruction spans multiple fields, only the last portion will be captured, resulting in partial instructions.
Because the instruction is provided for all fields up to the next set of instructions, some fields may display text intended for a previous section.
Manual curation of instruction metadata is planned for future releases. For the most accurate information, always refer to the original form.

Expected Fix: TBD

Basic Demographics🔗

Income Not Displayed For All Participants🔗

In rare cases, the Income field in Basic Demographics (sed_basic_demographics) may not be displayed for certain participants. This issue results from errors in transferring data from the REDCap Demographics form (sed_bm_demo) into the Basic Demographics. For complete income information, please reference the original source field in sed_bm_demo.
Expected Fix: R1.1

Duplicate Options for 'Mother Race' Variable🔗

The variable 'Mother Race' (sed_basic_demographics_screen_mother_race) has duplicate options for the selection of 'Black African American' (option #3). This option is not used for data entry, and instead the 'Black_or African American' option (option #5) should be used. No other variables are affected by this.
Expected Fix: R1.1

Gestational Age at Delivery and Mother’s Age at Delivery🔗

Gestational Age at Delivery (sed_basic_demographics_gestational_age_delivery) and Mother's Age at Delivery (sed_basic_demographics_mother_age_delivery) are variables that should only be available for participants who have V01 + V02 or V03 in the data release which had a cutoff of visit completion of July 1, 2024. However, for these measures data for deliveries after July 1, 2024 were included in the release in error. These fields which represent births beyond our cutoff dates were incorrectly made available, did not undergo QC, and will be removed in the patch release. Users can currently filter or remove any values for participants that do not have a V01 + V02 or V03 until the fix.
Expected Fix: R1.1

Mother Ethnicity🔗

The variable screen_mother_ethnicity should be a 2-level variable, however it is currently noted as a 4-level variable in the data dictionary. Levels of 0 and 1 (in the data dictionary) are included in error, they do not appear in the dataset; all participants with valid data have a value of 2 (Hispanic) or 3 (non-Hispanic).
Expected Fix: R1.1

Mother Race and Ethnicity🔗

For the variable rc_mother_ethnoracial_aou_race_ethnicity, the “None of these fully describe me/Other” response option is not currently a separate category for this variable and will be added.
Expected Fix: R1.1

Erroneous Inclusion of Response Option (2=Hawaiian) in 'Mother Race' Variable🔗

The variable sed_basic_demographics_screen_mother_race has two levels to reflect Hawaiian race (2 = Hawaiian; 7 = Native Hawaiian or Other Pacific Islander). 2 = Hawaiian was not a response option to this question and can be ignored; no participants selected this option.
Expected Fix: R2.0

Biospecimens🔗

Nails & Urine: Collection & Analysis Dates Currently Missing🔗

Collection dates and analysis dates for Nails and Urine are not provided in the current release and will be provided in the future.
Expected Fix: R1.1

Urine: Incorrect Specific Gravity Variable🔗

Urine concentrations vary by participant and concentration corrections can be made by creatine or specific gravity. However, the urine specific gravity variable is incorrect (bio_bm_biosample_urine_bio_spg_u) (there are several participants with “1” when the variable should be expressed in the thousands) and should therefore not be analyzed. Only the initial creatinine results from sample validation should be used for urinary concentration corrections.
Expected Fix: R1.1

Urine: Toxicology (Cotinine)🔗

There may be negative values for urinary toxicology results (e.g. bio_bm_biosample_urine_bio_bm_biosample_urine_bio_c_cot_u). Please note that negative values for these variables are not biologically plausible. We recommend users convert these values to 0 prior to analyzing their data.
Expected Fix: R1.1

Urine: Negative Gestational Ages🔗

There are two participants with negative gestational ages in the urine biosample dataset due to inaccurate collection dates of the biosample. Please do not include these two observations in your analysis.
Expected Fix: R1.1

EEG🔗

HBCD-MADE Resting-State Derivatives🔗

The HBCD-MADE summary statistics for resting-state EEG data contained in the derivative file processed_data/*_task-RS_powerSummaryStats.csv (see HBCD-MADE derivatives structure for details) are incorrect due to a former bug in the pipeline and should not be used for analysis. Users should instead generate these files themselves using scripts provided via HBCD EEG Utilities for extracting summary statistics.
Expected Fix: R1.1

Imaging Data🔗

Run ID Order May Be Incorrect🔗

For HBCD BIDS data with multiple runs, the run number displayed in the run-{X} field is not guaranteed to reflect the chronological acquisition order. This applies to both raw and processed file-basedimaging and biosignal data
(varied formats) data, as well as derived tabulatedinstrument and derived data
(tabulated format) data. Despite this, the data remain internally consistent — for example, the run IDs in the raw BIDS data match the corresponding runs in the processed BIDS data.
Expected Fix: R2.0

Neurocognition & Language🔗

SPM-2 T-Scores🔗

The t-scores are currently not provided, as the original conversion from raw score to t-score was incorrect. The t-scores will be corrected and provided in a future data release.
Expected Fix: R1.1

Pregnancy & Exposure, Including Substance Use🔗

Pregnancy & Infant Health🔗

ICD Code Names/Labels Inconsistently Provided🔗

In cases where ICD codes are provided, corresponding names/labels are sometimes not provided. This is a known issue to be fixed in future releases. In the meantime, users can consider existing packages to merge ICD labels in Stata, SAS, or R.
Expected Fix: R2.0

Infant Health Check🔗

The fields pex_bm_healthv2_inf_00<1|2|3|4|5>__00 are 'Descriptive' fields that were erroneously inclduded and will be removed in a future release. They can be safely ignored.
Expected Fix: R1.1

Mental Health🔗

APA 1/2🔗

Individual items for Level 1 and Level 2 domains are provided, but any summary scores and corresponding T-scores (where appropriate) are not provided for any Level 2 domains. This will be corrected in a future release. In the meantime, users can calculate their own summary scores and convert them to T-scores as appropriate based on the scoring procedures provided in the user documentation. Please note for Mania, the Level 2 individual items are currently coded on a scale of 1 to 5 and will need to be recoded as 0 to 4 prior to summary score calculation. This will be corrected in a future release.
Expected Fix: R1.1

Edinburgh Postnatal Depression Scale (EPDS)🔗

Users should be aware that each item for the EPDS is duplicated (for example, epds_001 and epds_001_01); these duplicate columns contain the same data. Duplicate data will be removed in the future.
Expected Fix: R1.1

Substance Use🔗

TLFB Substance Use Flags🔗

The TLFB Substance Use Flags are intended to indicate whether a participant had ever met the substance-specific use criteria during or after pregnancy across visits V01 and V02 at the time of survey administration. Currently, only the alcohol use flag correctly follows this logic. All other substance use flags are incorrect and will be corrected in a future release. In the meantime, use the R code provided here to derive your own substance use flag variables.
Expected Fix: R1.1

TLFB Incorrect Age Variables🔗

The following age variables are incorrect: pex_ch_tlfb_adjusted_age, pex_ch_tlfb_gestational_age, and pex_ch_tlfb_candidate_age. Please do not use these age variables in your analyses until they are corrected.
Expected Fix: R1.1

Blank Cells in PhenX Discrimination Survey🔗

For the PhenX+ Discrimination survey, one of the multi-select questions (column sed_bm_phx__discr.006: "What do you think is the main reason for these experiences? If more than one main reason, check all that apply.") is blank for some participants.
Expected Fix: R2.0

Visit Information🔗

Missing Substance Use Flags🔗

The substance use flags found in the Visit Information data are single summary variables to reflect substance use status (yes/no) based on any positive reports from the (1) Timeline Follow Back (self-report), (2) Healthy History (V02) (self-report), or (3) USDTL urine toxicology results. Nail toxicology results were not used in the creation of these substance use flags. Further, the substance use flag variable is missing for alcohol, opioid, cannabis, and nicotine, and will be integrated in future data releases. In the meantime, users can generate their own substance use flag summary variables using the individual components found in the “pregnancy exposures, including substances” and “biospecimens” domains.
Expected Fix: R1.1

Invalid Participant Withdrawal Dates for Participants Who Did Not Withdraw🔗

Participants who did not withdraw from the study (and so have a value of "no" for par_visit_data_participant_withdrawal) have a sentinel value of 12/26/1999, meaning no withdrawal, for participant withdrawal date (par_visit_data_participant_withdrawal_date). This can be safely ignored. Participants who did withdraw (and so have a value of “yes” for par_visit_data_participant_withdrawal) have a valid date and are unimpacted.
Expected Fix: TBD