MétaCan
Menu
Back to cohort
Record W2001086332 · doi:10.2196/resprot.4065

“What Is eHealth”: Time for An Update?

2015· article· en· W2001086332 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.

venuePublished in a venue whose home country is Canada.
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

VenueJMIR Research Protocols · 2015
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
Fundersnot available
KeywordseHealthPsychological interventionComputer sciencemHealthField (mathematics)Data scienceInternet privacyWorld Wide WebMedicineNursingPolitical scienceHealth care

Abstract

fetched live from OpenAlex

The annual number of articles reporting on eHealth interventions has increased over the last 10 years. In contrast, the last article in this journal on the definition of eHealth was published in 2006. This leads to the question whether the field itself has reached consensus about the definition and description of eHealth or whether it is in need for a new review of the literature and a new description of the rapidly changing field of eHealth. Since the JMIR community has successfully collaborated on the "CONSORT-eHealth" in the past, we would like to use the same strategy to explore the need for a new definition of eHealth and the creation of a taxonomy for this field. Therefore, we hereby submit a call to all JMIR-readers, to fill out a 4-question survey on their ideas about a refined eHealth definition. Based on these results, we will decide whether or not to engage in a systematic review. Logically, the entire JMIR community is invited to join us in our attempt to further elucidate the field of eHealth.

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.011
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Protocol · Consensus signal: Protocol
Teacher disagreement score0.045
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0110.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0020.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.002
Insufficient payload (model declined to judge)0.0010.010

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.542
GPT teacher head0.703
Teacher spread0.161 · 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