MétaCan
Menu
Back to cohort
Record W1985887105 · doi:10.3109/01676830.2014.882362

Evaluation of Tearing in Oculoplastics Assisted by Tear Osmolarity Measurement

2014· article· en· W1985887105 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

VenueOrbit · 2014
Typearticle
Languageen
FieldMedicine
TopicOcular Surface and Contact Lens
Canadian institutionsMontreal General HospitalMcGill University
Fundersnot available
KeywordsMedicineTearingOsmotic concentrationTearsOphthalmologySurgeryInternal medicineMechanical engineering

Abstract

fetched live from OpenAlex

PURPOSE: To determine the tear osmolarity in patients with tearing secondary to dry eye and other pathologies, and to determine the prevalence of dry eye disease among patients with tearing in an oculoplastics setting. METHODS: 108 eyes of 54 patients with a chief complaint of tearing were prospectively recruited. Subjects were excluded if they used eye drops or contact lenses within 2 hours of assessment, had a history of refractive surgery, an active ocular allergy, or evidence of a systemic disease which affects tear production. A full medical and ocular history was taken with a complete eye exam pertinent to dry eye. Tear osmolarity was measured using the TearLab device. A clinical diagnosis of dry eye was made based on findings, without reference to tear osmolarity. RESULTS: Among 86 eyes symptomatic for tearing, 32 eyes had dry eye disease (37%). Patients with dry eye had a significantly higher median tear osmolarity compared to that in patients with other diagnoses (308 mOsm/L vs. 294 mOsm/L, p < 0.0001). At a cut-off of 308 mOsm/L, tear osmolarity resulted in a sensitivity of 50% and a specificity of 88% for the diagnosis of dry eye. CONCLUSIONS: A significant proportion of patients with tearing in an oculoplastics practice had dry eye disease. The high specificity of tear osmolarity may render it a useful tool to rule in dry eye disease and may assist the oculoplastic surgeon in more accurately determining the cause of tearing.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.186
Threshold uncertainty score0.246

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
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.0000.000
Research integrity0.0000.000
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.051
GPT teacher head0.288
Teacher spread0.237 · 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