MétaCan
Menu
Back to cohort
Record W2745376615 · doi:10.1016/j.jcrs.2017.03.046

Rate of retinal tear and detachment after neodymium:YAG capsulotomy

2017· article· en· W2745376615 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Cataract & Refractive Surgery · 2017
Typearticle
Languageen
FieldMedicine
TopicIntraocular Surgery and Lenses
Canadian institutionsUniversity of SaskatchewanUniversity of Alberta
Fundersnot available
KeywordsCapsulotomyMedicineRetinal detachmentRetinal TearOphthalmologyRetinalNd:YAG laserPosterior CapsulotomySurgeryLaserIntraocular lensOptics

Abstract

fetched live from OpenAlex

PURPOSE: To determine the rate of retinal tear and retinal detachment (RD) after neodymium:YAG (Nd:YAG) laser capsulotomy for posterior capsule opacification (PCO) after cataract surgery. SETTING: Province-wide outpatient and hospital settings, Alberta, Canada. DESIGN: Database study. METHODS: Eleven years of billing records data were collected to assess the rate of retinal tear and/or RD after Nd:YAG laser capsulotomy. A period of 90 days from Nd:YAG was considered the at-risk period, although statistics for 10 years of data were included in the study. Risk was calculated as a rate (%) of retinal tear or RD after Nd:YAG laser capsulotomy. RESULTS: The study comprised 92 654 discrete billing records yielding 73 586 ocular procedures for the analysis of the rate of retinal tear and/or RD after Nd:YAG laser capsulotomy. There were 67 287 Nd:YAG capsulotomies for PCO performed during the study. The 90-day risk for retinal tear after Nd:YAG was 0.21%; 720 retinal tears occurred in the study population at some point after the procedure. The rate of RD was 0.60%, with 2219 RDs occurring at some point after Nd:YAG capsulotomy. The cumulative risk for retinal tear or detachment at 3, 6, 9, and 12 months was 0.21%, 0.30%, 0.36%, and 0.43% and 0.60%, 0.96%, 1.19%, and 1.39%, respectively. The rates of retinal tear and detachment varied significantly between age categories. CONCLUSIONS: There was an increased risk for RD in the first 5 months after Nd:YAG, with a return to a baseline plateau thereafter. As such, the rate of retinal tear after Nd:YAG capsulotomy at 5 months was 0.29%, whereas the rate of RD was 0.87%.

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.031
Threshold uncertainty score0.617

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.016
GPT teacher head0.292
Teacher spread0.277 · 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