|
| DOE-STD-1187-2005
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.
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
was 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).
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 are 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.
The Medical Surveillance tables are not 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 is related logically to the roster only by the Job Stop Date
and the Year Employment Ended. A worker cannot have a 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 relates 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 stop dates.
7. REQUIRED FIELDS: Every record must contain the worker's Unique ID and Site
Code. This allows all the records on an individual worker to be linked. In addition to
31
|
Privacy Statement - Press Release - Copyright Information. - Contact Us |