Beryllium-Associated Worker Registry

1. Beryllium-AssociatedWorker Registry May 24, 2016 2:00-3:00 p.m. (EDT) Or May 25, 2016 9:00-10:00 a.m. (EDT)

2. Beryllium-Associated Worker Registry Data Coordinator Role, Turnover, and Data Submissions Dr. Cliff Strader May 24/25, 2016

3. DATA COORDINATOR ROLE • Absolutely central to program success • Collects, organizes, transmits data • Interacts with data center • Quality assurance follow-up • Establishes primary POC for reporting organization

4. REPORTING ORGANIZATIONS WITH DATA COORDINATOR CHANGES

5. IMPLICATIONS OF HIGH DATA COORDINATOR TURNOVER • Poor understanding ofrequirements & expectations • Repeated need for training drains resources, takes time • Data quality can suffer • Can delay data submissions

6. DATA SUBMISSIONS • Reporting is required by 10 CFR 850[ section 850.39 (g) ] • Due by end of January & end of July • Communication – Please let the Data Center know if you’re having specific problems, establish an ETA • Late data submissions producecascade of delays

7. Beryllium-Associated Worker Registry Roster Construction Deb Sweeney May 24/25, 2016

8. Construction of Rosters • Who Should Be Included (10 CFR 850.3): • Current workers exposed or potentiallyexposed to beryllium at a DOE facility • Workers who self-identify and indicate a past history of possible exposure • Workers who exhibit signs or symptoms of beryllium exposure OR are receiving medical removal protection benefits

9. Construction of Rosters • Who Should Be Included: • “Once in the Registry, Always in the Registry” – the health impact of beryllium exposure may not occur until many years later • Being in the Registry is NOT Voluntary – an employee can not opt out of the Registry • The Registry is not tied to Worker Compensation

10. Construction of Rosters • Who Should Be Included – Other Considerations: • Site’s Chronic Beryllium Disease Prevention Program (CBDPP) • How the site handles “transferred” or “loaned” workers • How the site handles former workers (especially from closure sites like Rocky Flats)

11. Construction of Rosters • How to Manage Your Roster: • The Roster is the cornerstone • Inclusion in the Roster is not dependent on whether an employee has had medical monitoring • However, all employees who have been BeLPT testedshould be included in the Roster and their results should be reported • Assure employees with Normal BeLPTs are included • Report all BeLPT results

12. Construction of Rosters • How to Manage Your Roster: • Inclusion in the Roster is not dependent on whether an employee has been exposure monitored • However, all employees who have been exposure monitoredshould be included in the Roster and their results should be reported • Assure that employees with non-detects are included • Report all personal sampling results

13. Construction of Rosters • How to Manage Your Roster: • Regarding employees who have transferred from another DOE site, every effort should be made to populate Previous Site • Provides valuable information, particularly if the worker received their exposure at another site • When an employee has termed, populate Year Employment Ended • As the Registry ages, reporting on the current worker subset is relevant

14. Construction of Rosters • Roster Fields – “Death” fields are dropped in the new guidance.This is what you need to concentrate on: • Site Code: assigned by the Data Center • Unique ID: a unique encrypted employee identifier (encryption key is held by the reporting organization) • Status Code: N(ew) or D(elete) • Year Born: year of birth (YYYY format) • Gender: M(ale) or F(emale)

15. Construction of Rosters • Roster Fields(continued): • Employer Type: F(ederal), C(ontractor), S(ubcontractor), or V(isitor) • First Hire on Site Date: date the employee was first hired to work at the current site (MM/DD/YYYY format) • Year Employment Ended: year employment terminated (YYYY format) – null means currently employed

16. Construction of Rosters • Roster Fields(continued): • Previous Site: name of the previous site where the worker was employed as a beryllium worker or had the potential for exposure to beryllium • Old Unique ID: Unique ID from previous site, if at all possible

17. Beryllium-Associated Worker Registry Exposure Sampling Data and Survey Results Eric Adams May 24/25, 2016

18. Exposure Sampling Data • Complete Picture: • Submit All Available Records: both detects and non-detects for all employees in the roster • Add To Roster: if exposure monitoring records or a BeLPT exists for employees not already in the registry • No Reason To Stop Including: new exposure monitoring data to be submitted, regardless of BeS/CBD status or BeLPT results

19. Exposure Sampling Data • Retrospective Data: • Historical Data: submit records held back for QA or other purposes, if it exists submit it • “Transferred”/“Loaned” Workers: people who move sites need to be added to the roster if they were a beryllium worker at the prior site, and populate the previous site field and ID if possible

20. Exposure Sampling Data • Additional Data: • Data Completeness: want as comprehensive and complete a view as possible • Multiple Records: same day multiple exposure records for one employee should still be submitted

21. Exposure Sampling Data • TWA QA: • Rolled Up Samples: non-detects > 0.2 rare to see, caused by multiple records • Irreconcilable TWAs: some can not be replicated with data submitted (exposure level and sampling time)

22. Survey Results • Survey: • Good Consistency: little data manipulation or accuracy changes to accredited lab results beyond understandable rounding • RL/LOQ/LOD Impact: investigating if variance is impactful

23. Beryllium-Associated Worker Registry Technical Standard Changes Phil Wallace May 24/25, 2016

24. Changes to DOE-STD-1187 • Data fields removed • Roster (table 3) • Race • Death date • Immediate cause • First cause • Second cause • Other cause • Smoking (table 4) – entire table removed • More data fields required • Work History (table 5) • Organization code • Beryllium job start date

25. Changes to DOE-STD-1187 • Will be effective for the January 2017 submission • New requirement data elements not retroactive • Document will be placed in REVCOM soon • Draft copy will be distributed after today’s webinar

26. Beryllium-Associated Worker Registry Data Analyses Dr. Cliff Strader May 24/25, 2016

27. USING YOUR DATA • We encourage you to look at your data in more depth • Data Center can assist if needed • Within our resource limits, we can help conduct analyses specific to your own reporting organization

28. WORKERS WITH EXPOSURE SAMPLING AFTER DATE OF Be SENSITIZATION

29. Beryllium-Associated Worker Registry BAWR Web Front End Application Deb Sweeney May 24/25, 2016

30. BAWR Web Front-End Application • Getting a Facelift • Should be rolled out later this calendar year • Redesigned to be more inviting, user friendly, intuitive, and efficient • More consistent website and application navigation • Users will be able to navigate between the application section and the website home page without losing their session • By using icons as buttons, standardized navigation, etc., much of the text clutter will be eliminated and usability will be improved

31. BAWR Web Front-End Application • New Features • Users will be able to view/download a summary page with aggregate data for a single employee (i.e., Unique ID) • Use It!-https://apps.orau.gov/BAWR/ • Data views are current – users can view and download their data 24/7 • Contact the Data Center for Accounts/Passwords