| Literature DB >> 32483871 |
Liu Yang1, Crystal Weston2, Curtis Cude2, Laurel Kincl1.
Abstract
BACKGROUND: The Oregon Occupational Public Health Program (OOPHP) monitors occupational health indicators (OHIs) to inform occupational safety and health (OSH) surveillance. In 2018, OOPHP evaluated the performance of the OSH surveillance system and identified areas for future improvement.Entities:
Keywords: occupational health indicators; occupational safety and health surveillance; surveillance evaluation
Mesh:
Year: 2020 PMID: 32483871 PMCID: PMC7383881 DOI: 10.1002/ajim.23139
Source DB: PubMed Journal: Am J Ind Med ISSN: 0271-3586 Impact factor: 2.214
Key data sources and corresponding occupational health indicators (OHIs)
| Data source | Corresponding OHIs |
|---|---|
| Hospital Discharge (HD) data | Work‐related hospitalizations |
| Hospitalization for work‐related burns | |
| Hospitalization from or with pneumoconiosis | |
| Work‐related low‐back disorder hospitalizations | |
| Workers' Compensation (WC) data | WC claims for amputation with lost work‐time |
| WC claims for carpal tunnel syndrome with lost work‐time | |
| Adult Blood Lead Epidemiology and Surveillance (ABLES) data | Elevated blood lead levels among adults |
Approaches for evaluating surveillance attributes
| Attribute | Definition | Evaluation measure | Evidence collection method | Evidence collected/data analysis |
|---|---|---|---|---|
| System performance | ||||
| Simplicity | Structure and ease of operation to perform its stated objectives | (1) Data sources needed |
| Types & number of data sources needed |
| (2) Ease of obtaining and processing data |
| Work process | ||
| (3) Ease of event/case ascertainment |
| Rating of ease; possible challenges/problems | ||
| (4) Number of organizations requiring data reports |
| Types of data reporting & number of organizations | ||
| Flexibility | Ability to adapt to operating conditions or informational changes with little additional time, personnel, or funds | (1) Whether the system accommodates updates and changes in OHI methodology? |
| Past examples; potential changes and the system's preparation |
| (2) Whether it accommodates other changes (eg, funding, data sources, technologies and standards, policies and regulation, emerging OSH issues)? |
| Past examples; potential changes and challenges; the system's preparation; resources available | ||
| Acceptability | The willingness of persons and organizations to participate in the surveillance system | (1) Willingness of stakeholders to collaborate with the program |
| Rating of willingness; possible barriers & problems |
| (2) Stakeholders awareness of the OSH surveillance system's objectives |
| Summarize statistics | ||
| (3) Stakeholders' participation in program activities |
| Participation rate; collaboration process & collaborators’ responsiveness | ||
| Timeliness | The speed between steps in a public health surveillance system | (1) The time gap between the occurrence of a case/event and the report of OHI |
| Time gap (in month/year); possible reasons & barriers |
| (2) The amount of time spent for each working step in the system |
| Time spent for each step in the logic model; possible reasons & barriers | ||
| (3) Stakeholders' perspectives on the time lag |
| Stakeholders' perspectives; discuss OHIs/events that should/could be tracked more timely | ||
| Stability | System's reliability (without failure) and availability | (1) Little or no failure in operating the system |
| Working environment and infrastructure; past serious failures and possible current issues |
| (2) Being operational when needed | ||||
| System's sustainability | (3) Financial resources (funding support) |
| Possible issues with funding & other resources; availability for continuous resources and support | |
| (4) Other resources (human, technical, leadership support) to sustain the system | ||||
| Data quality (for key data sources) | ||||
| Data quality | Completeness and validity of the data | (1) Data validity (is the case/event correctly measured what it is intended to measure?) |
| Possible validity issues |
| (2) The completeness of the source data (less % of "unknown" or "blank" responses) |
| Completeness rate if possible; possible issues | ||
| (3) Data quality control process in place to monitor errors/avoid missing data |
| Data quality control process & problems | ||
| Sensitivity | The proportion of cases/events detected by the surveillance system | (1) The proportion of cases/events detected by each OHI |
| Report quantitative data if possible; potential issues |
| The ability to monitor changes in the number of cases over time | (2) Ability to monitor changes over time |
| Past examples; key staff's perspective | |
| (3) Any active surveillance approaches used |
| Active surveillance approaches & their effects on sensitivity | ||
| Predictive value positive (PVP) | The proportion of true cases among all reported cases | (1) The proportion of true cases among all reported cases |
| Report quantitative data if possible; potential issues |
| (2) Approaches for confirming true cases |
| Approaches & their effects on PVP | ||
| Representativeness | The ability of the surveillance system to accurately describe the occurrence and distribution of a health‐related event by time, place, and person | (1) Is denominator used appropriately for OHIs to match numerator? |
| Possible issues with the choice of denominators |
| (2) Is there any subpopulation excluded from the OHI? |
| Subpopulations potentially excluded; Statistics whenever possible | ||
| Overall usefulness | ||||
| Usefulness | Contribute to the prevention and control of adverse occupational health conditions | (1) Contribute to the prevention and control of adverse occupational health events and to an improved understanding of the public health implications of such events |
| Ways to use OHI data; ways to promote dissemination & usage |
| (2) Relevance & significance of the system's objectives and activities to the OSH needs to be perceived by stakeholders |
| Stakeholders’ ratings & comments | ||
| (3) Overall usefulness of the surveillance system perceived by stakeholders |
| Stakeholders’ ratings & comments | ||
Abbreviations: OHI, occupational health indicator; OSH, occupational safety and health.
Document/literature review; interview; focus group; survey questionnaire; onsite observation.
Data collection methods and corresponding stakeholders and attributes
| Evidence collection method | Stakeholder group | Level of involvement | Format | Targeted attributes | Participated | Participation rate (%) |
|---|---|---|---|---|---|---|
|
| Higher level supporting leaders | Level 3 | Phone call | Stability, Usefulness | 3 | 100 |
| Key OSH surveillance staff | Level 1 | In‐person | Simplicity, Flexibility, Acceptability, Timeliness, Stability, Data quality, Sensitivity, PVP, Representativeness, Usefulness | 1 | 100 | |
| Key data source provider | Level 2 | In‐person/phone call | Flexibility, Timeliness, Stability, Data quality, Sensitivity, PVP, Representativeness | 4 | 100 | |
|
| Management and key personnel | Level 1 | In‐person | Flexibility, Timeliness, Stability, Usefulness | 7 | 87.5 |
|
| Management and key personnel | Level 1 | Online | Flexibility, Acceptability, Timeliness, Stability, Usefulness | 6 | 75 |
| External experts | Level 2 | Online | Flexibility, Acceptability, Timeliness, Stability, Usefulness | 4 | 25 | |
| All other stakeholders | Level 3 | Online | Acceptability, usefulness | 4 | 36.4 | |
|
| … | … | Working documents/published literature | Simplicity, Flexibility, Acceptability, Timeliness, Data quality, Sensitivity, PVP, Representativeness | / | / |
|
| … | … | Onsite | Timeliness, Stability | / | / |
Abbreviations: OSH, occupational safety and health; PVP, predictive value positive.
Evaluation results for performance attributes
| Attributes | Evaluation measure | Evidence collected | Assessment | Overall evaluation |
|---|---|---|---|---|
| Simplicity | (1) Data sources needed |
>15 secondary data sources needed No data reporting & recording components | Very simple | Very simple |
| (2) Ease of obtaining and processing data |
Obtain only aggregated data for 60% OHIs Five data sources (including the three key data sources) involve straightforward data processing | Easy and straightforward | ||
| (3) Ease of event/case ascertainment |
Average rating of ease by key staff: 3.7 of 5‐point scale (5 represents the easiest), with 13 OHIs rated 4 or 5 Six out of the 24 OHIs under surveillance were rated below 3, with difficulties related to data interpretation, meticulousness in data processing, etc | Easy | ||
| (4) Number of organizations requiring data reports |
Only the grant office requiring reports | Very simple | ||
| Flexibility | (1) Accommodates updates and changes in OHI methodology |
Adapts changes in OHI annual guide very well, such as adding new OHIs and using alternative data sources | Very flexible | Flexible |
| (2) Whether it accommodates other changes |
Leadership is an awareness of new trends and challenges Past examples attempted to respond to local OSH surveillance needs | Has the potential to adapt changes | ||
| Acceptability | (1) Willingness of stakeholders |
Average willingness rating was 4.8 86% participants chose “very willing” (rating 5) | Very willing | Highly accepted |
| (2) Stakeholders’ awareness of the system's objectives |
93% participants were aware of the system's objectives | Stakeholders held positive perspectives towards the system | ||
| (3) Stakeholders' participation |
Average attendance rate in advisory committee board meetings was 60% Stakeholders were responsive in work collaboration | Good | ||
| Timeliness | (1) The time gap of OHIs |
2‐3 years lag | Not timely | Not timely |
| (2) The amount of time for working steps |
Data collection and report process was timely Dissemination speed cannot be assessed as little dissemination work done | Timely | ||
| (3) Stakeholders' perspectives |
70% participants accepted the time lag; OHIs limited in their usability being lagging indicators; | Fair, but limited in usability | ||
| Stability | (1) Reliability |
Able to produce OHIs efficiently and effectively | Very stable | Stable |
| (2) Availability |
Able to generate products when needed | High availability | ||
| (3) Financial resources |
Funding a big concern for sustainability; NIOSH seemed to be the only funding source The competitive research application proposal is challenging | Lack of long‐term funding security | ||
| (4) Other resources |
Received support from its housing agencies and partners All stakeholders are very willing to collaborate with the program | Good |
Abbreviations: NIOSH, National Institute for Occupational Safety and Health; OHI, occupational health indicator; OSH, occupational safety and health.
Evaluation results for data quality attributes
| Attribute | Evaluation measure | HD data | WC data | ABLES data | Average score | |||
|---|---|---|---|---|---|---|---|---|
| Evidence collected | Score | Evidence collected | Score | Evidence collected | Score | |||
| Data quality | (1) Data validity |
Key definitions were scientifically sound | 5 |
Key definitions were scientifically sound; Some variables (eg, injury date) were not precise for chronic injuries and illnesses. | 4 |
BLL was confirmed by lab test | 5 | 4.7 |
| (2) Completeness |
Missing rate in “primary payer” was considered to be low Literature concerned on miscoding & omission of comorbidities, which may affect three of the four associated OHIs | 4 |
Missing rates were 0% for injury nature, up to 4% for injury event in 2016‐2017; | 5 |
Missing rate of some variables (eg, age) was considered to be low Complete and correct residency information: 71% (among cases needing mail follow‐up, 2016‐2018 data) | 4 | 4.3 | |
| (3) Data quality control process |
Standard data quality controls Literature showed concerns with data quality control | 3 |
Formal internal quality control process for coding and check errors | 5 |
Standard data quality controls Follow‐up investigation helped to confirm/correct missing/wrong residency and other information | 4 | 4.0 | |
| Average score (data quality) | / | 4.0 | / | 4.7 | / | 4.3 | 4.3 | |
| Sensitivity | (1) True cases/events detected |
Certain hospitals were excluded WC under‐coverage & under‐reporting issue (see WC data section) Errors & misclassifications existed | 3 |
Certain populations were excluded Literature reported under‐reporting as a common problem, especially for illnesses | 3 |
Mandatory BLL testing facilitated case identification, but certain populations were excluded | 4 | 3.3 |
| (2) Monitor changes |
Coding changes caused “break‐in‐series” | 4 |
Coding changes caused “break‐in‐series” | 4 |
Definition changes caused misclassifications | 3 | 3.7 | |
| (3) Active surveillance approaches |
No active approach | 3 |
No active approach | 3 |
Follow‐up investigation could help to identify potential cases | 5 | 3.7 | |
| Average score (sensitivity) | … | 3.3 | … | 3.3 | … | 4.0 | 3.6 | |
| Predictive value positive (PVP) | (1) Proportion of true cases |
Misclassifications was a concern | 4 |
Insurers’ review was regarded as effective Misclassifications in data coding & entry were minimum | 5 |
Definition changes caused misclassifications (ie, false‐positive incidences) | 4 | 4.3 |
| (2) Approaches for confirming true cases |
No approach in place | 3 |
The insurers investigated cases for correct information | 5 |
Follow‐up investigation could help to correct errors | 5 | 4.3 | |
| Average score (PVP) | … | 3.5 | … | 5.0 | … | 4.5 | 4.3 | |
| Representativeness | (1) Is denominator used appropriately? |
Denominator/baseline populations match the numerators | 5 |
Denominator/baseline populations match the numerators | 5 |
Denominator/baseline populations match the numerators | 5 | 5.0 |
| (2) Any subpopulation excluded? |
Populations going to hospitals that were excluded from HD data Fewer hospital access in rural counties in Oregon may impact hospitalization decisions Populations living/working cross states border | 3 |
Populations excluded from Oregon WC coverage (see Sensitivity section) Populations tended not to fine WC claims | 3 |
Population with nonoccupational lead exposure (tracked in the OHI) Population living/working cross state borders | 4 | 3.3 | |
| Average score (representativeness) | … | 4.0 | … | 4.0 | … | 4.5 | 4.2 | |
| Average overall score | … | 3.7 | … | 4.3 | … | 4.3 | 4.1 | |
Abbreviations: ABLES, adult blood lead epidemiology and surveillance; BLL, blood lead level; HD, hospital discharge; OHI, occupational health indicator; WC, workers’ compensation.
Evaluation results on the system's overall usefulness
| Attributes | Evaluation measure | Evidence collected | Assessment | Overall evaluation |
|---|---|---|---|---|
| Usefulness | (1) Contribute to the prevention and control of adverse occupational health events and to an improved understanding of the public health implications of such events; |
Lack of active data dissemination Lack of data usage OHIs are useful in tracking state‐level trends but limited in guiding local OSH practices The system has created little outcomes and impacts | No significant outcomes & impacts | Not useful |
| (2) Relevance of system's activities to the OSH needs perceived by stakeholders |
Average rating was 4.1. | Relevant | ||
| (3) Overall usefulness of the surveillance system perceived by stakeholders |
Average rating was 3.0 Many stakeholders pointed out the importance of putting data into use | Moderate |
Abbreviations: OHI, occupational health indicator; OSH, occupational safety and health.