MétaCan
Menu
Back to cohort
Record W3185660615 · doi:10.1080/20476965.2021.1952113

Patterns of health information exchange strategies underlying health information technologies capabilities building

2021· article· en· W3185660615 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 Systems · 2021
Typearticle
Languageen
FieldHealth Professions
TopicElectronic Health Records Systems
Canadian institutionsUniversité de MontréalUniversité du Québec à Trois-RivièresNational Bank of CanadaUniversité du Québec à Montréal
Fundersnot available
KeywordsHealth information exchangeHealth informaticsInformation exchangeHealth careCluster analysisSet (abstract data type)Health recordsEuropean unionData setHealth information technologyComputer scienceBusinessMedicineData scienceMedical emergencyNursingPublic healthHealth informationArtificial intelligence

Abstract

fetched live from OpenAlex

The combination of electronic health records (EHRs), health information exchange (HIE), and telehealthholds a high potential for improving the coordination of care and saving lives. As well, the benefits of the three HIT on hospitals' depend on the patterns of capabilities that are available and used by clinicians. However, little is known about how the three HIT, actually empirically coexist and about the strategies underlying the use of HIE in hospital settings. Based on data from a European Union survey, we use a combination of hierarchical and non-hierarchical clustering and discriminant analysis to identify patterns of hospitals' HIT capabilities. Five statistically significantly separated configurations were derived from a data set of 1038 acute care hospitals. The actual empirical coexistence of the three HIT capabilities and associated HIE strategies revealed by this study can be counter-intuitive and shed light on misalignments that may impede the realisation of the potential benefits.

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.010
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.744
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0100.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0010.001
Science and technology studies0.0020.000
Scholarly communication0.0000.003
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.108
GPT teacher head0.435
Teacher spread0.327 · 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