68/100

Moderate evidence

Published recordHealthGeneral

Rapid serum-based differentiation of ovarian tumors and assessment of post-treatment disease-free status using portable Raman spectroscopy and machine learning

Truvace record
TRV-2026-1189raw data (JSON)
Version
v3Revised
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
da270dc95edb…check it

Rapid, low-cost tools for ovarian tumor discrimination and post-treatment assessment remain limited because conventional serum biomarkers such as CA125 have suboptimal sensitivity and specificity. Serum contains proteins, lipids, carbohydrates, and nucleic acids that generate disease-related spectrochemical fingerprints, which portable Raman spectroscopy can capture with minimal sample preparation. We investigated serum Raman profiling for ovarian tumor discrimination and cross-sectional characterization of post…

The gain

Portable Raman spectroscopy with machine learning offers a rapid, low-cost serum approach to distinguish ovarian tumors and assess post-treatment status, where CA125 is limited.

Sources

1 on file
  1. Analytical and Bioanalytical Chemistrydoi:10.1007/s00216-026-06823-5
    Peer-reviewed2026-09-23

Cite this record

v3

Truvace Impact Record TRV-2026-1189, v3: “Rapid serum-based differentiation of ovarian tumors and assessment of post-treatment disease-free status using portable Raman spectroscopy and machine learning.” Truvace, 2026-11-04. /record/TRV-2026-1189 (accessed on the day you copy it). sha256 da270dc95edbae88…

Change history

3 versions

Every change made to this record since it was first published, and why.

  1. Revisedv3da270dc95edb…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain unsupported, problem absent).

  2. Revisedv2ee6441ed1c83…

    Direction audit: filed as a problem but describes a gain.

  3. Publishedv138526b18e095…

    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-1189 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.