TRV-2026-2953Version 1 · Published

Saved · see the current record

Why this version exists

Certified into the record

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-2953
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-11-16T00:03:11.811062Z
status: published
lens: g_space
sector: science
headline: Overcoming High Volume and Complexity: Developing a Large Language Model-Assisted Scoping Review Method for Identifying Long-term Caesarean Section Outcomes
dek: Rapid growth in medical literature limits traditional systematic review methods, particularly in high-volume fields like maternity care. This paper presents a novel methodological approach using a hybrid workflow that combines Large Language Model (LLM) semantic data extraction with programmatic filtering to automate title and abstract screening. The workflow was deployed on a high-volume clinical dataset (51,281 records retrieved from six databases) as a validation case study. Google Gemini 1.5-pro and 2.5-flas…
gain_title: In a validation study of 51,281 caesarean-section literature records, a Gemini-based screening workflow cut human manual screening by 96% for US$458.73 in API costs, with accuracy comparable to dual-human review.
problem_title: (none)
trace_subject: (none)
gain_reading: In a validation study of 51,281 caesarean-section literature records, a Gemini-based screening workflow cut human manual screening by 96% for US$458.73 in API costs, with accuracy comparable to dual-human review.
gain_evidence: The workflow reduced the human manual screening burden by 96%. | Total API expenditure was US$458.73. | achieving accuracy comparable to dual-human review
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built a hybrid workflow for reviewing medical literature on long-term outcomes of caesarean section. Google's Gemini models pulled structured information from titles and abstracts, and a rule-based pipeline then decided which records were eligible. Applied to 51,281 records from six databases, it cut the human manual screening burden by 96%.

A manual audit checked the results. The workflow's estimated sensitivity was 89.9%, its specificity 96.4% and its false negative rate 0.18%, which the authors describe as comparable to dual-human review. Total API spending came to US$458.73.

Swapping the language model did not change screening accuracy in a subgroup analysis. The authors say separating data extraction from inclusion rules lets reviewers keep control over eligibility criteria and could support living systematic reviews in fast-growing fields such as maternity care.
limitation: Estimated sensitivity was 89.9%, so roughly one in ten eligible records may have been missed at the screening stage, and the approach was validated on a single clinical topic.
tag: Evidence-backed gain
key_points: The workflow screened 51,281 records retrieved from six databases for a review of long-term caesarean section outcomes. | Gemini 1.5-pro and 2.5-flash extracted 12 structured semantic variables from each record. | A seven-stage rule-based filtering pipeline then determined eligibility. | Estimated sensitivity was 89.9% (95% CI 87.3-92.1%) and specificity 96.4% (95% CI 96.2-96.5%). | The false negative rate was 0.18% (95% CI 0.09-0.35%), and human screening burden fell by 96%. | Total API expenditure was US$458.73, and a subgroup analysis found no change in accuracy after changing the language model.
rundown: The method targets a bottleneck: the rapid growth of medical literature limits traditional systematic review methods, particularly in high-volume fields like maternity care. The authors used long-term caesarean section outcomes as a validation case.

Instead of asking the model to make include-or-exclude calls, the workflow has it extract 12 structured variables, which a seven-stage rule-based filter then uses to decide eligibility. The authors say this keeps researchers in control of the inclusion logic.

Accuracy was checked against a large-scale manual audit. Sensitivity, specificity and false negative rate were reported with confidence intervals, and the authors say accuracy matched dual-human review. The run cost US$458.73 in API fees, and changing the model did not alter accuracy.
sources:
- peer_reviewed | Annals of Epidemiology | https://doi.org/10.1016/j.annepidem.2026.110319 | 2026-11-14
prev: 0000000000000000000000000000000000000000000000000000000000000000
SHA-256 hash
63acf259907909bfef3bf18c9f19cbaca291f149c21b9a7eb3b7ddb0ab3114d4
Previous version’s hash
0000000000000000000000000000000000000000000000000000000000000000
Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2953 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.