ArticleJournal of the American Medical Informatics Association : JAMIA2024
A national survey of digital health company experiences with electronic health record application programming interfaces.
Article in Journal of the American Medical Informatics Association : JAMIA, 2024. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 7 papers.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
7 citing papers in PubMed.
- Avoiding "shiny objects" and heeding "red flags": a sensemaking framework for emerging technology procurement.JAMIA open · 2026Article
- Integrating Heterogeneous Real-World Cancer Data for Semantic Interoperability in Oncology and Medical Imaging: Development and Validation of the Cancer Image Europe Hyperontology.Journal of medical Internet research · 2026Article
- Clarifying Associations Between HIS Provider Characteristics and Hospital Digital Maturity: Provider-Level Inference, Self-Inclusion, and Market-Size Dependence.Journal of medical systems · 2026Article
- A Manifesto for Universal Healthcare: Reconstituting Primary Care Through Digital Innovation, Microbial Technologies and Empowered Citizenship.Microbial biotechnology · 2026Article
- Digital assessment in myasthenia gravis: evidence, validation, and a proposed framework for autoimmune heterogeneity, remote monitoring, and clinical endpoints.Frontiers in immunology · 2026Review
- Rethinking the methodology of global indexes for equitable evidence-informed policy towards sustainable development.Journal of global health · 2024Article
- Engaging knowers in the design and implementation of digital health innovations.Journal of the American Medical Informatics Association : JAMIA · 2024Article
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
6 authors.
Funding
Abstract
objectivesThis study sought to capture current digital health company experiences integrating with electronic health records (EHRs), given new federally regulated standards-based application programming interface (API) policies. MATERIALS AND
methodsWe developed and fielded a survey among companies that develop solutions enabling human interaction with an EHR API. The survey was developed by the University of California San Francisco in collaboration with the Office of the National Coordinator for Health Information Technology, the California Health Care Foundation, and ScaleHealth. The instrument contained questions pertaining to experiences with API integrations, barriers faced during API integrations, and API-relevant policy efforts.
resultsAbout 73% of companies reported current or previous use of a standards-based EHR API in production. About 57% of respondents indicated using both standards-based and proprietary APIs to integrate with an EHR, and 24% worked about equally with both APIs. Most companies reported use of the Fast Healthcare Interoperability Resources standard. Companies reported that standards-based APIs required on average less burden than proprietary APIs to establish and maintain. However, companies face barriers to adopting standards-based APIs, including high fees, lack of realistic clinical testing data, and lack of data elements of interest or value. DISCUSSION: The industry is moving toward the use of standardized APIs to streamline data exchange, with a majority of digital health companies using standards-based APIs to integrate with EHRs. However, barriers persist.
conclusionA large portion of digital health companies use standards-based APIs to interoperate with EHRs. Continuing to improve the resources for digital health companies to find, test, connect, and use these APIs "without special effort" will be crucial to ensure future technology robustness and durability.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.