Resources

I have an employee that will be added to the roster for BAWR, but he says that he thinks he is already on the registry from a previous site where he was employed. Is there a way for us to verify he is in the program so that we do not duplicate his entry into the registry?

The employee will need to be added to the organization’s roster and assigned a unique id for that site. One of the fields on the roster table is “Previous Site”. That field would be the site of the employee’s previous employment. Another field is “Old Unique ID”. The employee will need to reach out to the Beryllium coordinator at the previous employer to determine the ID number. If there are several subcontractors involved and multiple data coordinators it could be difficult to obtain. Most of the time, individuals do not reach out to get previous ID numbers. There is no need to worry if this number cannot be obtained. The BAWR Team is aware of these types of situations.

If an individual is still employed but changes job titles (laborer to truck driver) and is no longer in the beryllium monitoring program, do I update the work history to show the “job stop date?” I know he is still an “associated worker.”

Yes, that is correct.

I am working on our data submission. We were assigned a site code by the BAWR Team. The work history tab requires an "Organization Code," but I am not sure what to put there. The instructions indicate that the registry data coordinator should provide a data dictionary to the data Center.

There is an accompanying standard that outlines each one of the fields for the tabs. It can be found here: Beryllium-Associated Worker Registry Data Collection and Management Guidance. The particular field mentioned above is specific to whichever organization or department that the employee falls under. For example, HVAC or Nuclear Services Department.

When does the registry consider a Beryllium worker to be sensitized? Is it by actual date of abnormal BeLPT or by date of registry submission of that abnormal test?

A worker is considered sensitized if any one of the following clinical criteria and incidence rules for the case definition of beryllium sensitizations is met. Often, a worker’s data will satisfy multiple criteria, and their date of sensitization is calculated as the earliest date any one of these conditions is met.

• 2 positive or abnormal beryllium proliferation test (BeLPT) results (based on 2 separate blood draws).
• 1 positive or abnormal plus 2 (or more) borderline BeLPT results.
• A positive or abnormal bronchoalveolar lavage (BAL) result.
• CBD evaluation with a finding of sensitization but no chronic beryllium disease (CBD).

Dates are based on when the individual was tested and are not based on when the results were reported to the Registry.

Does the registry roster include all personnel in the BAWR program or just the individuals that had exams during the six-month period?

The roster should include any new individuals to the program or employees who have had changes to the information in the roster (left the company, employment ended, etc).

We have an employee that started work at our site after we were no longer engaged in any Be work. Because of this individual’s position as a radiological control technician (RCT), they were assigned the marker for Be workers that was normally assigned to all RCTs regardless of their actual exposure to Be. We have put measures in place to stop this practice; however, we now have an individual that was incorrectly identified as a Be-associated worker and who dutifully reported to medical for initial screening and was reported to the ORISE BAWR. This worker no longer wishes to be kept on the list, complete Be training, and is declining screening for the remainder of their career. How do we remove them from the roster?

It is not possible to remove someone from the registry, but they can be marked inactive. To do this, simply ensure that there is an entry for “date of last beryllium job.” You can either use the start date since he supposedly never did perform a beryllium job, or you can add some other reasonable date. That will flag this entry for the BAWR Registry Team so that we know to make it inactive.

I am now the data coordinator for another site in the BAWR program. Previously, when submitting data, I submitted a separate spreadsheet for “terminations” and have not received any “error” reports for that. Is it OK if I continue to submit that way or do you want terminations added to the Roster spreadsheet?

As you see, each site has a slightly different way of reporting data. You can report terminations on their own data tab; however, we would prefer that they are added to the roster as you suggested.

As a reminder, for updates to roster records, there need to be two records, one that is N (new/update) and one that is D (delete).

Here is the relevant section in the Standard:

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 13 DOE-STD-1187-2019 data for the worker.

The unique ID should remain the same each period for the workers, is this correct?

Yes, the unique ID should remain constant for the individual.

Who is responsible for reporting to the Registry, the employer or the provider who did the medical surveillance?

It is the “responsible employer” according to the regulation.