MétaCan
Menu
Back to cohort
Record W1977341443 · doi:10.1177/1460458205055685

Managing hospital databases: can large hospitals really protect patient data?

2005· article· en· W1977341443 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

VenueHealth Informatics Journal · 2005
Typearticle
Languageen
FieldDecision Sciences
TopicData Quality and Management
Canadian institutionsnot available
Fundersnot available
KeywordsLegislationDirectiveCompliance (psychology)Data Protection Act 1998BusinessInternet privacyDatabaseMedicineComputer securityComputer sciencePolitical scienceLaw

Abstract

fetched live from OpenAlex

Between 1998 and 2003 a number of European countries, the UK, Canada, Australia and the US all introduced data privacy legislation that sought to comply with the European Data Privacy Directive of 1995 in protecting the privacy of individuals undergoing treatment in large hospitals. In 2004 we find that hospital administrators within these jurisdictions are still struggling to find ways to implement and maintain hospital databases while complying with the given legislation - where compliance seems to require a whole new approach to database management. This research examines the UK Data Protection Act 1998 and considers whether current database management systems allow the EU Directives contained in the Act to be followed in practice. It finds a number of recurrent problems with hospital systems that would make compliance with the Act difficult. These findings have significant implications for hospital information systems development and design.

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.018
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.576
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0180.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0010.004
Open science0.0020.002
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.001

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.152
GPT teacher head0.432
Teacher spread0.280 · 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