TRV-2026-2091Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2091 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-21T10:41:44.427948Z status: published lens: g_space sector: health headline: Detecting Language-Related Disparities in Spiritual Care Using Artificial Intelligence dek: Introduction: Language barriers perpetuate health care disparities, yet traditional data sources overlook inequities in relationship‑based care. This study uses artificial intelligence to examine language‑related disparities in spiritual care, a domain largely documented in unstructured clinical notes. Methods: We analyzed electronic health records of 7,360 deceased adults aged ≥65 years from a tertiary hospital (2010-2023). Natural language processing identified spiritual care documentation, and structured flow… gain_title: Natural language processing of unstructured clinical notes found language-based inequities in spiritual care that structured data alone did not capture. problem_title: (none) trace_subject: (none) gain_reading: Natural language processing of unstructured clinical notes found language-based inequities in spiritual care that structured data alone did not capture. gain_evidence: missed by structured data problem_reading: (none) problem_evidence: (none) quick_read: Researchers reviewed electronic health records of 7,360 adults aged 65 and older who died at one tertiary hospital between 2010 and 2023. Natural language processing found spiritual care documentation in clinical notes, while structured flowsheets recorded formal chaplain visits. The team then compared access and timing by patient language. The findings suggest that inequities in relationship-based care can stay hidden when only structured data are examined, and that text analysis can make them visible. It remains uncertain how far the results apply beyond this hospital and patient group, and the abstract does not say why the gaps arose or whether fixing them changes patient outcomes. limitation: The data come from a single tertiary hospital and cover only deceased adults aged 65 and older, which limits how far the findings generalize to other patients and settings. tag: Evidence-backed gain key_points: The sample was 7,360 deceased adults aged 65 or older from a tertiary hospital, with records spanning 2010 to 2023. | Non-English speakers had an odds ratio of 0.41 (p = .003) for receiving formal spiritual care. | The median time to support was 136 days for non-English speakers versus 432 days for others (p = .020). | Among non-English speakers, providers other than chaplains more often first documented spiritual needs. rundown: The study combined two data sources. Natural language processing identified spiritual care documentation in unstructured clinical notes, and structured flowsheets captured formal chaplain visits. Logistic regression then tested links between patient language and both access to and timing of spiritual care. Non-English speakers had markedly lower odds of formal spiritual care and received it nearly ten months later at the median. The authors report that, for these patients, spiritual needs were more often first noted by providers other than chaplains, which points to how needs are identified before a chaplain gets involved. The authors conclude that AI-supported analysis of unstructured documentation revealed disparities that structured data missed. They describe it as a culturally grounded way to identify inequities in relationship-based care. sources: - peer_reviewed | Journal of Transcultural Nursing | https://doi.org/10.1177/10436596261491239 | 2026-10-20 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 7be515f9cf2342e920cf744899ccc3c923b0ef9f078e9780d2828025d064b080
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2091 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.
ace