DOE-STD-1187-2007, Beryllium-Associated Worker Registry Data Collection and Management Guidance

DOE-STD-1187-2007 June 2007 DOE TECHNICAL STANDARD Beryllium-Associated Worker Registry Data Collection and Management Guidance U.S. Department of Energy AREA SAFT Washington, D.C. 20585 DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited NOT MEASUREMENT SENSITIVE DOE-STD-1187-2007 ii Available on the Department of Energy Technical Standards Program Web site at http://www.hss.energy.gov/NuclearSafety/techstds/ DOE-STD-1187-2007 iii FOREWORD 1. This standard provides acceptable methods for compliance with the requirements of paragraph 10 CFR 850.39 “Recordkeeping and Use of Information.” Use of this standard is not mandatory. Users should review the document and determine if it meets their purpose. 2. Comments (recommendations, additions, and deletions) that may be of use in improving this document should be addressed to: U.S. Department of Energy, Office of Illness and Injury Prevention Programs, c/o Paul Wambach, HS-13/270 Corporate Square Building, 1000 Independence Avenue, SW, Washington, DC 20585-0270. 3. This standard was developed through a consensus process by staff operating the DOE Beryllium-Associated Worker Registry with expert review by data coordinators who report information to the Registry. It was developed to facilitate the routine collection, analysis, and dissemination of information on the health effects of occupational exposure to beryllium. DOE-STD-1187-2007 iv CONTENTS FOREWORD.................................................................................................................... iii 1. SCOPE ....................................................................................................................1 2. BACKGROUND ....................................................................................................1 2.1. Data Sources ......................................................................................................................1 2.2. Site Registry Coordinator.................................................................................................2 2.3. Data Collection ..................................................................................................................2 2.4. Worker Confidentiality Protection..................................................................................2 2.5. Data Analysis and Dissemination.....................................................................................3 3. ROSTER OF BERYLLIUM-ASSOCIATED WORKERS................................7 4. BERYLLIUM-RELATED MEDICAL SURVEILLANCE .............................10 4.1. Table 4.1 – Beryllium Lymphocyte Proliferation Test (LPT) Results ........................11 4.2. Table 4.2 – Smoking Data...............................................................................................12 4.3. Table 4.3 – Chest X-Ray Results....................................................................................13 4.4. Table 4.4 – Referral/Follow-Up .....................................................................................14 4.5. Table 4.5 – Bronchoalveolar Lavage (BAL) LPT Results ...........................................15 4.6. Table 4.6 – Transbronchial Biopsy and BAL Pathology Results ................................16 4.7. Table 4.7 – High-Resolution Computed Tomography (CT) Results...........................17 4.8. Table 4.8 – Cardiopulmonary Exercise Testing (CPET) Results................................18

4.9. Table 4.9 – CBD Evaluation Results..............................................................................19 4.10. Table 4.10 – Beryllium-Induced Dermatitis..................................................................20 5. DOE BERYLLIUM WORK HISTORY AND EXPOSURE DATA...............21 5.1. Table 5.1 – DOE Beryllium Work History....................................................................22 5.2. Table 5.2 – DOE Beryllium Activities and Exposure ...................................................24 6. TABLE RELATIONSHIPS ................................................................................29 DOE-STD-1187-2007 v 7. REQUIRED FIELDS...........................................................................................30 QUALITY ASSURANCE ...............................................................................................30 Appendix A – Frequently Asked Questions ....................................................................1 Appendix B – Chronic Beryllium Disease Definition .....................................................1 Appendix C – Process-Operation-Task Examples..........................................................1 Appendix D –Laboratory Reporting Limit .....................................................................1 Appendix E - Calculating Non-Standard Shift and Sequential Sample 8-Hour TWA ..................................................................................................................................1 DOE-STD-1187-2007 1 1. SCOPE: This standard provides acceptable methods for compliance with the requirements of Title 10 Code of Federal Regulations, Part 850.39 (10 CFR 850.39) “Recordkeeping and Use of Information.” It should be used by responsible employers subject to the requirements of 10 CFR 850 “Chronic Beryllium Disease Prevention Program” to guide their submission of information to the Department of Energy (DOE) Beryllium-Associated Worker Registry. Use of this standard promotes consistent reporting and efficient analysis and dissemination of information to those who need to know. 2. BACKGROUND: The DOE Beryllium-Associated Worker Registry is a complex- wide internal program to help DOE conduct and improve its chronic beryllium disease prevention programs. Paragraph 10 CFR 850.39 specifies beryllium recordkeeping and reporting requirements for both DOE federal and contractor employees. The Registry contains data on DOE contractor and federal workers, the jobs they performed, their beryllium exposure monitoring results, results from screening tests for chronic beryllium disease, and the results from subsequent medical diagnostic procedures. The Office of Illness and Injury Prevention Programs (HS-13) sponsored the development of this technical standard. The Registry is maintained by the Beryllium Registry Data Center at the Oak Ridge Institute for Science and Education (ORISE), Oak Ridge, Tennessee. The Registry includes several components called data sets. These data sets include: a roster, or listing, of all current workers who may be potentially exposed to or may have been previously exposed to beryllium; medical information related to signs and symptoms of beryllium-related disease; work history of beryllium jobs while employed at a DOE site; and exposure data (industrial hygiene sampling data) with calculated 8-hour time-weighted average (TWA) for that exposure. 2.1. Data Sources: Sources of information for these data include human resource

organizations; medical, safety, and industrial hygiene organizations; and other organizations such as operations, maintenance, engineering, and payroll. Additional sources of information may include Workers' Compensation files, the OSHA Form 200 and 300 log, and headquarters managed databases such as the Computerized Accident and Illness Reporting System (CAIRS), the Occurrence Reporting and Processing System (ORPS), and the Occurrence Reporting Binned Information Trending Tool (ORBITT). In the event that a worker who is enrolled in the Registry dies, information regarding the cause of death should be entered into the Registry. This information is available from a death certificate, which may be available through the occupational medicine clinic or human resource departments. If a death certificate is not available, the cause of death information may sometimes be obtained from the medical record. DOE-STD-1187-2007 2 2.2. Site Registry Coordinator: A Registry coordinator must be identified at each DOE site to serve as the point of contact between the site and the Beryllium Registry Data Center at Oak Ridge. The Registry coordinator should be responsible for coordinating activities at the site related to data collection, submitting data to the Data Center in a timely manner, receiving inquiries from the Data Center, contacting appropriate site personnel to resolve data management and collection issues, and correcting errors. It is expected that the Registry coordinator will interact with a variety of individuals at the site such as line managers, computer support personnel, industrial hygienists, and site medical clinic personnel. 2.3. Data Collection: 2.3.1. Each site should define the best file structure and transmitting protocol for their site, in coordination with the Beryllium Registry Data Center. All data must be submitted as electronic files. The Data Center is flexible as to file type and will work with each site individually to accommodate various computer systems. 2.3.2. All sites should have had, and been using, fully functioning data submission procedures no later than the 10 CFR 850 implementation date of January 7, 2002. Initial submissions to the Registry should have included all available data for all current beryllium-associated workers at that time. 2.3.3. Data must be submitted semi-annually to the Beryllium Registry Data Center at the Oak Ridge Institute for Science and Education (ORISE). The reporting periods begin on January 1 and July 1. Data should be submitted within 30 days of the reporting period to: The Beryllium Registry Data Center ORISE Center for Epidemiologic Research P.O. Box 117 Oak Ridge, TN 37831-0117 ORISE data coordinator: Phil Wallace Phone: (865) 576-3142 Fax: (865) 576-9557 Email: Phil.Wallace@orau.org 2.4. Worker Confidentiality Protection: To maintain the confidentiality of Registry data, the Registry coordinator must insure that a unique, encrypted identification number is assigned to every worker included in the Registry. All information that is submitted to the Registry regarding a specific worker must include his or her unique encrypted identification number. As the health impact of beryllium exposure may not occur until many years after employment, the Registry coordinator must insure that a system is maintained that links a DOE-STD-1187-2007 3

worker’s identity to his or her unique identification number, even after the worker terminates employment. Because the Beryllium Registry contains only encrypted identifying information, submitting information to it is explicitly exempt from Institutional Review Board review of research protocols under 10 CFR 745 section 101 (b)(4) that deals with Federal Policy for the Protection of Human Subjects. Unique encrypted identifiers should not be overly simplistic, such as reversing the worker's social security number, and should not duplicate other existing identifiers. The unique identifier should not be reassigned to a different worker, even if the first worker assigned to the identifier exits the workforce at that respective site. Should this worker return to the workforce at this site, his or her unique number should be restored to this specific individual. Sites that are participating in the Illness and Injury Surveillance Program (IISP) should use the previously assigned IISP identification number as the unique encrypted identifier. When a worker transfers from one DOE site to another, he or she will be reassigned a new unique encrypted identifier, coded according to the current site’s encryption scheme. Former sites should advise the transferees to identify themselves as a beryllium-associated worker to the site occupational medicine director (SOMD) upon their arrival at the new site. The SOMD should also determine if transferred workers were included in the Beryllium Registry at the previous site. If so, the SOMD will contact the SOMD at the previous site to obtain the old identification number so that linkages can be made. To maintain the confidential nature of the Registry, 10 CFR 850.39 (e)(2)(i) requires that the SOMD, or other designated site personnel within the occupational medicine clinic, retain the encryption key that identifies an individual worker to his or her unique identifier. The encryption key should be provided with security protection similar to other medically confidential information. Published reports using Registry information will generally contain only summary data. It is possible that descriptions of working conditions associated with a specific case will be published to share lessons with others. Such descriptions of specific cases will avoid containing enough unique information to allow readers to identify the individuals being described. 2.5. Data Analysis and Dissemination: The Registry serves as a surveillance system for current workers. It will provide DOE with information regarding adverse health outcomes associated with a specific exposure. The Registry will allow DOE to ascertain the prevalence of workers sensitized to beryllium and the number of workers who have chronic beryllium disease due to past exposure. As the data base is longitudinal in nature (i.e. following workers forward in time), the data will be able to determine the number of newly DOE-STD-1187-2007 4 sensitized workers (incidence) and characterize the development of disease based on a worker’s first exposure to beryllium. In addition, the exposure monitoring data will be used to characterize levels of beryllium across the complex. Lastly, the Registry is an epidemiologic tool to evaluate hypotheses about the causation of disease. Adverse health outcomes and exposure data will be analyzed together to determine the risk of disease. DOE-STD-1187-2007 5

2.5.1. Data Analysis: Data sent by each site to the Data Center will be initially reviewed for completeness and accuracy. Registry staff members will use a system of automated codes to determine missing data, data that are out of range (e.g. unusual or incorrect values) and other inconsistencies. The Data Center will notify each site data coordinator of errors or omissions within 60 days of the receipt of the data. The data coordinators must submit the corrected data within 30 days of notification. Data processing and subsequent analyses will be conducted by ORISE staff under the direction of the DOE Office of Health and Safety (HS-10.) When scientifically justifiable, categories of variables with small numbers will be collapsed to ensure more stable estimates of risk. Variables that had a total frequency of five counts or less, and could not be reasonably combined with others will be excluded from the analysis. Measures of central tendency, the mean, median, and geometric mean will be used in the analysis of continuous variables (such as age, beryllium exposure levels, etc). Continuous variables may be categorized based on their variance parameters for additional analyses. Estimates of the percent of exposures exceeding the DOE action level will be used as indicators of site performance in controlling exposures. In addition, this information may be used to examine the effect of compliance on the occurrence of CBD. Categorical data such as the beryllium lymphocyte proliferation test (BeLPT) results, smoking status, the use of respiratory protection, and the specified chemical compound, will be presented as frequency distributions. Relative risk (or the odds ratio) estimates will be used to determine the association of categorical variables with adverse health effect outcomes. Statistical associations between categorical variables and adverse health outcomes will be determined using a chi-squared test or Fisher’s exact test, as appropriate. Logistic regression will be used in the analyses of multivariate models to take into account continuous exposure variables, while adjusting for the effects of other variables of interest. Beryllium exposure data commonly contain a high percentage of data points lower than laboratory reporting limits; as a result, maximum likelihood and product limit estimates for censored data will be used in some analyses. The statistical significance level for all analyses will be set at a probability of <0.05 (two-tailed test). Analyses will be performed using SAS (SAS Institute, Cary, NC) and R (the R Foundation for Statistical Computing). The specifications of all variables are in this technical standard. DOE uses the term "sensitization" to mean that the individual has had abnormal results on at least two BeLPTs confirming exposure and an DOE-STD-1187-2007 6 immune system response to beryllium. Only one abnormal BeLPT is required for the DOL's EEOICP coverage of follow-up medical costs. CBD status was identified by the occupational medicine clinic in accordance with the Energy Employees Occupational Illness Compensation Program Act. Job titles will be reviewed and categorized into a matrix of occupational categories described below. Cumulative occupational beryllium exposure for each worker may be calculated as the sum of the job specific exposures multiplied by the years of exposure in the specific job (∑ (job title exposure estimate X years in the job title)).

The analytic techniques for this Registry are those appropriate for epidemiologic studies based on a longitudinal cohort or a health Registry design. Analyses will progress from simple descriptive statistics to statistical modeling where appropriate. Analyses will focus on all participating sites; individual site data may be analyzed separately depending on the size of the database. Frequency distributions will be reviewed for all data variables. The prevalence and incidence of beryllium sensitivity and CBD will be determined across all participating sites; when appropriate, analyses will be conducted for individual sites. The initial univariate analyses will focus on describing the demographic variables (e.g. age, gender, race, etc.) and employment variables (e.g. job category, date of first hire, duration of employment, exposure variables, etc) by the presence or absence of various health outcomes (sensitization, CBD, lung function scores, etc). An analysis of the exposure data will be conducted separately to characterize how exposures are distributed in the workforce. Exposure data with a high percentage of non-detectable results (left censored data) will be analyzed using methods adapted from survival analysis. Both parametric and non-parametric methods are described in an Oak Ridge National Laboratory report.1 The results of the analyses will be returned to individual site IH departments to assist them in determining compliance with exposure limits. Multivariate analyses will be used to refine the association between adverse health outcomes and exposure to beryllium. 2.5.2. Dissemination of Information: Analyses of health and exposure data will be published in periodic reports. Approved reports will be published on the DOE Office of Illness and Injury Prevention web site and submitted to the DOE Office of Scientific and Technical 1 Statistical Methods and Software for the Analysis of Occupational Exposure Data with Non-detectable Values, Frome EL and Wambach PF, ORNL/TM-2005/52, http://www.hss.energy.gov/HealthSafety/IIPP/hservices/statmethods.pdf, accessed 6/14/2007. DOE-STD-1187-2007 7 Information. Participating sites will be notified of the availability of these reports and asked for comments and suggested improvements for future reports. Data analyses will also be presented at meetings of DOE safety and health protection specialists such as those sponsored by the Energy Facility Contractors Group and the Beryllium Health and Safety Committee. One goal of reporting will be to provide information useful for communicating beryllium hazard information to beryllium-associated workers. Operating organizations responsible for implementing the employee training requirements of 10 CFR 850 will be a target audience for the distribution of periodic reports and the solicitation of comments for suggested improvements. 3. ROSTER OF BERYLLIUM-ASSOCIATED WORKERS: The Roster Data Set will be a compilation of all beryllium-associated workers submitted by the Registry coordinator to the Data Center. The following definitions from paragraph 10 CFR 850.3 should be used to guide decisions on the DOE and DOE contractor employees who should be included in the roster. Beryllium-associated worker means a current worker who is or was exposed or potentially exposed to airborne concentrations of beryllium at a DOE facility, including: (1) A beryllium worker; (2) A current worker whose work history shows that the worker may have been exposed to airborne concentrations of beryllium at a DOE facility; (3) A current worker who exhibits signs or symptoms of beryllium exposure; and (4) A current worker who is receiving medical removal protection benefits.

Beryllium worker means a current worker who is regularly employed in a DOE beryllium activity. Beryllium activity means an activity taken for, or by, DOE at a DOE facility that can expose workers to airborne beryllium, including but not limited to design, construction, operation, maintenance, or decommissioning, and which may involve one DOE facility or operation or a combination of facilities and operations. Fields marked with an asterisk (*) will be required. 3.1. Table 3 – Roster: 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique worker identification number (to be determined by site) DOE-STD-1187-2007 8 3. *Status Code N = New record, D = Delete record 4. *Year Born Year of birth 5. *Gender Gender of worker 6. Race If collected by the site 7. *Employer Type Indicate the worker's employer as (F)ederal, (C)ontractor, (S)ubcontractor, or (V)isitor 8. *First Hire on Site Date Date first hired to work on current site 9. Year Employment Ended Year individual separated from employment at site 10. Death Date Date of death 11. Immediate Cause Text abstracted from death certificate, immediate cause 12. First Cause Text abstracted from death certificate, first "Due to or as a consequence of" section 13. Second Cause Text abstracted from death certificate, second "Due to or as a consequence of" section 14. Other Cause Other significant conditions contributing to the death 15. Old Unique ID Unique ID from previous site, if applicable 16. Previous Site Text field that contains the name of the previous site where the worker was employed as a beryllium worker 3.1.1. Site Code: Identify the DOE site with a unique code. The Beryllium Registry Data Center will provide a site code to each Registry coordinator. Sites currently participating in the IISP should use their current site codes. 3.1.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link DOE-STD-1187-2007 9 multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID. 3.1.3. Status Code: Indicate whether this is a new record (N) to be added to the roster or a delete record (D) for a worker already in the roster. Only a new record (N) should be submitted for workers first entering the roster. To make changes to information for workers already in the roster, the site should submit both a delete (D) and a corresponding new record (N) that will replace all previous roster data for the worker. . 3.1.4. Year Born: Provide only the year of birth (YYYY). This is a measure to help ensure privacy and prevent identification of individuals by using a specific date of birth. 3.1.5. Gender: Provide the code for the gender of the worker as either male or female. 3.1.6. Race: Provide race if captured by the site. 3.1.7. Employer Type: Indicate the worker's current employment type as federal, contractor, sub-contractor, or visitor. The permanent employees of cost-plus subcontractors to a site integrating or management and operating contractor will be considered a contractor for the Registry. Visitors include visiting scientists, graduate students, research collaborators, vendors, etc.

3.1.8. First Hire on Site Date: Provide the date that the worker was hired for the first time to work on the current DOE site (MM/DD/YYYY). Personnel records for current workers normally should have been transferred to successive contractors for a number of reasons and in particular in order to calculate employee benefits. Personnel departments should have this information. Medical records for current workers likewise should be transferred to successive medical surveillance providers. The date of the worker’s first medical examination should be in the current medical files and may be a reasonable surrogate for the date first hired to work on the current site if the true date is not available. If no accessible records are available, information provided by the worker can be used. 3.1.9. Year Employment Ended: Provide the year (YYYY) that the worker separated from employment at the site. Current workers should have a blank (null) value in this field. The value should remain blank (null) if the employee transfers to a different employer on site. The year of the employee’s termination medical examination may be a reasonable DOE-STD-1187-2007 10 surrogate if the true date is not available. 3.1.10. Death Date: Provide the date on which worker’s death occurred, if available, in MM/DD/YYYY format. 3.1.11. Immediate Cause: Provide text describing the immediate cause of death. Abstract the "immediate cause of death" section from the death certificate. 3.1.12. First Cause: Provide text describing the first contributing cause of death. Abstract the first "due to or as a consequence of" section from the death certificate. 3.1.13. Second Cause: Provide text describing the second contributing cause of death. Abstract the second "due to, or as a consequence of" section from the death certificate. 3.1.14. Other Cause: Provide text describing other significant conditions identified as contributing cause(s) of death, but not related to the immediate cause of death. 3.1.15. Old Unique ID: Provide unique ID from previous site (for workers who have transferred from one DOE site to another DOE site). 3.1.16. Previous Site: Provide a text field that contains the name of the most recent previous site the worker was employed at as a beryllium- associated worker and was submitted to the Registry from that site. Examples of values: Sandia, LANL, Rocky Flats. (Site names can be abbreviated and will be changed to a code number by the Registry Data Center.) 4. BERYLLIUM-RELATED MEDICAL SURVEILLANCE: The beryllium-related medical surveillance data sets will contain the beryllium-related disease medical information obtained by the Site Occupational Medicine Director (SOMD) related to beryllium exposure and medical testing. Tables 4.1 through 4.3 contain information generated through periodic medical monitoring programs operated by occupational medicine clinics. The content and frequency of surveillance evaluations and tests offered employees will be determined by the SOMD based on policies and standards and the employee’s health and work history. Findings suggestive of possible chronic beryllium disease (CBD) will usually result in a referral to a pulmonary medicine or other specialized clinic for follow-up diagnosis and care. Tables 4.4 through 4.10 contain information from diagnostic evaluations. Obtaining copies of reports containing this information from the clinic often requires the signed release from individuals upon their return to work or in some cases individuals can provide copies themselves. No records will be available for individuals who refuse

DOE-STD-1187-2007 11 the offer of a diagnostic evaluation or refuse to release copies of reports on their evaluations. The content of a diagnostic evaluation will vary based on the health of the patient and the judgment of the clinician. A record should be provided for each of the following tests or evaluations if they were provided during the reporting period. When a record is submitted, fields marked with an asterisk (*) are required. 4.1. Table 4.1 – Beryllium Lymphocyte Proliferation Test (LPT) Results: A record should be submitted for each LPT result received from a testing laboratory. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *LPT date Date of blood draw for the LPT test 5. *LPT result LPT result: Normal (Negative), Abnormal (Positive), Refused, Borderline, Unsatisfactory 4.1.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.1.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID. 4.1.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for LPT test results. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. Because the LPT results data may contain up to 3 records with identical information for Site Code, Unique ID, and LPT Date, a delete record DOE-STD-1187-2007 12 (D) requires that all fields, including the LPT Result, be populated. Each delete record will apply to only one record in the data table, so if the site wishes to delete multiple records it should supply the proper number of delete records. 4.1.4. LPT date: Provide the date the blood was drawn for the LPT (MM/DD/YYYY). 4.1.5. LPT result: Provide the result of the LPT as Normal (Negative), Abnormal (Positive), Refused, Borderline (neither fully normal nor fully abnormal), or Unsatisfactory (a failed or un-interpretable test). 4.2. Table 4.2 – Smoking Data: Provide if this information has been collected for inclusion in an employee’s medical record. Provide the most recently collected information. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Date Reported Date that data on smoking status was captured 5. *SMOKE Smoking status : Current (C) , Former (F), Never (N), Unknown (U) 4.2.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.2.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID.

4.2.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance smoking data. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate DOE-STD-1187-2007 13 smoking data may contain only one record for each date reported for a worker. Therefore, a smoking data delete record (D) requires matching values for the Site Code, Unique ID, and Date Reported. 4.2.4. Date Reported: This is the date when the smoking status was captured. 4.2.5. SMOKE: Indicate the worker's smoking status as: Current (C), Former (F), Never (N), or if there are no data available, put Unknown (U). 4.3. Table 4.3 – Chest X-Ray Results: Report information on the most recent chest x-ray results for individuals added to the Roster during the reporting period (if available.) In subsequent reporting periods report only new chest x-ray results obtained in that reporting period including results of chest x-rays provided due to the employee’s participation in other medical monitoring or health promotion programs. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Date CXR Date chest X-ray 5. *CXR Result Chest X-Ray results 4.3.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.3.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID. 4.3.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for chest x-ray results. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The DOE-STD-1187-2007 14 aggregate chest x-ray data may contain more than one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, date of CXR, and CXR result. Each delete record will apply to only one record in the data table, so if the site wishes to delete multiple records it should supply the proper number of delete records. 4.3.4. Date CXR: Provide the date the chest X-Ray was taken (MM/DD/YYYY). 4.3.5. CXR Result: Indicate result of chest X-ray according to the ILO (International Labor Organization code), e.g. 0/0, or 0/1. If the X-ray does not have the ILO codes, the evaluation of the X-ray in text form is acceptable. For more information see http://www.cdc.gov/niosh/topics/chestradiography/breader- info.html#e. 4.4. Table 4.4 – Referral/Follow-Up: A referral/follow-up record should be submitted for individuals offered referral to specialized medical clinics because of medical surveillance findings suggestive of possible CBD. 1. *Site Code Site code (provided by ORISE Data Center)

2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Referral Offered Date Date follow-up referral offered 5. *Follow-Up Referral Accepted (Y) or declined (N) referral for diagnostic follow-up 4.4.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.4.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should DOE-STD-1187-2007 15 use the workers' IISP identifiers as the Unique ID. 4.4.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for referral or follow-up. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate referral/follow-up data may contain only one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, and the date the referral was offered. 4.4.4. Referral Offered Date: Indicate date the follow-up referral was offered (MM/DD/YYYY). 4.4.5. Follow-Up Referral: Indicate whether this individual accepted (Y) or declined (N) a referral for a follow-up examination. 4.5. Table 4.5 – Bronchoalveolar Lavage (BAL) LPT Results: A BAL record should be provided when interpretable information is available from diagnostic evaluation reports. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Date Lavage Date of BAL 5. *Lavage Result BAL results: Normal (Negative), Abnormal (Positive), Refused, Borderline, Unsatisfactory 4.5.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.5.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should DOE-STD-1187-2007 16 use the workers' IISP identifiers as the Unique ID. 4.5.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for BAL results. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate BAL results data may contain only one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, and date of lavage. 4.5.4. Date Lavage: Provide the date the BAL was administered (MM/DD/YYYY).

4.5.5. Lavage Result: Provide the result of the BAL LPT as Normal (Negative), Abnormal (Positive), Refused, Borderline (neither fully normal or fully abnormal), or Unsatisfactory (an unsatisfactory test). Note: pathology results may be available even if the LPT is Normal or Negative. 4.6. Table 4.6 – Transbronchial Biopsy and BAL Pathology Results: A BAL pathology record should be provided when interpretable information is available from diagnostic evaluation reports. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Date BX Date of transbronchial biopsy 5. *BX Result Transbronchial biopsy result 4.6.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.6.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data DOE-STD-1187-2007 17 Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID. 4.6.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for transbronchial biopsy and BAL pathology results. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate transbronchial biopsy data may contain only one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, and date of transbronchial biopsy. 4.6.4. Date BX: Provide the date the transbronchial biopsy and BAL were administered (MM/DD/YYYY). 4.6.5. BX Result: Indicate results of pathologist’s evaluation - suggested values are: normal (negative), positive - granuloma, positive - alveolitis, and positive-interstitial thickening. Indicate all that apply. Other values and comments may be provided. 4.7. Table 4.7 – High-Resolution Computed Tomography (CT) Results: A CT record should be provided when interpretable information is available from diagnostic evaluation reports. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Date CT Date of CT studies 5. *CT Result CT study result 4.7.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. DOE-STD-1187-2007 18 4.7.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID.

4.7.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for CT results. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate CT results data may contain only one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, and date of CT study. 4.7.4. Date CT: Provide the date the CT study was administered (MM/DD/YYYY). 4.7.5. CT Result: Indicate CT study result - suggested values are: normal, abnormalities consistent with CBD, opacities consistent with CBD, and abnormalities requiring medical follow-up for conditions other than CBD. Other values and comments may be provided. 4.8. Table 4.8 – Cardiopulmonary Exercise Testing (CPET) Results: A CPET record should be provided when interpretable information is available from diagnostic evaluation reports. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Date CPET Date of CPET studies 5. *CPET Result CPET study result 4.8.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. DOE-STD-1187-2007 19 4.8.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID. 4.8.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for CPET results. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate CPET results data allow (although unlikely) more than one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, date of CPET study, and CPET study result. Each delete record will apply to only one record in the data table, so if the site wishes to delete multiple records it should supply the proper number of delete records. 4.8.4. Date CPET: Provide the date the CPET study was administered (MM/DD/YYYY). 4.8.5. CPET Result: Indicate CPET study result - These studies will provide several measurements in the following categories. Suggested values should be normal or abnormal for: oxygen uptake, carbon dioxide output, gas exchange ratio, anaerobic threshold, cardiac output, blood pressure and vascular resistance, ventilation, and pulmonary gas exchange function. 4.9. Table 4.9 – CBD Evaluation Results: A CBD evaluation record should be provided when interpretable information is available from diagnostic evaluation reports. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *CBD Date Date CBD evaluation made

5. *CBD Result CBD evaluation result DOE-STD-1187-2007 20 4.9.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.9.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID. 4.9.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for CBD evaluation results. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate CBD evaluation results data may contain only one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, and date of CBD evaluation. 4.9.4. CBD Date: Indicate the date that the CBD evaluation was complete (MM/DD/YYYY). 4.9.5. CBD Result: Indicate CBD evaluation result as “CBD” when the patient has a definitive diagnosis of CBD, “BeS no CBD” when the patient has been found to be sensitized to beryllium but not to have CBD, and “No BeS or CBD” when a patient has been found to not be sensitized to beryllium or to have CBD. Use the definition of CBD in use for the Energy Employees Occupational Illness Compensation Program Act, given in Appendix B if the evaluation report provides findings and test results but not a definitive diagnosis. 4.10. Table 4.10 – Beryllium-Induced Dermatitis: Beryllium can cause skin diseases from contact with the more soluble forms or implantation of the less soluble forms. A record of a beryllium-induced dermatitis should be submitted if a diagnosis of a beryllium-related skin disease has been entered into the employee’s personnel medical record. The diagnosis may have been made by the occupational medicine clinic, an individual’s personal physician, or a specialist as part of a clinical evaluation for CBD. 1. *Site Code Site code (provided by ORISE Data Center) DOE-STD-1187-2007 21 2. *Unique ID Unique identifier (to be determined by the site) 3. *Status Code N = New record, D = Delete record 4. *Date of Dermatitis Date Be-induced dermatitis diagnosed 5. *Dermatitis Positive Be-induced dermatitis diagnosed - Positive (P), Negative (N), Equivocal (E) 4.10.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 4.10.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. . It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID.

4.10.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related medical surveillance data for beryllium-induced dermatitis. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate beryllium-induced dermatitis data may contain only one record for each date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, and date dermatitis diagnosed. 4.10.4. Date Dermatitis: Indicate the date of dermatitis diagnosis (MM/DD/YYYY). 4.10.5. Dermatitis Positive: Indicate whether beryllium-induced dermatitis was diagnosed as: Positive (P), Negative (N), or if neither fully positive nor fully negative, put Equivocal (E). 5. DOE BERYLLIUM WORK HISTORY AND EXPOSURE DATA: The Beryllium Work History and Exposure Data Sets will contain information about all activities having potential beryllium exposure where the beryllium-associated worker currently works or previously had worked and the exposures associated with those activities. See section 3 above for definitions of a beryllium-associated worker. Retrospective work history information most often will be collected through DOE-STD-1187-2007 22 questionnaires and interviews with the worker. Information from records generally will be more reliable than an individual’s memory and will be preferred if readily accessible. Location, organizational, and job title data on current work should be reported using terminology consistent with that used in official records to simplify investigations or studies that might become desirable in the future. The data should include working directly with beryllium, working in areas of potential beryllium exposure even if not working directly with beryllium, and activities with potential casual exposure to beryllium, such as working near an area where others are working directly with beryllium. Do not provide or submit classified data to the Registry. 5.1. Table 5.1 – DOE Beryllium Work History: 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique employee identifier (provided by data coordinator) 3. *Status Code N = New record, D = Delete record 4. Organization Code Department/division/organization 5. First Beryllium Job Start Date Date that first job involving beryllium began 6. *Activity General description of the job function 7. *Job Title Job title at time of Be exposure 8. *Job Start Date Date job involving beryllium began 9. Job Stop Date Date job involving beryllium stopped, if applicable 5.1.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 5.1.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data DOE-STD-1187-2007 23 Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID.

5.1.3. Status Code: Indicate whether this is a new record (N) to be added to the beryllium work history or a delete record (D) for a record that has been previously submitted to the Registry. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate beryllium work history data may contain only one record for each Job Start Date reported for a worker. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, and Job Start Date. 5.1.4. Organization Code: Provide the worker's department, division, or organization code or number. The Registry coordinator must provide a data dictionary (the code and the organization associated with that code) to the Data Center. 5.1.5. First Beryllium Job Start Date: Provide the recorded or reported date the worker began working in the first job in which he or she was potentially or actually exposed to beryllium (MM/DD/YYYY). For current workers, medical records normally will be the source of this information since they are transferred to successive medical surveillance providers and kept in the clinic. If records are not accessible the date should be the date reported by the employee to the best of his or her recollection. 5.1.6. Activity: A high level roll-up category that will be a general description of the job function. Provide a one-character code as selected from one of the following categories. 5.1.6.1. Management (M) – Predominately office work at a desk; first level supervisor and above. 5.1.6.2. Administrative Support (A) – Predominately office-work at a desk but can include tasks that involve visiting, production areas, shops and labs. This category includes but is not limited to information technology, clerical, and secretarial staff. 5.1.6.3. In-House Professionals (I)– Predominately office work at a desk typically without supervisory responsibilities. Occasional tasks outside office create opportunities for exposure. 5.1.6.4. Field Professionals (F)– Frequently works outside of their office in areas such as but not limited to laboratories, testing areas, and construction areas. Employees in the Illness and DOE-STD-1187-2007 24 Injury Surveillance category “Biohazard” should be placed in this category. 5.1.6.5. Technical Support (T) – Workers who typically support the field professionals and have hands-on work situations. 5.1.6.6. Service (S) – Typically includes but is not limited to custodians, drivers, laborers, laundry workers, linemen, mail clerks, pilots, railroad engineers, records center workers, stationary engineers, utility workers, and water plant operators. These workers support and maintain the facility’s infrastructure. Most work is not performed sitting at a desk. 5.1.6.7. Security and Fire (E) – Typically includes protective forces and firefighters. 5.1.6.8. Crafts (C) – Typically includes skilled craftsmen and laborers who are members of building trade unions and engaged in construction, remodeling or facility maintenance work. 5.1.6.9. Line Operators (O)–Typically workers who are directly involved in process, operation, or line activities at the facility. 5.1.6.10. Guests (G) – Employees on short-term assignments or internships. Typically includes guest scientists, postdoctoral fellows, co-op students, and interns. Potential for exposure dependent on job assignment.

5.1.6.11. Unknown (U) – Job title is missing. 5.1.7. Job Title: Provide the worker's job title at time of exposure, (e.g. Machinist, Technician, or Chemical Operator). This should be the job title used in pay and other employment records. 5.1.8. Job Start Date: For each subsequent job involving potential or actual exposure to beryllium, provide the date the worker’s duties, location, or job title changed (MM/DD/YYYY). This date may be recorded in medical, administrative, or exposure monitoring records. If records are not accessible the date should be the date reported by the employee to the best of his or her recollection. 5.1.9. Job Stop Date: Provide the date the worker stopped working in the job in which he or she was actually or potentially exposed to beryllium (MM/DD/YYYY). This date may be recorded in medical, administrative, or exposure monitoring records. If records are not accessible the date should be the date reported by the employee to the best of his or her recollection. If this is the current job for the worker a blank (null) value in the Job Stop Date field is acceptable. 5.2. Table 5.2 – DOE Beryllium Activities and Exposure: A record should be submitted for each beryllium exposure monitoring result. Records predominantly report the results of personal exposure monitoring aimed at determining whether an individual’s full shift exposure was in compliance with DOE-STD-1187-2007 25 the DOE action level or other 8-hour time weighted average occupational exposure limit. In some cases a single result will be reported in several records for coworkers judged to be similarly exposed. The information included in the record will generally come from the industrial hygiene sample data sheet and analytical laboratory sample analysis report. 1. *Site Code Site code (provided by ORISE Data Center) 2. *Unique ID Unique employee identifier (provided by data coordinator) 3. *Status Code N = New record, D = Delete record 4. *Location Identification Location where the exposure occurred 5. *Room/Area Room/area where exposure occurred 6. *Process Free form text describing beryllium activity process 7. Operation Free form text describing the beryllium activity operation 8. Task Free form text describing the beryllium activity task 9. *Actual Exposure Actual exposure level or laboratory reporting limit during the sampling period in μg/m3 10. *Actual Exposure < Reporting Limit Indicate whether the actual exposure is less than the laboratory reporting limit, Y/N 11. *Exposure Sample Volume The volume of air sampled in liters 12. *8-hour TWA 8-hour time weighted average exposure level or laboratory reporting limit in μg/m3 13. *Exposure Method Free form text describing the type of exposure method 14. *Sampling Method Describe the sampling method used 15. *Analytic Method Describe the analytic method used DOE-STD-1187-2007 26 16. *Exposure Sampling Time Exposure sampling time (min.) 17. Sample Number Sample identification number 18. *Monitoring Date Date monitoring was conducted - MM/DD/YYYY 19. Chemical Free form text describing beryllium chemical compound 20. Engineering Controls Free form text describing engineering controls 21. PPC&E Personal protective clothing and equipment used? Y/N 22. *Respirator Protection Respiratory protection used? Y/N 23. *Respirator APF Respiratory protection “Assigned Protection Factor “ Use 1 when no respiratory is worn.

5.2.1. Site Code: Identify the DOE site with a unique code. The Data Center will provide a site code to each data coordinator. Data coordinators currently participating in the IISP should continue to use their previously identified site codes. 5.2.2. Unique ID: Identify each beryllium-associated worker with a unique encrypted number. It will be assigned by the site and is used to link multiple records to one worker. Every record submitted to the Data Center must include the Unique ID. Sites enrolled in the IISP should use the workers' IISP identifiers as the Unique ID. 5.2.3. Status Code: Indicate whether this is a new record (N) or a delete record (D) in the beryllium-related exposure data. To make corrections to a previously submitted record the site should submit both a delete record (D) and a corresponding new record (N) that will replace the deleted record for the worker. The aggregate exposure data may contain more than one record for each date that monitoring was conducted. Therefore, a delete record (D) requires matching values for the Site Code, Unique ID, Monitoring Date, and one or more other fields. If Sample Number (which can be an encrypted value) has been provided by the site the key for a delete record (D)— and the corresponding new record (N) —can be Site Code, Unique ID, Monitoring Date, and Sample Number. Sample Number is not a required field and if it is not provided the site must designate the DOE-STD-1187-2007 27 additional field or fields that can be used to uniquely identify a record. (Each delete record will apply to only one record in the data table.) 5.2.4. Location Identification: Provide the on-site code for the location within which the beryllium exposure occurred. This should be the unique administrative code that usually will be established by the facility or property management organization for each building and area on site. The Registry coordinator must provide a data dictionary (the code and the building or area associated with that code) to the Data Center. This cannot be null, nor can it be populated with “not available.” 5.2.5. Room/Area: Free form text that is usually one or more room numbers where the beryllium exposure occurred. For outdoor areas or buildings where room numbers are not used this should be a description in common use at the site (for example “maintenance welding shop”). If no other information is available, repeat the information provided in 5.2.4 Location Identification above. This cannot be null, nor can it be populated with “not available.” 5.2.6. Process: Free form text that describes the beryllium activity process. Process is the highest level of grouped tasks. Dry machining is an example of a process. See Appendix C for more examples. This cannot be null, nor can it be populated with "not available." 5.2.7. Operation: Free form text that describes the beryllium activity operation. Operation is the mid-level of grouped tasks. Using a particular type of lathe is an example of an operation in the dry machining process. See Appendix C for more examples. 5.2.8. Task: Free form text that describes the beryllium activity task. Task is the lowest level of beryllium activity and is not grouped. Machine preparation is an example of a task performed in the operation of using a particular type of lathe. See Appendix C for more examples.

5.2.9. Actual Exposure: Provide the level of the worker's beryllium exposure measured during the sampling period for the Task (field 8) as determined by personal monitoring of the worker or by some other method. This will be the measured beryllium concentration during the time period the sample was collected. Examples of other methods are use of a direct-reading instrument, field wet chemical analysis results, and presuming an exposure based on the monitoring results of other workers performing similar tasks. The industrial hygienist must calculate the actual exposure before submitting data to the site Registry coordinator. Results below the laboratory reporting limit should be reported as concentrations calculated from the laboratory’s DOE-STD-1187-2007 28 reporting limit in the volume of air sampled. See Appendix D for an explanation of laboratory reporting limit. 5.2.10. Actual Exposure < Reporting Limit: Indicate by Y/N whether the value reported in Actual Exposure (field 9) is the calculated laboratory reporting limit rather than the actual measured exposure level. "Yes" indicates that the value reported in field 9 is calculated from the laboratory reporting limit. 5.2.11. Exposure Sample Volume: This is the volume of air sampled, in liters, that was used to calculate the "Actual Exposure" above. 5.2.12. 8-hour TWA: Provide the 8-hour TWA (time weighted average) of the worker's beryllium exposure for the work shift as determined by personal monitoring of the worker or other method. The industrial hygienist must calculate the 8-hour TWA before submitting the data to the Registry coordinator. If monitoring results show levels of beryllium that are less than the reporting limit, the 8-hour TWA should be calculated using the reporting limit (e.g., 0.03 μg/m3). See Appendix D for an explanation of reporting limit. See Appendix E for calculating 8-hour TWAs for non-standard work shifts and sequential sample results including results that are less than the reporting limit. 5.2.13. Exposure Method: Free form text describing the type of exposure measuring method used. Personal breathing zone is most common. Examples of other methods are use of direct-reading instruments, field wet chemical analysis results, and presuming an exposure based on the monitoring results of other workers performing similar tasks. 5.2.14. Sampling Method: Describe the sampling method used. Examples are procedures in the U.S. Department of Labor, Occupational Safety and Health Administration, OSHA Technical Manual, Fourth Edition, OSHA Instruction TED 1-0.15A, Washington, D.C., Government Institute, Inc., 1-20-99; National Institute for Occupational Safety and Health, Analytical Method 7102, Issue 1, 2-15-84; and National Institute for Occupational Safety and Health, Analytical Method 7300, Issue 2, 8-15-94. 5.2.15. Analytic Method: Describe the analytic method used. Examples are procedures in the U.S. Department of Labor, Occupational Safety and Health Administration, OSHA Technical Manual, Fourth Edition, OSHA Instruction TED 1-0.15A, Washington, D.C., Government Institute, Inc., 1-20-99; National Institute for Occupational Safety and Health, Analytical Method 7102, Issue 1, 2-15-84; and National Institute for Occupational Safety and Health, Analytical Method 7300, DOE-STD-1187-2007 29 Issue 2, 8-15-94.

5.2.16. Exposure Sampling Time: The length of time of the sampling that generated the actual sample exposure level, Actual Exposure (field 9), or an analogous length of time if possible, if the exposure was presumed by some other method. Examples of other methods are use of direct-reading instruments, field wet chemical analysis results, and presuming an exposure based on the monitoring results of other workers performing similar tasks. 5.2.17. Sample Number: Identifying number assigned to the sample that generated Actual Exposure (field 9) for tracking purposes. Sites must ensure that the sample number does not identify the employee. Sites may use encrypted numbers. 5.2.18. Monitoring Date: The date on which the monitoring was conducted that generated the actual exposure level used in calculating the 8-hour TWA (MM/DD/YYYY). Use the date of the first day if the monitoring spans midnight. 5.2.19. Chemical: Free form text that identifies the chemical composition of the beryllium being monitored. 5.2.20. Engineering Controls: Free form text used to indicate type of engineering controls used with the Task (field 8). 5.2.21. PPC&E: Indicate whether personal protective clothing and equipment were used with the Task (field 8). 5.2.22. Respirator Protection: Indicate whether respiratory protection was used with the Task (field 8). 5.2.23. Respirator APF: Provide the Assigned Protection Factor for respiratory protection when it was used for the Task (field 8). The Assigned Protection Factor should be those endorsed in written respiratory protection program plans used to establish work site specific procedures. When no respirator is worn, use the value 1 for the assigned protection factor. 6. TABLE RELATIONSHIPS: All tables can be related to one another by concatenating the Site Code and Unique ID as a key. This will allow any records in any tables to be related to any other table. However, there will be some logical relationships that also exist. The Roster table is the driving source of the Registry. All medical surveillance, work history, and exposure/sampling data must match to a Roster table record via the Site Code/Unique ID key. If not, these records will be questioned and returned to the site for resolution. DOE-STD-1187-2007 30 The Medical Surveillance tables will not be related logically to the Work History or Activities and Exposure table, and there can be a many-to-one relationship from the Medical Surveillance tables to the roster. The Work History table will be logically related to the Roster by the Job Start and Stop Date(s) and the Year Employment Ended. A worker cannot have a Job Start Date or Job Stop Date that is later than the Year Employment Ended (i.e., they cannot be working on a job later than their employment existed). The Activities and Exposure table will relate logically to the Work History table in a many-to-one fashion by checking the Monitoring Date field with the time window of the Job Start and Job Stop dates. The Beryllium Data Center will also check that supporting Work History data have been submitted for every worker (i.e., every Site Code/Unique ID key) reported in the Roster or Activities and Exposure data. 7. REQUIRED FIELDS: Every record must contain the worker's Unique ID and Site Code. This will allow all the records on an individual worker to be linked. In addition to the Unique ID and Site Code, selected fields in all the data sets must be populated every time data are submitted. These fields are indicated by * in the tables.

QUALITY ASSURANCE: The Data Center performs edit and logic checks on the data as part of its quality assurance procedures. The unique identification number of a record submitted for the medical surveillance, work history and exposure data sets must match a unique identification number of a record in the Roster data set. The integrity of the Activities and Exposure Data Set is achieved by maintaining the chronological order of a worker’s job history. The Data Center will prepare a list of edit checks and furnish these to the data coordinator so that inconsistencies and errors can be resolved. Copies of the data files will be provided to the data coordinator for their review to determine if the tables are consistent with the information submitted. The Data Center will notify the Office of Illness and Injury Prevention Programs (HS-13) of errors data coordinators indicate are due to a systemic problem that requires management attention. HS-13 will notify DOE line management of the issue and seek their assistance in planning appropriate corrective actions. DOE-STD-1187-2007 A - 1 Appendix A – Frequently Asked Questions General Questions Q. – Where do I get the site code? A. – That is a number that is furnished to you by the Registry Data Center Q. – Will others be able to request and receive data I have submitted from my site? A. – No. Obtaining a copy of data that was submitted from other sites requires DOE approval. Q. – Can I get a copy of the list where numbers are assigned to each site? A. – No. As an extra step to help protect the identity and confidentiality of the workers, this list will be maintained at the Registry Data Center and will not be give to anyone else. Q. – Are self-identified beryllium workers to be included in the Registry? A. – Yes. Q. – Do I have to submit a value for all required fields? A. –If a record is submitted then all required fields in that record must be filled. If a required field contains a null it will be flagged as an error and returned to the site for resolution. If a value of “Not Applicable” or “N/A” is provided for a required field it will also be flagged as an error and returned. Roster Questions Q. – After the initial roster was submitted by January, 2002, do we submit all the roster records again every six months with the changes incorporated? A. – No. After the initial roster was submitted by January, 2002, all of those workers will be in the roster forever and there is no need to submit them again unless (1) you have detected that some of the data are in error and you wish to correct it, (2) a worker terminates/retires, or (3) a worker expires. Q. – At our site, it is common for an employee to jump from one employer to another. Do I fill out a roster record each time this occurs? A. – If this is an employee that you as a site are responsible for reporting into the Registry, then the answer is “YES.” DOE-STD-1187-2007 A - 2 Q. – We seldom get death certificates or any death information. What do we supply when we know the person has deceased? A. – Every effort should be made to get these data but if they are not obtainable, it is advisable to put “N/A” in the field and that will give the Registry an indication the person is deceased but the data are not available. Q. – Suppose an employee terminates from our company. How do I submit this to the Registry?

A. – In the next submission, provide a roster delete record (Status Code=D) for this person and a corresponding new record (Status Code=N) with all of the data fields populated as needed. Upon receipt, the roster table will be scanned for this person, the previous record will be deleted, and the newest submitted record will replace it. Medical Surveillance Questions Q. – If I have submitted a record for a LPT and discovered that the date in that record for that LPT is wrong, how do I correct it? A. – To correct the information for an LPT record the site should submit a delete record (Status Code=D) with the Site Code, Unique ID, LPT Date, and LPT result populated. A corresponding “new” record (Status Code=N) should be submitted at the same time with all fields populated with the correct information; this record will replace the previous (deleted) record. LPT data may contain up to 3 records with identical LPT dates. Therefore, each delete record will apply to only one record in the data table, and if the site wishes to delete multiple records it should supply the proper number of delete records. Q. – Sometimes a beryllium-associated worker will be provided a chest X-ray and refuse the LPT. Do we submit these values anyway? A. – Yes. Submit any test results requested by the Registry that the person may have. Work History Questions Q. – Due to security reasons, the job title cannot be provided. Is it acceptable to leave it blank? A. – It is required to have some value here, so a generalization is recommended so the field is not blank. This will give some indication of what the person was doing to become identified as a beryllium-associated worker. If your security organization has approved an unclassified code word, use that word. Q. – Are sites required to retrieve retrospective work history data for beryllium workers? DOE-STD-1187-2007 A - 3 A. – According to the rule, the answer is no, although these data would increase the value of the Registry and some sites have said they can do this easily and will do so. Activities and Exposure Questions Q. – Again, security concerns arise with combining data from the DOE Activities and Exposure table, particularly the fields Process, Operation, and Task. What should a site do in this case? A. – Generalizations are recommended for the values in these fields that allow the Registry to have data that are as detailed and complete as possible without breaching security restrictions. Each site has to assess their own situation and develop a data policy/procedure they are comfortable with, ensuring that security is not compromised. Q. – The Sample Number field can be traced to an individual. To protect confidentiality, what should a site do? A. – Notice that this field is not required, but some sites asked/recommended that it be included to make it easier to search samples for specific values or to answer questions that may arise from these data. Most sites have procedures to maintain confidentiality of sampled individuals. If a site needs to use some form of encryption, that is acceptable. This field is there primarily for the site’s use. Q. – Is there a limit to the amount of text that can be supplied for the Process field? A. – No, the field is virtually limitless. DOE-STD-1187-2007 B -1 Appendix B – Chronic Beryllium Disease Definition The following definition of chronic beryllium disease is provided by the Energy Employees Occupational Illness Compensation Program Act Of 2000, As Amended, 42 U.S.C. § 7384 et seq.

PART B—PROGRAM ADMINISTRATION § 7384L. Definitions for program administration (13)The term "established chronic beryllium disease" means chronic beryllium disease as established by the following: (A) For diagnoses on or after January 1, 1993, beryllium sensitivity (as established in accordance with paragraph (8)(A)), together with lung pathology consistent with chronic beryllium disease, including— (i) a lung biopsy showing granulomas or a lymphocytic process consistent with chronic beryllium disease; (ii) a computerized axial tomography scan showing changes consistent with chronic beryllium disease; or (iii) pulmonary function or exercise testing showing pulmonary deficits consistent with chronic beryllium disease. (8)(A) Beryllium sensitivity as established by an abnormal beryllium lymphocyte proliferation test performed on either blood or lung lavage cells. DOE-STD-1187-2007 C -1 Appendix C – Process-Operation-Task Examples PROCESS OPERATION TASK DRY MACHINING HARDINGE LATHE MACHINE PREP DRY MACHINING HARDINGE LATHE OPERATING LATHE DRY MACHINING HARDINGE LATHE CLEAN UP DRY MACHINING HARDINGE LATHE MAINTAIN EQUIPMENT DRY MACHINING BRIDGEPORT MILL MACHINE PREP DRY MACHINING BRIDGEPORT MILL OPERATING MILL DRY MACHINING BRIDGEPORT MILL CLEAN UP DRY MACHINING BRIDGEPORT MILL MAINTAIN EQUIPMENT POWDER OPERATIONS BERYLLIUM PLASMA SPRAYING POWDER/CHAMBER INSPECTION POWDER OPERATIONS BERYLLIUM PLASMA SPRAYING ATTACH/REMOVE CANISTERS POWDER OPERATIONS BERYLLIUM PLASMA SPRAYING LOAD SAMPLE POWDER OPERATIONS BERYLLIUM PLASMA SPRAYING SPRAY OPERATION POWDER OPERATIONS BERYLLIUM PLASMA SPRAYING BLOW DOWN POWDER OPERATIONS BERYLLIUM PLASMA SPRAYING PART TRANSFER ANALYSIS ICP BERYLLIUM ANALYSIS PREP STANDARDS ANALYSIS ICP BERYLLIUM ANALYSIS INSTRUMENT ANALYSIS ANALYSIS ICP BERYLLIUM ANALYSIS SAMPLE RECEIVING AND PREPARATION ANALYSIS ICP BERYLLIUM ANALYSIS DATA MANAGEMENT AND REPORTS ANALYSIS ICP BERYLLIUM ANALYSIS ANALYTICAL CHEMISTRY POWDER OPERATIONS BERYLLIUM PLASMA SPRAY OPERATIONS VACUUM PUMP MAINTENANCE POWDER OPERATIONS BERYLLIUM PLASMA SPRAY OPERATIONS TORCH MANIPULATOR MAINTENANCE ES&H SUPPORT SAMPLE COLLECTION TAKE AIR SAMPLES ES&H SUPPORT SAMPLE COLLECTION TAKE SWIPE SAMPLES ES&H SUPPORT SAMPLE COLLECTION TAKE VACUUM/BULK SAMPLES ES&H SUPPORT INSPECTION, EVALUATION, AND INVESTIGATION VERIFY ADMINISTRATIVE CONTROLS ES&H SUPPORT INSPECTION, EVALUATION, AND INVESTIGATION PERFORM GENERAL WALKTHROUGHS ES&H SUPPORT INSPECTION, EVALUATION, AND INVESTIGATION PERFORM PHYSICAL HAZARD EVALUATIONS ES&H SUPPORT INSPECTION, EVALUATION, AND INVESTIGATION EVALUATE ENGINEERING CONTROLS ES&H SUPPORT INSPECTION, EVALUATION, AND INVESTIGATION EVALUATE CHEMICAL HAZARDS ES&H SUPPORT EQUIPMENT MAINTENANCE CLEANING AND PACKAGING ES&H SUPPORT EQUIPMENT MAINTENANCE CALIBRATING, ADJUSTING, AND TROUBLESHOOTING ES&H SUPPORT SHORT-TERM HCP OPERATIONS SUPPORTING A LOW RESIDUAL RISK OPERATION ES&H SUPPORT SHORT-TERM HCP OPERATIONS SUPPORTING A MINIMAL RESIDUAL RISK OPERATION ES&H SUPPORT SHORT-TERM HCP OPERATIONS SUPPORTING A MEDIUM RESIDUAL RISK OPERATION CUSTODIAL/JANITORIAL EQUIPMENT DECON WET WIPING CUSTODIAL/JANITORIAL EQUIPMENT DECON STRIPCOAT REMOVE CUSTODIAL/JANITORIAL EQUIPMENT DECON HEPA FILTERED VACUUMING CUSTODIAL/JANITORIAL GENERAL DECON WET MOPPING CUSTODIAL/JANITORIAL GENERAL DECON STRIPCOAT REMOVE CUSTODIAL/JANITORIAL GENERAL DECON HEPA FILTERED VACUUMING DOE-STD-1187-2007 C -2 PROCESS OPERATION TASK

DECONTAMINATION GENERAL DECON APPLYING STRIPCOAT DECONTAMINATION GENERAL DECON SETTING UP/TEARING DOWN DECONTAMINATION GENERAL DECON REMOVING STRIPCOAT DECONTAMINATION GENERAL DECON WET MOPPING DECONTAMINATION GENERAL DECON WET WIPING DECONTAMINATION GENERAL DECON HEPA FILTERED VACUUMING DECONTAMINATION EQUIPMENT DECON SETTING UP / TEARING DOWN DECONTAMINATION EQUIPMENT DECON APPLYING STRIPCOAT DECONTAMINATION EQUIPMENT DECON REMOVING STRIPCOAT DECONTAMINATION EQUIPMENT DECON WET MOPPING DECONTAMINATION EQUIPMENT DECON WET WIPING DECONTAMINATION EQUIPMENT DECON HEPA FILTERED VACUUMING DECONTAMINATION LAUNDRY COLLECTING LAUNDRY DECONTAMINATION LAUNDRY WASHING/DRYING LAUNDRY DECONTAMINATION LAUNDRY FOLDING/STORING LAUNDRY DECONTAMINATION HEPA VACUUM MAINTENANCE CHANGE PAPERBAG, MAIN & MICRO FILTERS DECONTAMINATION HEPA VACUUM MAINTENANCE CHANGE ULPA/HEPA FILTERS DECONTAMINATION DRYER LINT COLLECTOR REMOVING LINT DECONTAMINATION DRYER LINT COLLECTOR CHANGING LINT BAG DECONTAMINATION OVERHEAD DECON WET WIPING DECONTAMINATION OVERHEAD DECON HEPA FILTERED VACUUMING GLOVEBOX MAINTENANCE INSPECTION TRANSFER GLOVEBOX INSPECTION GLOVEBOX MAINTENANCE INSPECTION PLASMA SPRAY CHAMBER GLOVEBOX INSPECTION GLOVEBOX MAINTENANCE GLOVE CHANGE TRANSFER GLOVEBOX GLOVE CHANGE GLOVEBOX MAINTENANCE GLOVE CHANGE PLASMA SPRAY CHAMBER GLOVEBOX GLOVE CHANG POWDER OPERATIONS BERYLLIUM PLASMA SPRAY MAINTENANCE TORCH MAINTENANCE POWDER OPERATIONS BERYLLIUM PLASMA SPRAY MAINTENANCE VACUUM PUMP MAINTENANCE POWDER OPERATIONS BERYLLIUM PLASMA SPRAY MAINTENANCE POWDER HOPPER MAINTENANCE POWDER OPERATIONS GLOVEBOX MAINTENANCE INSPECTION POWDER OPERATIONS GLOVEBOX MAINTENANCE GLOVE CHANGE PARTICULATE CONTAINER HANDLING CYCLONE CONTAINER CHANGE-OUT REMOVING/INSTALLING CONTAINER PARTICULATE CONTAINER HANDLING CYCLONE CONTAINER CHANGE-OUT POST OPERATION CLEAN-UP PARTICULATE CONTAINER HANDLING DUST COLLECTOR CANISTER CHANGE-OUT REMOVING/INSTALLING CONTAINER PARTICULATE CONTAINER HANDLING DUST COLLECTOR CANISTER CHANGE-OUT POST OPERATION CLEAN-UP FACILITY OPERATIONAL SUPPORT SHORT TERM HCP RESIDUAL RISK MEDIUM FACILITY OPERATIONAL SUPPORT SHORT TERM HCP RESIDUAL RISK LOW FACILITY OPERATIONAL SUPPORT SHORT TERM HCP RESIDUAL RISK MINIMAL FACILITY OPERATIONAL SUPPORT ROUTINE MAINTENANCE FACILITY OPERATIONAL SUPPORT ROUTINE INSPECTION INSPECTING SAFETY SHOWERS & EYEWASH FACILITY OPERATIONAL SUPPORT ROUTINE INSPECTION INSPECTING FIRE EXTINGUISHERS FACILITY OPERATIONAL SUPPORT ROUTINE INSPECTION INSPECTING EMERGENCY LIGHTING FACILITY OPERATIONAL SUPPORT ROUTINE INSPECTION INSPECTING COMBUSTIBLE LOADING ENVIRONMENTAL SAMPLING BERYLLIUM PRECISION MACHINE SHOP EDM MACHINING FACILITY OPERATIONAL SUPPORT ROUTINE SURVEILLANCE & CALIBRATION SURVEYING HVAC SYSTEM PID/PDIP DOE-STD-1187-2007 C -3 PROCESS OPERATION TASK FACILITY OPERATIONAL SUPPORT ROUTINE SURVEILLANCE & CALIBRATION SURVEYING LOCAL VENTILATION ALARMS ELECTRICAL SERVICE/INSTALLATION/REPAIR SERVICE ELECTRICAL SERVICE/INSTALLATION/REPAIR INSTALL ELECTRICAL SERVICE/INSTALLATION/REPAIR REPAIR ELECTRICAL SERVICE/INSTALLATION/REPAIR SCOPE WORK TICKET CONSTRUCTION/MAINTENANCE OPERATIONS GENERAL MAINTENANCE WELDING PIGMA WELDING WELDING LEAK CHECK WELDING RESTRAINED BEND WELDING MAINTENANCE DOE-STD-1187-2007 D -1 Appendix D –Laboratory Reporting Limit

The American Industrial Hygiene Association defines the laboratory reporting limit as “The lowest concentration of analyte in a sample that can be reported with a defined, reproducible level of certainty.”2 Laboratories typically report a result of “Less Than (reporting limit value)” when sample results are below the reporting limit. Such a result might be reported as “Less Than 0.028 µg” for the sample. In the case of air samples collected on a filter medium, laboratories would typically divide their reporting limit by the sample volume to calculate a concentration result. For instance, the result reported to the Registry would be “Less Than 0.028 µg/m3” if the sample volume is 1,000 liters (or 1 m3). This concentration value is the “Actual Exposure” value required by the Registry (table 5.2, field 9) when a result is less than the reporting limit. Laboratory quality assurance programs generally calculate three limits: 1) an instrument detection limit based on analyses of blank samples, which establishes a value that is not likely to be a blank; 2) a method detection limit based on analyses of spiked samples, which establishes a value at which a specified level of precision and accuracy is achieved; and 3) a reporting limit, which accounts for variation in method detection limits due to factors such as differing filter media and interference from other metals in samples. Industrial hygienists monitoring beryllium exposures should inform the laboratory of their data quality objectives to avoid reporting limits that are higher than expected. One goal of the Registry is to determine whether compliance with the DOE action level is protective. The sampling and analytical methods used should be capable of demonstrating exposures are less than that level. 2 AIHA Laboratory Quality Assurance Programs (LQAP) Policy Document – Module 9, Revision 4: January 2, 2007. http://www.aiha.org/1documents/lab/Policy%20Module9_R4_Final_2007_01_02.pdf. Accessed 02/28/2007 DOE-STD-1187-2007 E -1 Appendix E - Calculating Non-Standard Shift and Sequential Sample 8-Hour TWA The conversion of actual exposure levels to an 8-hour TWA is a key standardizing step in the interpretation of exposure monitoring data. Calculations are simple when a worker has worn a sampler for the entire duration of their potential exposure in a shift. The actual exposure level is multiplied by the number of minutes worn and divided by 480 minutes in 8 hours. The 8-hour TWA for full shift sample results that are less than the reporting limit are calculated in the same way. When the 8-hour TWA is calculated from sequential samples in the same work shift, each sample receives a separate record and the calculated 8-hour TWA is recorded next to each actual value used to calculate that 8-hour TWA. When calculating an 8-hour TWA from sequential samples in the same work shift that are a mix of results that are greater than and less than the reporting limit, substitute the reporting limit for values less than the reporting limit. The calculated 8-hour TWA will be above the reporting limit. For example, with two results above the reporting limit and one less than the reporting limit (RL): (Value1 x TimeV1) + (Value2 x TimeV2) + (RL1 x TimeRL) = 8-hour TWA 480 minutes

Assume a worker's exposure was unmeasured for 15 minutes at the beginning of the shift while donning clean work clothing and for 30 minutes at the end of a shift while showering and donning street clothes. Also assume that the worker was monitored for a 225 minute period with a result of 0.1 μg/m3 and for a 210 minute period with a result of less than the reporting limit of 0.03 μg/m3. If the unmeasured periods are judged to have no potential for beryllium exposure, the 8-hour TWA would be: (0.1 x 225) + (0.03 x 210) = 0.06 μg/m3 480 CONCLUDING MATERIAL Review Activity: Headquarters Offices Environmental Management Fossil Energy Health Safety and Security National Nuclear Security Administration Nuclear Energy Science Field and Operations Offices Chicago Operations Office Idaho Operations Office Oak Ridge Operations Office Office of River Protection NNSA Service Center Richland Operations Office Savannah River Operations Office Area and Site Offices Argonne Area Office Brookhaven Area Office Fermi Area Office Kansas City Site Office Livermore Site Office Los Alamos Site Office Nevada Site Office Pantex Site Office Savannah River Site Office Sandia Site Office Y-12 Site Office National Laboratories Ames Laboratory Argonne National Laboratory Brookhaven National Laboratory Fermi National Accelerator Laboratory Lawrence Berkeley National Laboratory Lawrence Livermore National Laboratory Los Alamos National Laboratory Oak Ridge National Laboratory National Energy Technology Laboratory Pacific Northwest National Laboratory Sandia National Laboratories Facilities East Tennessee Technology Park Hanford Site Kansas City Plant Knolls Atomic Power Laboratory Nevada Test Site Oak Ridge Institute for Science and Education Pantex Plant Savannah River Site Stanford Linear Accelerator Center Y-12 National Security Complex Preparing Activity: DOE-HS-13 Project Number: SAFT-0111