68/100

Moderate evidence

Published recordHealthGeneral

Integrated Multi-Omics Reveals Cellular States and Microenvironmental Remodeling in Coexisting DCIS and IDC

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

Ductal carcinoma in situ (DCIS) is a non-invasive precursor of invasive ductal carcinoma (IDC), yet the biological mechanisms underlying the transition from DCIS to IDC remain incompletely understood. Here, we integrate spatial transcriptomics, single-cell RNA sequencing, and single-cell DNA sequencing on coexisting DCIS and IDC samples to characterize cellular and microenvironmental alterations. Integrated analyses reveal differential molecular characterizations between coexisting DCIS and IDC and identify cand…

The gain

Researchers built and externally validated a machine learning model that identifies DCIS at high risk of progressing to invasive disease, enabling more precise risk stratification and clinical management.

Sources

1 on file
  1. Advanced Sciencedoi:10.1002/advs.77897
    Peer-reviewed2026-09-27

Cite this record

v3

Truvace Impact Record TRV-2026-1224, v3: “Integrated Multi-Omics Reveals Cellular States and Microenvironmental Remodeling in Coexisting DCIS and IDC.” Truvace, 2026-11-05. /record/TRV-2026-1224 (accessed on the day you copy it). sha256 71fd7577182876ca…

Change history

3 versions

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

  1. Revisedv371fd75771828…

    Voice pass: plainer wording and study attribution; no facts or figures changed.

  2. Revisedv233f71996b930…

    Direction audit: the gain line stated no AI consequence and was removed. Filed as context; not counted as a gain or a problem.

  3. Publishedv11f212812ae09…

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