Automatic Work-Hours Recorder for Medical Staff (Staff Hours): Mobile App Development
Bibliographic record
Abstract
BACKGROUND: There are numerous mobile apps for tracking work hours, but only a few of them record work hours automatically instead of relying on manual logging. No apps have been customized for medical staff, whose work schedules are highly complicated as they have both regular hours and on-call duties. OBJECTIVE: The specific aims of this study were to (1) identify the Staff Hours app users' GPS-defined work hours, (2) examine the overtime work hours from the app-recorded total work hours and the participants' self-reported scheduled work hours, and (3) compare these app-recorded total work hours among different occupations. METHODS: We developed an app, Staff Hours, to automatically calculate a user's work hours via GPS background data. Users can enter their scheduled hours, including regular hours and on-call duties. The app automatically generates overtime reports by comparing the app-recorded total work hours with the user-defined scheduled hours. A total of 183 volunteers (60 females and 123 males; mean age 32.98 years, SD 6.74) were included in this study. Most of the participants (162/183, 88.5%) were medical staff, and their positions were resident physicians (n=89), visiting staff (n=38), medical students (n=10), registered nurses (n=25), and non-health care professionals (non-HCPs; n=21). RESULTS: The total work hours (mean 55.69 hours, SD 21.34) of the 183 participants were significantly higher than their scheduled work hours (mean 50.67 hours, SD 21.44; P=.01). Medical staff had significantly longer total work hours (mean 57.01 hours, SD 21.20) than non-HCPs (mean 45.48 hours, SD 20.08; P=.02). Residents (mean 60.38 hours, SD 18.67) had significantly longer work hours than visiting staff (mean 51.42 hours, SD 20.33; P=.03) and non-HCPs (mean 45.48 hours, SD 20.08; P=.004). CONCLUSIONS: Staff Hours is the first automatic GPS location-based app designed for medical staff to track work hours and calculate overtime. For medical staff, this app could keep complete and accurate records of work hours in real time, reduce bias, and allow for better complying with labor regulations.
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.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.005 | 0.004 |
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".