ArticleJAMIA open2022
Why APIs? Anticipated value, barriers, and opportunities for standards-based application programming interfaces in healthcare: perspectives of US thought leaders.
Article in JAMIA open, 2022. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 9 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
9 citing papers in PubMed.
- Approaches to Collect Comprehensive Electronic Patient Data Across Multiple Providers and Payers for Research: Landscape Analysis.Journal of medical Internet research · 2026Article
- Meeting the challenges of electronic health record (EHR) optimization.NPJ digital medicine · 2025Review
- Bridging the gap between models and reality: development of a research environment for an object-oriented hospital information system to integrate artificial intelligence and robotics into clinical practice.International journal of computer assisted radiology and surgery · 2025Article
- Wearing a fur coat in the summertime: Should digital pathology redefine medical imaging?Journal of pathology informatics · 2025Article
- Using Generative Artificial Intelligence in Health Economics and Outcomes Research: A Primer on Techniques and Breakthroughs.PharmacoEconomics - open · 2025Article
- Transforming transplantation access: A federal directive for comprehensive pre-waitlisting data collection.American journal of transplantation : official journal of the American Society of Transplantation and the American Society of Transplant Surgeons · 2025Article
- Automated Mass Extraction of Over 680,000 PICOs from Clinical Study Abstracts Using Generative AI: A Proof-of-Concept Study.Pharmaceutical medicine · 2024Article
- New Horizons for Consumer-Mediated Health Information Exchange.Yearbook of medical informatics · 2024Review
- Perspectives on Challenges and Opportunities for Interoperability: Findings From Key Informant Interviews With Stakeholders in Ohio.JMIR medical informatics · 2023Article
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
2 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
Objective: Improving health data interoperability through application programming interfaces (APIs) is a focus of US policy initiatives and could have tremendous impact on many aspects of care delivery, such as innovation, operational efficiency, and patient-centered care. To better understand the landscape of API use cases, we interviewed US thought leaders involved in developing and implementing standard-based APIs. Materials and Methods: We conducted semi-structured virtual interviews with US subject matter experts (SMEs) on APIs. SMEs were asked to describe API use cases along with value and barriers for each use case. Written summaries were checked by the SME and analyzed by the study team to identify findings and themes. Results: We interviewed 12 SMEs representing diverse sectors of the US healthcare system, including academia, industry, public health agencies, electronic health record vendors, government, and standards organizations. Use cases for standards-based APIs fell into six categories: patient-facing, clinician-facing, population health and value-based care, public health, administrative, and social services. The value across use cases was viewed as unrealized to date, and barriers to the use of APIs varied by use case. Conclusions: SMEs identified a diverse set of API use cases where standard-based APIs had the potential to generate value. As policy efforts seek to increase API adoption, our work provides an early look at the landscape of API use cases, value propositions, and barriers. Additional effort is needed to better understand the barriers and how to overcome them to create value, such as through demonstration projects and rigorous evaluations for specific use cases.
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.