Truace
Subscribe
52/100

Moderate evidence

GainPublished recordHealthGood Space

Full story
More
Export record JSONEmailLinkedInX

MAGR-TCM: a knowledge graph-powered multi-agent model for intelligent home health consultation and triage in TCM gynecology

Truvace record
TRV-2026-2865raw data (JSON)
Version
v1Published
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
d12468f064fb…check it

Traditional Chinese Medicine (TCM) demonstrates distinct efficacy in managing gynecological disorders. However, accessing this specialized care in a home setting remains challenging due to the high cost of frequent hospital visits, privacy concerns, and a lack of immediate professional guidance. While general-purpose artificial intelligence offers a convenient alternative, the semantic gap between a patient's colloquial symptom descriptions and formal TCM diagnostic logic-compounded by the inherent 'hallucinatio…

The gain

In a model-evaluation study, MAGR-TCM, a knowledge graph-based multi-agent AI for home consultation in TCM gynecology, outperformed all baseline models on automatic and expert evaluation and reached 100% sensitivity and specificity on its safety test set.

Sources

1 on file
  1. Chinese Medicinedoi:10.1186/s13020-026-01485-y
    Peer-reviewed2026-11-12

Cite this record

v1

Truvace Impact Record TRV-2026-2865, v1: “MAGR-TCM: a knowledge graph-powered multi-agent model for intelligent home health consultation and triage in TCM gynecology.” Truvace, 2026-11-12. /record/TRV-2026-2865 (accessed on the day you copy it). sha256 d12468f064fba350…

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. Publishedv1d12468f064fb…

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