Moderate evidence
Published recordHealthGeneral
More
Identifying incident medication-related osteonecrosis of the jaw and antiresorptive drug holidays using natural language processing on clinical notes in men and women prescribed bisphosphonates or denosumab for fracture prevention
- Truvace record
- TRV-2026-1272raw data (JSON)
- Version
- v2Revised
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- f006552d6ae1…check it
Objective Medication-related osteonecrosis of the jaw (MRONJ) is a rare complication of antiresorptive therapy for osteoporosis, with risk potentially influenced by "drug holidays" around dentoalveolar procedures. MRONJ risk is higher in rheumatic diseases. Epidemiologic studies are limited by poor administrative code performance for MRONJ identification and lack of structured pharmacy data capturing drug holidays. We developed and validated a natural language processing (NLP) algorithm to classify MRONJ and det…
The gain
NLP model classified incident MRONJ and identified antiresorptive drug holidays from free-text EHR notes with high precision and recall in validation sets.
What this doesn’t fix
Validation was limited to U.S. Veterans Health Administration EHR for adults >=50 prescribed bisphosphonates or denosumab, and MRONJ is described as rare, constraining generalizability and epidemiologic power.
Sources
1 on file- Arthritis Care & Researchdoi:10.1002/acr.80173
Cite this record
v2Truvace Impact Record TRV-2026-1272, v2: “Identifying incident medication-related osteonecrosis of the jaw and antiresorptive drug holidays using natural language processing on clinical notes in men and women prescribed bisphosphonates or denosumab for fracture prevention.” Truvace, 2026-11-04. /record/TRV-2026-1272 (accessed on the day you copy it). sha256 f006552d6ae143f1…
Change history
2 versionsEvery change made to this record since it was first published, and why.
Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain activity_only, problem absent).
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-1272 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.
ace