MétaCan
Menu
Back to cohort
Record W2626464553 · doi:10.1287/ited.2016.0160

How Big Should My Dot Be? Using Spreadsheet Simulation to Evaluate Process Improvement Data Collection Strategies

2017· article· en· W2626464553 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueINFORMS Transactions on Education · 2017
Typearticle
Languageen
FieldComputer Science
TopicSpreadsheets and End-User Computing
Canadian institutionsSaskatchewan Health Quality CouncilUniversity of Saskatchewan
Fundersnot available
KeywordsData collectionComputer scienceProcess (computing)Big dataData scienceData miningOperating systemMathematicsStatistics

Abstract

fetched live from OpenAlex

Occasionally, healthcare professionals approach analytical topics and courses with a blend of fear and loathing. They may fail to grasp the connection between particular principles and their application to actual process analysis and improvement. The run chart is a persuasively powerful quantitative tool. Healthcare teams could use this tool to better comprehend the extent of process changes over time. Although constructing the run chart is mathematically simple, healthcare professionals may be uncertain as to sample size sufficiency. They may also be unsure of the number of observations required in run chart subgroups. We developed a spreadsheet simulation model to provide enhanced relevance for the topic of run chart subgroup size determination. This classroom-tested active learning exercise helps healthcare teams to visually understand the relationships between subgroup size, underlying process variation, and anticipated levels of improvement.

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 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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.819
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0030.005
Open science0.0010.000
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.151
GPT teacher head0.394
Teacher spread0.242 · 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