Alternatives to sharing COVID-19 data with law enforcement: Recommendations for stakeholders
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
During the COVID-19 pandemic, in some jurisdictions, police have become involved in enforcing coronavirus-related measures. Relatedly, several North American jurisdictions have established COVID-19 data sharing protocols with law enforcement. Research across a range of fields has demonstrated that involving police in matters of public health disproportionately impacts the most vulnerable and does more harm than good. This is reflected in the consensus against COVID-19 criminalization that has emerged among civil society organizations focused on HIV, human rights, and harm reduction. The European Data Protection Board has also released guidelines against re-uses of COVID-19 data for law enforcement purposes. This article offers an overview of the harms of criminalizing illnesses and strategies for health stakeholders to seek alternatives to sharing COVID-19 data with police agencies while facilitating interoperability with healthcare first responders. It also presents case studies from two North American jurisdictions - Ontario and Minnesota - that have established routine COVID-19 data sharing with police. We recommended seven alternatives, including designating COVID-19 data as sensitive and implementing segmented interoperability with first responder agencies. These guidelines can help ensure that health information technology platforms do not become vehicles for the criminalization of COVID-19, and that health data stay within the health system.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 it