TRV-2026-2228Version 1 · Certified

Written 2026-10-24 00:00:11 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-2228
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-24T00:00:11.018208Z
status: published
lens: g_space
sector: health
headline: Large Language Model Framework for Structured Biomarker Extraction and Triple-Negative Breast Cancer Identification From Pathology Reports: Development and Evaluation Study
dek: Background: Triple-negative breast cancer (TNBC) is an aggressive molecular subtype of breast cancer that needs to be identified accurately from pathology reports to inform decision-making. Large language models (LLMs) have been reported to show great potential in the automatic extraction of important oncology information from unstructured medical text.
Objective: We aimed to create and test an LLM-based approach for automatic biomarker extraction and TNBC subtype classification based on breast cancer pathology…
gain_title: Prompt-engineered language models converted unstructured pathology reports into structured clinical features and identified triple-negative breast cancer patients automatically.
problem_title: (none)
trace_subject: (none)
gain_reading: Prompt-engineered language models converted unstructured pathology reports into structured clinical features and identified triple-negative breast cancer patients automatically.
gain_evidence: translating unstructured breast cancer pathology reports into structured clinical information
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers built a prompting framework that reads free-text breast cancer pathology reports and pulls out structured details such as hormone receptor status, HER2 status, tumor size, grade, and histology. Those fields were then used to pick out patients with the triple-negative subtype. The work used 532 reports from The Cancer Genome Atlas and tested four commercial language models.

The approach matters because triple-negative breast cancer is aggressive and has to be identified accurately from pathology reports to inform decisions, and these reports are usually unstructured. The abstract reports that the method worked, but it gives no numeric performance figures, and it does not show use in routine clinical care.
limitation: 
tag: Evidence-backed gain
key_points: The study used 532 breast cancer pathology reports from The Cancer Genome Atlas. | Four models were compared: GPT-4o mini, GPT-4.1 nano, GPT-5 nano, and Gemini 2.5 Flash-Lite. | Chain-of-thought prompting beat zero-shot and few-shot prompting for both biomarker extraction and TNBC classification across all models. | Gemini 2.5 Flash-Lite was best at extracting clinicopathological attributes, while GPT-4o mini with chain-of-thought prompts scored highest for TNBC classification.
rundown: The framework extracted estrogen receptor, progesterone receptor, and HER2 status along with tumor size, grade, and histology from unstructured pathology text, then used those structured features to classify TNBC.

Model results differed by task. Gemini 2.5 Flash-Lite led on extracting clinicopathological attributes, but GPT-4o mini using chain-of-thought prompts reported the highest performance for TNBC classification.

Prompting strategy mattered consistently: for every model tested, chain-of-thought prompting outperformed zero-shot and few-shot approaches. The authors conclude that prompt engineering is an efficient route from unstructured reports to structured clinical information.
sources:
- peer_reviewed | JMIR Formative Research | https://doi.org/10.2196/97117 | 2026-10-23
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
80d62eb75ddf642fb166207bfd6547f790ba026efb737579c5b8d93e0eaf2108
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2228 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.