MétaCan
Menu
Back to cohort
Record W2980794656 · doi:10.1002/9781119413431.ch25

Distributed Networks of Databases Analyzed Using Common Protocols and/or Common Data Models

2019· other· en· W2980794656 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

VenuePharmacoepidemiology · 2019
Typeother
Languageen
FieldEconomics, Econometrics and Finance
TopicHealth Systems, Economic Evaluations, Quality of Life
Canadian institutionsMcGill University
Fundersnot available
KeywordsComputer scienceDistributed databaseProtocol (science)Distributed computingDatabaseData accessData miningMedicine

Abstract

fetched live from OpenAlex

A distributed data network architecture allows sensitive individual-level and institution-level information to be stored locally under the direct control of participating data partners. It enables multidatabase comparative safety and effectiveness studies of rare exposures, rare outcomes, or specific patient populations, while providing strong protection for patient privacy and data security. In this chapter, we describe the design, development, implementation, strengths, and challenges of distributed data networks. We discuss the methodologic and data issues unique to distributed data networks, and progress that has been accomplished to address these issues. We also examine the design and analytic considerations associated with using a common data model, a common protocol, or both, in distributed data network studies. We conclude with a discussion about some of the future directions for distributed data networks.

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.020
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.627
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0200.002
Meta-epidemiology (narrow)0.0000.001
Meta-epidemiology (broad)0.0040.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.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.778
GPT teacher head0.577
Teacher spread0.200 · 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