MétaCan
Menu
Back to cohort
Record W3048471045 · doi:10.2196/19533

A Web-Based, Mobile-Responsive Application to Screen Health Care Workers for COVID-19 Symptoms: Rapid Design, Deployment, and Usage

2020· article· en· W3048471045 on OpenAlexvenueno aff
Haipeng Zhang, Dimitar Dimitrov, Lynn Simpson, Nina Plaks, Balaji Singh, Stephen Penney, J. O. Charles, Rosemary R. Sheehan, Steven Flammini, Shawn N. Murphy, Adam Landman

Bibliographic record

VenueJMIR Formative Research · 2020
Typearticle
Languageen
FieldComputer Science
TopicCOVID-19 Digital Contact Tracing
Canadian institutionsnot available
Fundersnot available
KeywordsSoftware deploymentCoronavirus disease 2019 (COVID-19)Telemedicine2019-20 coronavirus outbreakWeb applicationSevere acute respiratory syndrome coronavirus 2 (SARS-CoV-2)Mobile deviceHealth careComputer scienceWorld Wide WebMedicineMedical emergencyVirologyOperating system

Abstract

fetched live from OpenAlex

BACKGROUND: As of July 17, 2020, the COVID-19 pandemic has affected over 14 million people worldwide, with over 3.68 million cases in the United States. As the number of COVID-19 cases increased in Massachusetts, the Massachusetts Department of Public Health mandated that all health care workers be screened for symptoms daily prior to entering any hospital or health care facility. We rapidly created a digital COVID-19 symptom screening tool to enable this screening for a large, academic, integrated health care delivery system, Partners HealthCare, in Boston, Massachusetts. OBJECTIVE: The aim of this study is to describe the design and development of the COVID Pass COVID-19 symptom screening application and report aggregate usage data from the first three months of its use across the organization. METHODS: Using agile principles, we designed, tested, and implemented a solution over the span of one week using progressively customized development approaches as the requirements and use case become more solidified. We developed the minimum viable product (MVP) of a mobile-responsive, web-based, self-service application using research electronic data capture (REDCap). For employees without access to a computer or mobile device to use the self-service application, we established a manual process where in-person, socially distanced screeners asked employees entering the site if they have symptoms and then manually recorded the responses in an Office 365 Form. A custom .NET Framework application solution was developed as COVID Pass was scaled. We collected log data from the .NET application, REDCap, and Microsoft Office 365 from the first three months of enterprise deployment (March 30 to June 30, 2020). Aggregate descriptive statistics, including overall employee attestations by day and site, employee attestations by application method (COVID Pass automatic screening vs manual screening), employee attestations by time of day, and percentage of employees reporting COVID-19 symptoms, were obtained. RESULTS: We rapidly created the MVP and gradually deployed it across the hospitals in our organization. By the end of the first week, the screening application was being used by over 25,000 employees each weekday. After three months, 2,169,406 attestations were recorded with COVID Pass. Over this period, 1865/160,159 employees (1.2%) reported positive symptoms. 1,976,379 of the 2,169,406 attestations (91.1%) were generated from the self-service screening application. The remainder were generated either from manual attestation processes (174,865/2,169,406, 8.1%) or COVID Pass kiosks (25,133/2,169,406, 1.2%). Hospital staff continued to work 24 hours per day, with staff attestations peaking around shift changes between 7 and 8 AM, 2 and 3 PM, 4 and 6 PM, and 11 PM and midnight. CONCLUSIONS: Using rapid, agile development, we quickly created and deployed a dedicated employee attestation application that gained widespread adoption and use within our health system. Further, we identified 1865 symptomatic employees who otherwise may have come to work, potentially putting others at risk. We share the story of our implementation, lessons learned, and source code (via GitHub) for other institutions who may want to implement similar solutions.

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 distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.965
Threshold uncertainty score0.925

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.091
GPT teacher head0.425
Teacher spread0.335 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designOther design
Domainnot available
GenreEmpirical

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".

Quick stats

Citations38
Published2020
Admission routes1
Has abstractyes

Explore more

Same venueJMIR Formative ResearchSame topicCOVID-19 Digital Contact TracingFrench-language works237,207