Evidence map›Paper›PMID 31968383›Full record

ArticleApplied clinical informatics2020

Application Programming Interfaces in Health Care: Findings from a Current-State Sociotechnical Assessment.

Prashila Dullabh, Lauren Hovey, Krysta Heaney-Huls, Nithya Rajendran, Adam Wright, Dean F Sittig

Abstract read
In one paragraph

Article in Applied clinical informatics, 2020. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 20 papers, 2 of them syntheses that pooled it.

0numbers the graph read from it
0cells of the map it votes in
20citing papers in PubMed, 2 pooled it
–field-weighted citation impact
1 · What the graph read from it

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.

2 · The registry

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.

3 · Its place in the literature

Who cites it

20 citing papers in PubMed, 2 syntheses or guidelines pooled it.

  1. Pooled it
  2. Pooled it
  3. Article
  4. Article
  5. Review
  6. Article
  7. Article
  8. Article
  9. Article
  10. Review
  11. Article
  12. Article
  13. Article
  14. Article
  15. Article
  16. The ecosystem of apps and software integrated with certified health information technology.Journal of the American Medical Informatics Association : JAMIA · 2021
    Article
  17. Article
  18. Article
  19. Review
  20. Observational
4 · The record

Corrections and comments

PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.

5 · Who and what money

Authors and funding

6 authors.

Prashila DullabhNORC at the University of Chicago, Chicago, Illinois, United States.
Lauren HoveyNORC at the University of Chicago, Chicago, Illinois, United States.
Krysta Heaney-HulsNORC at the University of Chicago, Chicago, Illinois, United States.
Nithya RajendranNORC at the University of Chicago, Chicago, Illinois, United States.
Adam WrightDepartment of Biomedical Informatics, Vanderbilt University Medical Center, Nashville, Tennessee, United States.
Dean F SittigSchool of Biomedical Informatics, University of Texas Health Science Center at Houston, Houston, Texas, United States.

Funding

No grant is acknowledged in the PubMed record.

6 · The paper itself

Abstract

objectiveInterest in application programming interfaces (APIs) is increasing as key stakeholders look for technical solutions to interoperability challenges. We explored three thematic areas to assess the current state of API use for data access and exchange in health care: (1) API use cases and standards; (2) challenges and facilitators for read and write capabilities; and (3) outlook for development of write capabilities.

methodsWe employed four methods: (1) literature review; (2) expert interviews with 13 API stakeholders; (3) review of electronic health record (EHR) app galleries; and (4) a technical expert panel. We used an eight-dimension sociotechnical model to organize our findings.

resultsThe API ecosystem is complicated and cuts across five of the eight sociotechnical model dimensions: (1) app marketplaces support a range of use cases, the majority of which target providers' needs, with far fewer supporting patient access to data; (2) current focus on read APIs with limited use of write APIs; (3) where standards are used, they are largely Fast Healthcare Interoperability Resources (FHIR); (4) FHIR-based APIs support exchange of electronic health information within the common clinical data set; and (5) validating external data and data sources for clinical decision making creates challenges to provider workflows.

conclusionWhile the use of APIs in health care is increasing rapidly, it is still in the pilot stages. We identified five key issues with implications for the continued advancement of API use: (1) a robust normative FHIR standard; (2) expansion of the common clinical data set to other data elements; (3) enhanced support for write implementation; (4) data provenance rules; and (5) data governance rules. Thus, while APIs are being touted as a solution to interoperability challenges, they remain an emerging technology that is only one piece of a multipronged approach to data access and use.

Indexed as

Delivery of Health CareSoftwareCommunicationHealth Information ExchangeHumansWorkflow

Identifiers

PMID31968383
PMCPMC6976305

What OpenQuestion holds

Textmetadata
LicenceCC BY-NC-ND
Read underepoch 390

Registered trials

None linked

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.