TRV-2026-1544Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1544 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-16T06:54:44.247032Z status: published lens: g_space sector: health headline: Clinician Use of an Artificial Intelligence-Enabled Clinical Information Platform dek: Importance: Despite growing interest in the use of artificial intelligence (AI) in medicine, empirical evidence on how clinicians use these tools is limited. Objective: To characterize clinician use of an AI-enabled clinical information platform, the distribution of use across the clinical workforce, and the purpose of submitted queries. Design, setting, and participants: This cross-sectional study analyzed clinicians with National Provider Identifier-verified accounts of a commonly used AI-enabled clinical info… gain_title: Clinicians adopted an AI clinical information platform at scale, with monthly active users rising from 355 to 703,265 and heavy use for treatment and management questions. problem_title: (none) trace_subject: (none) gain_reading: Clinicians adopted an AI clinical information platform at scale, with monthly active users rising from 355 to 703,265 and heavy use for treatment and management questions. gain_evidence: Monthly active users increased from 355 in January 2024 to 703 265 in June 2026 | Most queries addressed clinical decision-making (51.9%), particularly treatment and management (33.1%) problem_reading: (none) problem_evidence: (none) quick_read: A cross-sectional analysis of verified clinician accounts on the OpenEvidence platform covered January 2024 through June 2026. About 952,000 clinicians, including roughly 556,000 physicians, sent 271 million queries, and a large language model classified the purpose and topic of a stratified sample of 38.8 million of them. The findings show AI information tools becoming part of routine clinical practice within a short period, and they show who relies on them most. The study describes usage patterns rather than patient outcomes, so whether the queries improved care, or how accurate the answers were, is not established by this analysis. limitation: The study measures how clinicians use the platform, not whether the use was accurate or improved patient care, and the topic classification relied on a sample of queries labeled by a large language model. tag: Evidence-backed gain key_points: Average monthly queries per active user rose from 18.0 to 39.5 over the study period. | Nurse practitioners and physician assistants each averaged 44.5 queries per active user-month, versus 37.1 for physicians. | Physicians within a decade of graduation had a use ratio of 2.54, and residents and fellows 1.84. | Use was lower in ophthalmology (0.23), radiology (0.24) and orthopedics (0.24) than in oncology and hematology (2.00). | Diagnosis accounted for 13.9% of queries, well below treatment and management at 33.1%. rundown: The study used National Provider Identifier-verified accounts, which lets usage be compared with each group's share of the national workforce. Use ratios above 1 indicate overrepresentation relative to workforce size. Specialty differences were notable. Oncology and hematology (2.00), internal medicine (1.88) and family medicine (1.80) used the platform more than average, while procedural and diagnostic specialties used it far less. Many queries went beyond clinicians' own specialties. Queries on topics outside a physician's own specialty ranged from 35% among oncologists and hematologists to 88% among emergency department physicians, suggesting the tool is used to reach unfamiliar clinical areas. sources: - peer_reviewed | JAMA | https://doi.org/10.1001/jama.2026.21868 | 2026-10-15 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 0f625187223ca549bb52628add4d1de9bdcc6527ca73df34fd74c7fb665f0f53
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1544 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