70/100

Moderate evidence

GainPublished recordScienceGood Space

Overcoming High Volume and Complexity: Developing a Large Language Model-Assisted Scoping Review Method for Identifying Long-term Caesarean Section Outcomes

Truvace record
TRV-2026-2953raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
63acf2599079…check it

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…

The gain

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.

What this doesn’t fix

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.

Sources

1 on file
  1. Annals of Epidemiologydoi:10.1016/j.annepidem.2026.110319
    Peer-reviewed2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-2953, v1: “Overcoming High Volume and Complexity: Developing a Large Language Model-Assisted Scoping Review Method for Identifying Long-term Caesarean Section Outcomes.” Truvace, 2026-11-16. /record/TRV-2026-2953 (accessed on the day you copy it). sha256 63acf259907909bf…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv163acf2599079…

    Certified into the record

Check this record hasn’t been altered

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.