Moderate evidence
Published recordHealthGood Space
More
Label-free diagnosis of colorectal cancer using a SERS platform based on a modified glass fiber filter membrane combined with machine learning
- Truvace record
- TRV-2026-3001raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 7a9b2f6d753c…check it
A flexible three-dimensional surface-enhanced Raman scattering (SERS) platform using a 4-mercaptophenol (4-MP)-modified glass fiber filter membrane (GFF@4MP) for label-free colorectal cancer (CRC) serum discrimination. Silver nanoparticles were uniformly immobilized onto NaCl-modified porous scaffolds. The 4-MP modifier optimized the interfacial microenvironment and provided specific binding sites, improving target adsorption within SERS "hot spots", reducing non-specific interference, and enhancing spatial unif…
The gain
In a study of serum from 30 colorectal cancer patients and 30 healthy controls, a machine-learning model reading SERS spectra reached 93.3% accuracy internally and 85.5% on an external group of 21 patients and 21 controls.
What this doesn’t fix
The study compared cancer patients with healthy controls in small cohorts (60 internal, 42 external), and accuracy was lower on the external group than the internal one.
Sources
1 on file- Microchimica Actadoi:10.1007/s00604-026-08538-x
Cite this record
v1Truvace Impact Record TRV-2026-3001, v1: “Label-free diagnosis of colorectal cancer using a SERS platform based on a modified glass fiber filter membrane combined with machine learning.” Truvace, 2026-11-17. /record/TRV-2026-3001 (accessed on the day you copy it). sha256 7a9b2f6d753cbbf3…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-3001 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.
ace