Trends in EHR Satisfaction and Interoperability Among Family Physicians: A Five-Year Analysis of the ABFM Continuous Certification Questionnaire, 2022-2026
Carl Y. ZhangNathaniel HendrixRobert L. PhillipsAndrew W. Bazemore
Oct 2026
Human-computer Interaction
Abstract
Objective: To assess trends in family physicians' (FPs) electronic health record (EHR) satisfaction and their experience of interoperability across organizations.
Materials and Methods: Serial cross-sectional analysis of five waves of the American Board of Family Medicine's Continuous Certification Questionnaire (2022-26). Adjusted logistic regression compared odds of being very satisfied across 11 EHRs; Cochran-Armitage tests assessed vendor trends. Ease of using outside information was analyzed separately for same- and different-vendor sources.
Results: Across 36,785 FPs, adjusted odds of being very satisfied relative to Epic ranged from 0.91 (95% CI, 0.74-1.11) for Elation Health to 0.17 (95% CI, 0.15-0.20) for Oracle Health/Cerner. Only Epic's users became significantly more satisfied (Benjamini-Hochberg adjusted P < .001), widening the vendor satisfaction gap. Within comparable periods, ease of using different-vendor information did not improve; fewer than 13% rated it very easy. Epic's interoperability advantage reversed by exchange type: non-Epic users had less than half the odds of Epic users of rating same-vendor interoperability very easy (adjusted OR, 0.41; 95% CI, 0.38-0.44) but 1.54 times the odds for different-vendor interoperability (95% CI, 1.35-1.75).
Discussion and Conclusion: The ABFM data are already informing EHR policy effects but they also have utility for the EHR marketplace. EHR satisfaction differences are widening, and reported ease of using different-vendor information is low and unchanged. While EHR satisfaction has known implications for burden and burnout, interoperability is a quality and safety threat that may be compounded by artificial intelligence.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 7, 2026
Students in MIT’s Concourse program delve deeply into the human condition, debate challenging questions, and learn to develop judgment about issues that can’t be quantified.
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
MIT News · Artificial Intelligence· news.mit.eduSep 30, 2026
Able to defeat top-ranked human players and more efficient than other models, the new system could help decision-makers in military maneuvers or business negotiations.