MétaCan
Menu
Back to cohort
Record W1530745854

Incidence of portal vein thrombosis after laparoscopic splenectomy.

2005· article· en· W1530745854 on OpenAlexaff
William E. Harris, Michael Marcaccio

Bibliographic record

VenuePubMed · 2005
Typearticle
Languageen
FieldMedicine
TopicLiver Disease and Transplantation
Canadian institutionsMcMaster UniversityHamilton Health Sciences
Fundersnot available
KeywordsMedicineSplenectomyPortal vein thrombosisThrombosisSurgeryPortal hypertensionComplicationInternal medicineSpleenCirrhosis
DOInot available

Abstract

fetched live from OpenAlex

BACKGROUND: Laparoscopic splenectomy has become an important therapeutic option in the management of diverse hematologic disorders. However, the incidence of important complications, such as portal vein thrombosis, remains poorly understood. We set out to study the incidence of this complication over a 14-month period. METHODS: All adult patients who underwent laparoscopic splenectomy between July 2001 and April 2002 at McMaster University Medical Centre in Hamilton, Ont., were approached postoperatively and offered duplex ultrasonography of the portal vein to look for thrombosis. RESULTS: During the study period 17 patients underwent laparoscopic splenectomy. Two patients declined to participate, and in 1 patient the ultrasonography was technically inadequate. Of the 14 remaining patients, 2 (14%) were found to have portal vein thrombosis. In 1 other patient, the investigation was suggestive, but not conclusive, of a clot in the portal system. CONCLUSIONS: Portal vein thrombosis in this series was a relatively common complication of laparoscopic splenectomy. Further research is needed to confirm our findings.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.003
Version: metacan-v3-hybrid-931329e0061cValidation 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.002
Threshold uncertainty score0.006

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0000.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0010.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0020.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.015
GPT teacher head0.244
Teacher spread0.229 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations32
Published2005
Admission routes1
Has abstractyes

Explore more

Same venuePubMedSame topicLiver Disease and TransplantationFrench-language works237,207