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 OpenAlexaff
Keith A. Willoughby, Gary Teare

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

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

metaresearch head score (Codex)0.021
metaresearch head score (Gemma)0.123
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.021
Threshold uncertainty score0.113

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0210.123
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.002
Science and technology studies0.0010.001
Scholarly communication0.0030.003
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0020.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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreMethods

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

Citations0
Published2017
Admission routes1
Has abstractyes

Explore more

Same venueINFORMS Transactions on EducationSame topicSpreadsheets and End-User ComputingFrench-language works237,207