Concept: Families First Screening (FFS) / BabyFirst Screening (BFS) - Method of Creating a FFS / BFS Dataset
Last Updated: 2023-12-01
1. The Data Files
There are two types of data files relevant to working with the FFS data:
- FFS datasets - contain the FFS screening ID (i.e.: bfs_id) and the screening outcomes. There are several FFS data files based on the date of acquisition.
- Examples of the outcomes data include indicators for:
- alcohol and drug use by the mother during her pregnancy;
- maternal smoking during pregnancy;
- parental history regarding anxiety disorders, depression, child abuse, and criminal involvement;
- indication of whether the mother/father completed grade 12; and
- physical and medical characteristics of child.
For a list of specific indicators from MCHP research, please see the section titled Variables / Indicators From the Risk Screening Tool below.
- NOTE: Over time, the content/structure of the BFS/FFS datasets has changed. Please read the MCHP internal document titled The BabyFirst Screen (BFS) and Families First Screen (FFS) - Differences between the two screens - (internal access only) - located in the Links section below for a description of cautionary notes when working with this data and a list of the differences in the data content/structure between the forms/datasets.
- Linkfile datasets - contain the FFS screening ID (i.e.: bfs_id) associated to a mother and her potential newborn(s).
2. Steps for Creating the FFS Dataset
The steps listed below are a general summary of what needs to be done in order to generate a final FFS dataset. Some details have been omitted. If you would like a more detailed explanation or further your understanding, please refer to the PowerPoint presentation titled Families First Screen (FFS) - SAS Code to Generate the FFS Dataset - (internal access only) - by Wendy Au from the February 27, 2013 MCHP Data Analyst meeting. This concept also contains links to SAS code that have been used for generating the BFS and FFS datasets. Out Of Province (OOP) births are accounted for in the FFS/BFS data/SAS code programs. The FFS SAS code example deals with OOP births for the time period 2008-2010. Prior to this (for 2000-2007), OOP births have already been accounted for. Please see the example FFS and BFS SAS code provided in the SAS code and formats section below - (internal access only) for more detailed technical information.
- Generate your newborn cohort.
- After you have generated your newborn cohort obtain from the REGISTRY file a mom_baby dataset that attempts to link each of the newborns in your newborn cohort to a mom. Previous linkage rates indicate that the mom-baby linkage is close to 99%.
- Set all the FFS (social.hcm_FFS_xxxxjan) datasets together. This dataset contains the Families First Screen number (bfs_id) and screening outcomes data.
- Set all the Linkfile (social.hcm_FFS_linkfile_xxxxjan) datasets together. This dataset contains the Families First Screen number (bfs_id) and the mom phins and her potential newborns.
- Now merge the FFS and Linkfile dataset together by common bfs_id. This dataset is referred to as the FFS_linkfile dataset.
NOTE: In order to maximize the number of newborns screened allow up to a (+/-) 90 day difference in the birthdate value from the two sources.
- For each bfs_id record in the FFS_linkfile dataset determine:
- if the mom phin agrees from the two data sources. If so then mom_match = 1.
- if the newborn phin agrees from the two data sources. If so then child_match = 1.
- Determine the source of the mom phin and baby phin; either FFS, Linkfile or alternative.
- Create 4 datasets where each dataset will contain the various combinations of mom phin (if any) and baby phin (if any).
- FFS_linkfile_1: where mom phin ^= . or baby phin ^= .
- FFS_linkfile_2: where mom phin from linkfile ^= . or baby phin from linkfile ^= .
- FFS_linkfile_3: where mom phin from FFS ^= . or baby phin from FFS ^= .
- FFS_linkfile_4: where an alternative mom phin ^= . or alternative baby phin ^= .
- Set all the FFS_linkfile_x (ie. where x = 1, 2, 3 and 4) together. This dataset is referred to as the FFS_linkfile dataset.
NOTE: There will be multiple repeat bfs_id records, but this is okay as ultimately the dataset is reduced down to one bfs_id per baby and mom pair.
- There are some bfs_id(s) where a mom phin exists, but a baby phin is missing. Use the mom_baby dataset obtained from the REGISTRY to potentially identify the baby associated with that mom. This dataset is referred to as the relink_mom_baby dataset.
- Set the FFS_linkfile dataset and the relink_mom_baby dataset together.
- Create 2 datasets:
- one_bfs_id dataset (ie. baby/mom record is associated to only 1 bfs_id)
- one_plus_bfs_id dataset (ie. baby/mom record is associated to possibly 1+ bfs_id and possibly 1+ formdates).
NOTE: in the one_plus_bfs_id dataset remove duplicate records.
- Set the one_bfs_id dataset and the one_plus_bfs_id dataset together. This dataset is referred to as the all_FFS dataset and it contains all the possible baby/mom FFS available. Additional cleaning of records is required.
- Now merge the newborn dataset to the mom_baby dataset obtained from the REGISTRY by common baby phin. By doing so you have linked the baby to his/her mom. This dataset is referred to as the newb dataset. Add suffix _newb to all the variables in the newborn dataset.
- Next merge the newborn dataset to the all_FFS dataset by common baby phin. By doing so you have linked the baby to his/her screen. This dataset is referred to as the newb_FFS dataset. Add the suffix _FFS to all common variables appearing in both the all_FFS and the newb datasets.
- Upon merging by the common baby phin check to see if the mom phins agree from the two 2 data sources.
NOTE: There will be some newborns that report 2 different mothers. However, you will only want to associate one mom to a newborn. In the work completed, when such a scenario occurred, choose the mom phin as reported in the REGISTRY file.
- Create 2 datasets from the newb_FFS dataset:
- FFS_exist_0 (i.e.: FFS_exist = 0 -> baby has NO screen available)
- FFS_exist_1 (i.e.: FFS_exist = 1 -> baby has AT LEAST one screen available)
- Where FFS_exist = 1 reduce down to one bfs_id per baby/mom record.
- Set the FFS_exist_0 dataset and the FFS_exist_1 dataset together.
NOTE: if a baby is found in both datasets (i.e.: reports no screen and has screen) keep the baby record that reports a screen.
- Now you have successfully generated your final FFS dataset.
NOTES:
- Depending on the set of inclusion/exclusion criteria(s) applied to the newborn cohort, the % of infants screened will vary. However, based on past experience, one should expect around an 80% screening rate.
- The method for creating the BFS dataset is similar to the method for creating the FFS dataset. The detailed methods for creating the BFS are not described in this concept. For more detailed information on creating the BFS dataset, please refer to the appropriate SAS code link in the SAS code and formats - (internal access only) section below.
3. FFS and BFS Macro Calls
MCHP has developed SAS macros to assist in the generation of FFS and BFS datasets.
The following macro call from the MCHP Macro Library can be used to create a FFS dataset:%_FFS (nbbirth_cohort = ,
nbbirthdt_startdt = ,
nbbirthdt_enddt = ,
FFS_output = FFS_dataset);
nbbirth_cohort = The phins of the children in the cohort.
NOTE: the phin of the child must be named scrphin.
nbbirthdt_startdt = The min birthday value of the phins in the cohort.
NOTE: the format of the date must be 01Jan2003.
nbbirthdt_enddt = The max birthday value of the phins in the cohort.
NOTE: the format of the date must be 31Dec2003.
FFS_output = the name of the final FFS dataset - default is FFS_dataset.The following macro call from the MCHP Macro Library can be used to create a BFS dataset:
%_BFS (nbbirth_cohort = ,
nbbirthdt_startdt =,
nbbirthdt_enddt =,
BFS_output = BFS_dataset);
nbbirth_cohort = The phins of the children in the cohort.
NOTE: the phin of the child must be named scrphin.
nbbirthdt_startdt = The min birthday value of the phins in the cohort.
NOTE: the format of the date must be 01Jan2000.
nbbirthdt_enddt = The max birthday value of the phins in the cohort.
NOTE: the format of the date must be 31Dec2002.
BFS_output = the name of the final BFS dataset.