COVID-19 Vaccine Hesitancy in Canada: Content Analysis of Tweets Using the Theoretical Domains Framework
Bibliographic record
Abstract
BACKGROUND: With the approval of two COVID-19 vaccines in Canada, many people feel a sense of relief, as hope is on the horizon. However, only about 75% of people in Canada plan to receive one of the vaccines. OBJECTIVE: The purpose of this study is to determine the reasons why people in Canada feel hesitant toward receiving a COVID-19 vaccine. METHODS: We screened 3915 tweets from public Twitter profiles in Canada by using the search words "vaccine" and "COVID." The tweets that met the inclusion criteria (ie, those about COVID-19 vaccine hesitancy) were coded via content analysis. Codes were then organized into themes and interpreted by using the Theoretical Domains Framework. RESULTS: Overall, 605 tweets were identified as those about COVID-19 vaccine hesitancy. Vaccine hesitancy stemmed from the following themes: concerns over safety, suspicion about political or economic forces driving the COVID-19 pandemic or vaccine development, a lack of knowledge about the vaccine, antivaccine or confusing messages from authority figures, and a lack of legal liability from vaccine companies. This study also examined mistrust toward the medical industry not due to hesitancy, but due to the legacy of communities marginalized by health care institutions. These themes were categorized into the following five Theoretical Domains Framework constructs: knowledge, beliefs about consequences, environmental context and resources, social influence, and emotion. CONCLUSIONS: With the World Health Organization stating that one of the worst threats to global health is vaccine hesitancy, it is important to have a comprehensive understanding of the reasons behind this reluctance. By using a behavioral science framework, this study adds to the emerging knowledge about vaccine hesitancy in relation to COVID-19 vaccines by analyzing public discourse in tweets in real time. Health care leaders and clinicians may use this knowledge to develop public health interventions that are responsive to the concerns of people who are hesitant to receive vaccines.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.009 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.005 | 0.010 |
| Science and technology studies | 0.005 | 0.002 |
| Scholarly communication | 0.004 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".