MétaCan
Menu
Back to cohort
Record W2167264926 · doi:10.1177/146045820000600102

Complexity and safety in medical computing: a clinician’s musings

2000· article· en· W2167264926 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

VenueHealth Informatics Journal · 2000
Typearticle
Languageen
FieldEngineering
TopicBiomedical and Engineering Education
Canadian institutionsToronto General HospitalUniversity of Toronto
Fundersnot available
KeywordsRisk analysis (engineering)Simple (philosophy)Computer sciencePatient safetyComputer securityBusinessHealth carePolitical science

Abstract

fetched live from OpenAlex

Some technologies, like scissors and chopsticks, appear inherently simple. Others, like nuclear reactors or life-support electronics, are inherently complex. By nature, the safety issues associated with complex systems are more involved than those associated with simple systems. There are always added cost requirements in complexity, such as special requirements for ensuring safe operation of the system. The very subsystems added to increase safety, however, necessarily add to complexity and, ironically, enrich the number of possible failure modes in the overall system. Thus there is a concern that the failure of any additional safety system may itself lead to new system failure modes that would not have otherwise occurred [1]. These comments explain why simply adding complexity to a system may not always improve on the system’s performance. The following illustrates some of the concerns that I have developed about the potential misapplication of computers in medical technology. These concerns are based on my clinical experience over the last decade in dealing with high-tech aspects of medical care.

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.001
metaresearch head score (Gemma)0.000
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: Empirical
Teacher disagreement score0.976
Threshold uncertainty score0.396

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.028
GPT teacher head0.303
Teacher spread0.275 · 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