MétaCan
Menu
Back to cohort

4.2.3 A Systems Approach to Medical Device Compliance with IEC 60601–1:2005

2012· article· en· W2256298703 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueINCOSE International Symposium · 2012
Typearticle
Languageen
FieldHealth Professions
TopicQuality and Safety in Healthcare
Canadian institutionsnot available
Fundersnot available
KeywordsClinical engineeringRisk analysis (engineering)UsabilityMedical equipmentComputer scienceReliability engineeringEngineeringSystems engineeringEngineering managementBusinessMedicineHealth care

Abstract

fetched live from OpenAlex

Abstract The development of electrical medical devices requires compliance with a host of regulations and standards to help ensure their safety and effectiveness. One of the most notable additions in recent years is the 3 rd Edition of IEC 60601‐1 (IEC 60601–1, 2005), “Medical electrical equipment – General requirements for basic safety and essential performance.” Medical devices sold to the European Community and Canada must comply with the standard in 2012, and devices in the U.S. and other countries must follow shortly thereafter. This standard represents a sea change in the way medical devices are typically developed, and includes a heavy reliance on safety risk management and usability engineering processes. This paper presents the systems engineer as the ideal candidate to lead these activities and facilitate device development; the standard impacts many areas (e.g., engineering, regulatory, human factors, and project management) and requires a methodical approach to implement in a cost‐effective manner while ensuring safety and effectiveness of the device. This paper details techniques developed to efficiently comply with the standard, leveraging existing systems engineering practices and emerging methods such as Model Based Systems Engineering.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.858
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.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.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.002

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.154
GPT teacher head0.465
Teacher spread0.311 · 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