aceIs It Feasible to Assess Clinical Remission in Asthma via a Customized Data Extraction Approach from a Real-World Clinical Electronic Medical Records Database in Japan? A Retrospective Real-World Study
Objective : Clinical remission (CR) is an ambitious and attainable treatment goal for patients with asthma. This retrospective, observational study determined the feasibility of assessing CR using an electronic medical record (EMR) database. Methods : Data from the JAMDAS database were analyzed for patients with asthma initiating fluticasone furoate/umeclidinium/vilanterol single-inhaler triple therapy between August 18, 2020 and December 31, 2024. Asthma Control Test (ACT) scores were extracted using structured…
Researchers were able to extract asthma control and exacerbation data from routine EMRs using SQL and a large language model, suggesting it may be feasible to assess clinical remission in Japanese patients initiating triple therapy.
Routine clinical recording of remission components was sparse, with only a small fraction of eligible patients having ACT, FEV1%, or FeNO data, limiting availability of EMR data for remission assessment and generalizability.
CR assessment was constrained by infrequent routine recording of key components in clinical practice, with very low availability of ACT, lung function, and FeNO data, limiting generalizability of findings to the broader eligible population.
Evidence
- Peer-reviewedJournal of Asthma2026-09-15
How should this claim be treated?
Truvace Impact Record TRV-2026-1108, v1: “Is It Feasible to Assess Clinical Remission in Asthma via a Customized Data Extraction Approach from a Real-World Clinical Electronic Medical Records Database in Japan? A Retrospective Real-World Study.” Truvace, 2026-09-16. /record/TRV-2026-1108 (accessed at citation time). sha256 55bd18c9d35af3c4…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1108 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.