Why APIs? Anticipated value, barriers, and opportunities for standards-based application programming interfaces in healthcare: perspectives of US thought leaders
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 la...
Uložené v:
| Vydané v: | JAMIA open Ročník 5; číslo 2; s. ooac023 |
|---|---|
| Hlavní autori: | , |
| Médium: | Journal Article |
| Jazyk: | English |
| Vydavateľské údaje: |
United States
Oxford University Press
01.07.2022
|
| Predmet: | |
| ISSN: | 2574-2531, 2574-2531 |
| On-line prístup: | Získať plný text |
| Tagy: |
Pridať tag
Žiadne tagy, Buďte prvý, kto otaguje tento záznam!
|
| 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.
Lay Summary
Application programming interfaces (“APIs”) are a technical way of getting data out of a computer system. Recently, the United States passed legislation (the 21st Century Cures Act) requiring the use of APIs for electronic health record systems, which are where most healthcare providers document clinical encounters with patients and where other clinical data is held. In this article, we asked national experts in health information technology to describe some of the ways in which APIs could be used, how they are valuable, and what some barriers may be to broader use. We found 6 main categories, or “use cases,” for APIs in healthcare—patients, providers, administrative, public health, social services, and population-health. We also describe why these use cases are important, as well as barriers within each use case. As more and more health data are made available via APIs, these use cases will drive the success of these technological innovations. |
|---|---|
| AbstractList | 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.ObjectiveImproving 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.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.Materials and MethodsWe 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.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.ResultsWe 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.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.ConclusionsSMEs 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. 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. Lay Summary Application programming interfaces (“APIs”) are a technical way of getting data out of a computer system. Recently, the United States passed legislation (the 21st Century Cures Act) requiring the use of APIs for electronic health record systems, which are where most healthcare providers document clinical encounters with patients and where other clinical data is held. In this article, we asked national experts in health information technology to describe some of the ways in which APIs could be used, how they are valuable, and what some barriers may be to broader use. We found 6 main categories, or “use cases,” for APIs in healthcare—patients, providers, administrative, public health, social services, and population-health. We also describe why these use cases are important, as well as barriers within each use case. As more and more health data are made available via APIs, these use cases will drive the success of these technological innovations. 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. Keywords: interoperability, FHIR, application programming interfaces Application programming interfaces (“APIs”) are a technical way of getting data out of a computer system. Recently, the United States passed legislation (the 21st Century Cures Act) requiring the use of APIs for electronic health record systems, which are where most healthcare providers document clinical encounters with patients and where other clinical data is held. In this article, we asked national experts in health information technology to describe some of the ways in which APIs could be used, how they are valuable, and what some barriers may be to broader use. We found 6 main categories, or “use cases,” for APIs in healthcare—patients, providers, administrative, public health, social services, and population-health. We also describe why these use cases are important, as well as barriers within each use case. As more and more health data are made available via APIs, these use cases will drive the success of these technological innovations. 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. 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. 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. 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. |
| Audience | Academic |
| Author | Gordon, William J Rudin, Robert S |
| AuthorAffiliation | 4 Health Care Division, RAND Corporation , Boston, Massachusetts, USA 2 Mass General Brigham , Somerville, Massachusetts, USA 3 Department of Biomedical Informatics, Harvard Medical School , Boston, Massachusetts, USA 1 Department of Medicine, Brigham and Women’s Hospital , Boston, Massachusetts, USA |
| AuthorAffiliation_xml | – name: 2 Mass General Brigham , Somerville, Massachusetts, USA – name: 3 Department of Biomedical Informatics, Harvard Medical School , Boston, Massachusetts, USA – name: 4 Health Care Division, RAND Corporation , Boston, Massachusetts, USA – name: 1 Department of Medicine, Brigham and Women’s Hospital , Boston, Massachusetts, USA |
| Author_xml | – sequence: 1 givenname: William J surname: Gordon fullname: Gordon, William J email: wjgordon@partners.org organization: Department of Medicine, Brigham and Women’s Hospital, Boston, Massachusetts, USA – sequence: 2 givenname: Robert S orcidid: 0000-0001-9172-5506 surname: Rudin fullname: Rudin, Robert S organization: Department of Medicine, Brigham and Women’s Hospital, Boston, Massachusetts, USA |
| BackLink | https://www.ncbi.nlm.nih.gov/pubmed/35474716$$D View this record in MEDLINE/PubMed |
| BookMark | eNqNkl1rFDEUhgep2Fr7A7yRgDde7LbJZL7ihbIUPwoFBS1ehjP52EmZSdIks9Cf4z81625LKyKSi4RznvflhPM-Lw6ss6ooXhJ8SjCjZ9cwGXBe2TPnQOCSPimOyrqtlmVNycGD92FxEuM1xpgwxhqKnxWHtK7aqiXNUfHzx3CLVl8v4nu0sskI4yEpiTYwzmqBegjBqBAXCKxEznsX0mxNMioi7QKKKdchyLjsIWYZeD8aAck4i3xw6wDTZOwaGZtU0CCyzFg0KBjTICCot8hnd69EMpvccxpdfUNpcPN6SGhUIHP3RfFUwxjVyf4-Lq4-fvh-_nl5-eXTxfnqcilqTNNSge5rLWTdECIbrAUoJjGUXdcL0dGWyI6SqtVVr6tOd1LWVDYUBKFYd7Ri9Lh4t_P1cz8pKZRNAUbug5kg3HIHhj_uWDPwtdtwhikmuM0Gb_YGwd3MKiY-mSjUOIJVbo68bPJsrKvZFn29Q9cwKm6sdtlRbHG-atu2Yqxrt9TpX6h8pJqMyGnQJtcfCV49_ML97HfrzkC7A0RwMQaluTDp97qysxk5wXybLX6fLb7PVlaSP5R35v_SLHYaN_v_wH8BT8fqiw |
| CitedBy_id | crossref_primary_10_1007_s40290_024_00539_6 crossref_primary_10_1155_2024_7488352 crossref_primary_10_1007_s13239_023_00693_z crossref_primary_10_2196_43848 crossref_primary_10_1002_wcms_70047 crossref_primary_10_1016_j_ajt_2025_01_032 crossref_primary_10_1016_j_tvir_2022_100860 crossref_primary_10_3390_fi16090308 crossref_primary_10_1007_s41669_025_00580_4 crossref_primary_10_1016_j_jpi_2025_100450 crossref_primary_10_1007_s11548_025_03470_6 crossref_primary_10_1148_rg_240073 |
| Cites_doi | 10.1177/1049732316654870 10.1177/1049732305276687 10.1056/NEJMsr1110507 10.2196/14871 10.1016/j.hjdsi.2019.100377 10.2196/16813 10.1038/s41746-020-00358-4 10.1001/jamanetworkopen.2019.9544 10.1001/jamanetworkopen.2020.22408 |
| ContentType | Journal Article |
| Copyright | The Author(s) 2022. Published by Oxford University Press on behalf of the American Medical Informatics Association. 2022 The Author(s) 2022. Published by Oxford University Press on behalf of the American Medical Informatics Association. COPYRIGHT 2022 Oxford University Press The Author(s) 2022. Published by Oxford University Press on behalf of the American Medical Informatics Association. 2022 |
| Copyright_xml | – notice: The Author(s) 2022. Published by Oxford University Press on behalf of the American Medical Informatics Association. 2022 – notice: The Author(s) 2022. Published by Oxford University Press on behalf of the American Medical Informatics Association. – notice: COPYRIGHT 2022 Oxford University Press – notice: The Author(s) 2022. Published by Oxford University Press on behalf of the American Medical Informatics Association. 2022 |
| DBID | TOX AAYXX CITATION NPM 7X8 5PM |
| DOI | 10.1093/jamiaopen/ooac023 |
| DatabaseName | Oxford Journals Open Access Collection CrossRef PubMed MEDLINE - Academic PubMed Central (Full Participant titles) |
| DatabaseTitle | CrossRef PubMed MEDLINE - Academic |
| DatabaseTitleList | MEDLINE - Academic PubMed |
| Database_xml | – sequence: 1 dbid: NPM name: PubMed url: http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=PubMed sourceTypes: Index Database – sequence: 2 dbid: TOX name: Oxford Journals Open Access Collection url: https://academic.oup.com/journals/ sourceTypes: Publisher – sequence: 3 dbid: 7X8 name: MEDLINE - Academic url: https://search.proquest.com/medline sourceTypes: Aggregation Database |
| DeliveryMethod | fulltext_linktorsrc |
| Discipline | Public Health |
| EISSN | 2574-2531 |
| ExternalDocumentID | PMC9030107 A777499877 35474716 10_1093_jamiaopen_ooac023 10.1093/jamiaopen/ooac023 |
| Genre | Journal Article |
| GeographicLocations | Massachusetts |
| GeographicLocations_xml | – name: Massachusetts |
| GrantInformation_xml | – fundername: ; |
| GroupedDBID | 0R~ AAFWJ AAPXW AAVAP ABEJV ABPTD ABXVV ACGFS ADBBV AFPKN AFULF ALMA_UNASSIGNED_HOLDINGS BAYMD BCNDV BTTYL EBS EJD GROUPED_DOAJ IAO ITC KSI M~E O9- OK1 ROX RPM TOX AAYXX ABGNP AMNDL CITATION FYUFA NPM 7X8 5PM |
| ID | FETCH-LOGICAL-c503t-eafb5fcd5611d60fcae9d0a288bcc8371d83147f4bf48f8dd53d63ac130f83493 |
| IEDL.DBID | TOX |
| ISICitedReferencesCount | 11 |
| ISICitedReferencesURI | http://www.webofscience.com/api/gateway?GWVersion=2&SrcApp=Summon&SrcAuth=ProQuest&DestLinkType=CitingArticles&DestApp=WOS_CPL&KeyUT=000778713900001&url=https%3A%2F%2Fcvtisr.summon.serialssolutions.com%2F%23%21%2Fsearch%3Fho%3Df%26include.ft.matches%3Dt%26l%3Dnull%26q%3D |
| ISSN | 2574-2531 |
| IngestDate | Thu Aug 21 14:18:53 EDT 2025 Fri Jul 11 15:13:23 EDT 2025 Tue Jun 17 22:22:07 EDT 2025 Tue Jun 10 21:27:46 EDT 2025 Wed Feb 19 02:26:07 EST 2025 Sat Nov 29 03:56:55 EST 2025 Tue Nov 18 22:48:33 EST 2025 Thu Dec 19 07:37:12 EST 2024 |
| IsDoiOpenAccess | true |
| IsOpenAccess | true |
| IsPeerReviewed | true |
| IsScholarly | true |
| Issue | 2 |
| Keywords | interoperability application programming interfaces FHIR |
| Language | English |
| License | This is an Open Access article distributed under the terms of the Creative Commons Attribution Non-Commercial License (https://creativecommons.org/licenses/by-nc/4.0/), which permits non-commercial re-use, distribution, and reproduction in any medium, provided the original work is properly cited. For commercial re-use, please contact journals.permissions@oup.com https://creativecommons.org/licenses/by-nc/4.0 The Author(s) 2022. Published by Oxford University Press on behalf of the American Medical Informatics Association. |
| LinkModel | DirectLink |
| MergedId | FETCHMERGED-LOGICAL-c503t-eafb5fcd5611d60fcae9d0a288bcc8371d83147f4bf48f8dd53d63ac130f83493 |
| Notes | ObjectType-Article-1 SourceType-Scholarly Journals-1 ObjectType-Feature-2 content type line 23 |
| ORCID | 0000-0001-9172-5506 |
| OpenAccessLink | https://dx.doi.org/10.1093/jamiaopen/ooac023 |
| PMID | 35474716 |
| PQID | 2656198597 |
| PQPubID | 23479 |
| ParticipantIDs | pubmedcentral_primary_oai_pubmedcentral_nih_gov_9030107 proquest_miscellaneous_2656198597 gale_infotracmisc_A777499877 gale_infotracacademiconefile_A777499877 pubmed_primary_35474716 crossref_citationtrail_10_1093_jamiaopen_ooac023 crossref_primary_10_1093_jamiaopen_ooac023 oup_primary_10_1093_jamiaopen_ooac023 |
| PublicationCentury | 2000 |
| PublicationDate | 2022-07-01 |
| PublicationDateYYYYMMDD | 2022-07-01 |
| PublicationDate_xml | – month: 07 year: 2022 text: 2022-07-01 day: 01 |
| PublicationDecade | 2020 |
| PublicationPlace | United States |
| PublicationPlace_xml | – name: United States |
| PublicationTitle | JAMIA open |
| PublicationTitleAlternate | JAMIA Open |
| PublicationYear | 2022 |
| Publisher | Oxford University Press |
| Publisher_xml | – name: Oxford University Press |
| References | Holmgren (2022040613310875300_ooac023-B22) 2019; 7 Gordon (2022040613310875300_ooac023-B10) 2019; 21 HL7 International (2022040613310875300_ooac023-B15) Office of the National Coordinator for Health Information Technology. United States Core Data for Interoperability (USCDI) (2022040613310875300_ooac023-B7) Carin Alliance (2022040613310875300_ooac023-B14) Johnson (2022040613310875300_ooac023-B5) 2021 JASON (2022040613310875300_ooac023-B2) 2014 Iyengar (2022040613310875300_ooac023-B1) 2017 Jernigan (2022040613310875300_ooac023-B24) 2021 HL7 International. HL7 FHIR Accelerator Program. HL7 Int (2022040613310875300_ooac023-B23) Adler-Milstein (2022040613310875300_ooac023-B20) 2019; 2 Myers (2022040613310875300_ooac023-B9) 2021 Health Information Technology Advisory Committee (2022040613310875300_ooac023-B19) Savage (2022040613310875300_ooac023-B25) 2020 Neinstein (2022040613310875300_ooac023-B21) 2020; 22 Hsieh (2022040613310875300_ooac023-B13) 2005; 15 H.R.34—21st Century Cures Act (2022040613310875300_ooac023-B3) Office of Public and Intergovernmental Affairs (2022040613310875300_ooac023-B6) 2018 Centers for Medicare & Medicaid Services (2022040613310875300_ooac023-B17) 2020 Council for State and Territorial Epidemiologists (2022040613310875300_ooac023-B16) Blumenthal (2022040613310875300_ooac023-B4) 2011; 365 Gordon (2022040613310875300_ooac023-B11) 2020; 3 Birt (2022040613310875300_ooac023-B12) 2016; 26 Green (2022040613310875300_ooac023-B18) 2019 Mandl (2022040613310875300_ooac023-B8) 2020; 3 |
| References_xml | – volume-title: Hospital Capabilities to Enable Patient Electronic Access to Health Information, 2019 year: 2021 ident: 2022040613310875300_ooac023-B5 – year: 2018 ident: 2022040613310875300_ooac023-B6 – ident: 2022040613310875300_ooac023-B15 – ident: 2022040613310875300_ooac023-B23 – volume: 26 start-page: 1802 issue: 13 year: 2016 ident: 2022040613310875300_ooac023-B12 article-title: Member checking: a tool to enhance trustworthiness or merely a nod to validation? publication-title: Qual Health Res doi: 10.1177/1049732316654870 – volume-title: Public Health Data + IT Modernization at CDC year: 2021 ident: 2022040613310875300_ooac023-B24 – year: 2020 ident: 2022040613310875300_ooac023-B17 – volume: 15 start-page: 1277 issue: 9 year: 2005 ident: 2022040613310875300_ooac023-B13 article-title: Three approaches to qualitative content analysis publication-title: Qual Health Res doi: 10.1177/1049732305276687 – ident: 2022040613310875300_ooac023-B19 – volume-title: What it really takes to capture the value of APIs year: 2017 ident: 2022040613310875300_ooac023-B1 – volume: 365 start-page: 2323 issue: 24 year: 2011 ident: 2022040613310875300_ooac023-B4 article-title: Wiring the health system–origins and provisions of a new federal program publication-title: N Engl J Med doi: 10.1056/NEJMsr1110507 – volume: 21 start-page: e14871 year: 2019 ident: 2022040613310875300_ooac023-B10 article-title: Comparing characteristics of patients who connect their iphones to an electronic health records system versus patients who connect without personal devices: cohort study publication-title: J Med Internet Res doi: 10.2196/14871 – ident: 2022040613310875300_ooac023-B16 – volume: 7 start-page: 100377 issue: 4 year: 2019 ident: 2022040613310875300_ooac023-B22 article-title: Hospital adoption of API-enabled patient data access publication-title: Healthc (Amst) doi: 10.1016/j.hjdsi.2019.100377 – volume: 22 start-page: e16813 issue: 4 year: 2020 ident: 2022040613310875300_ooac023-B21 article-title: Deploying patient-facing application programming interfaces: thematic analysis of health system experiences publication-title: J Med Internet Res doi: 10.2196/16813 – ident: 2022040613310875300_ooac023-B7 – volume-title: When talking about social determinants, precision matters year: 2019 ident: 2022040613310875300_ooac023-B18 – volume-title: Federal Agencies Align to Promote Public Health Reporting year: 2021 ident: 2022040613310875300_ooac023-B9 – volume: 3 start-page: 151 issue: 1 year: 2020 ident: 2022040613310875300_ooac023-B8 article-title: Push button population health: the SMART/HL7 FHIR bulk data access application programming interface publication-title: NPJ Digit Med doi: 10.1038/s41746-020-00358-4 – volume: 2 start-page: e199544 issue: 8 year: 2019 ident: 2022040613310875300_ooac023-B20 article-title: Assessment of patient use of a new approach to access health record data among 12 US Health Systems publication-title: JAMA Netw Open doi: 10.1001/jamanetworkopen.2019.9544 – volume: 3 start-page: e2022408 issue: 10 year: 2020 ident: 2022040613310875300_ooac023-B11 article-title: Characteristics of patients using patient-facing application programming interface technology at a US Health Care System publication-title: JAMA Netw Open doi: 10.1001/jamanetworkopen.2020.22408 – year: 2020 ident: 2022040613310875300_ooac023-B25 article-title: Measure The Impact Of The ONC’s New Interoperability Rules Now publication-title: Health Aff. Blog. – volume-title: The Mitre Corporation year: 2014 ident: 2022040613310875300_ooac023-B2 – ident: 2022040613310875300_ooac023-B3 – ident: 2022040613310875300_ooac023-B14 |
| SSID | ssj0001999630 |
| Score | 2.2774248 |
| Snippet | Objective
Improving health data interoperability through application programming interfaces (APIs) is a focus of US policy initiatives and could have... Improving health data interoperability through application programming interfaces (APIs) is a focus of US policy initiatives and could have tremendous impact... Objective: Improving health data interoperability through application programming interfaces (APIs) is a focus of US policy initiatives and could have... Application programming interfaces (“APIs”) are a technical way of getting data out of a computer system. Recently, the United States passed legislation (the... |
| SourceID | pubmedcentral proquest gale pubmed crossref oup |
| SourceType | Open Access Repository Aggregation Database Index Database Enrichment Source Publisher |
| StartPage | ooac023 |
| SubjectTerms | Applications programming Electronic records Federal jurisdiction Medical records Middleware Public health Research and Applications Social service |
| Title | Why APIs? Anticipated value, barriers, and opportunities for standards-based application programming interfaces in healthcare: perspectives of US thought leaders |
| URI | https://www.ncbi.nlm.nih.gov/pubmed/35474716 https://www.proquest.com/docview/2656198597 https://pubmed.ncbi.nlm.nih.gov/PMC9030107 |
| Volume | 5 |
| WOSCitedRecordID | wos000778713900001&url=https%3A%2F%2Fcvtisr.summon.serialssolutions.com%2F%23%21%2Fsearch%3Fho%3Df%26include.ft.matches%3Dt%26l%3Dnull%26q%3D |
| hasFullText | 1 |
| inHoldings | 1 |
| isFullTextHit | |
| isPrint | |
| journalDatabaseRights | – providerCode: PRVAON databaseName: DOAJ Directory of Open Access Journals customDbUrl: eissn: 2574-2531 dateEnd: 99991231 omitProxy: false ssIdentifier: ssj0001999630 issn: 2574-2531 databaseCode: DOA dateStart: 20180101 isFulltext: true titleUrlDefault: https://www.doaj.org/ providerName: Directory of Open Access Journals – providerCode: PRVHPJ databaseName: ROAD: Directory of Open Access Scholarly Resources customDbUrl: eissn: 2574-2531 dateEnd: 99991231 omitProxy: false ssIdentifier: ssj0001999630 issn: 2574-2531 databaseCode: M~E dateStart: 20180101 isFulltext: true titleUrlDefault: https://road.issn.org providerName: ISSN International Centre – providerCode: PRVASL databaseName: Oxford Journals Open Access Collection customDbUrl: eissn: 2574-2531 dateEnd: 99991231 omitProxy: false ssIdentifier: ssj0001999630 issn: 2574-2531 databaseCode: TOX dateStart: 20180601 isFulltext: true titleUrlDefault: https://academic.oup.com/journals/ providerName: Oxford University Press |
| link | http://cvtisr.summon.serialssolutions.com/2.0.0/link/0/eLvHCXMwlV1ba9RAFB5q8cEXL3iLrcsRFEE2mGQmmYkvskiLPlgLtrhvYa7sQpssm2zBF_-L_9Q5STbdFJH6EgJzyTA5M-f-HUJeR7mWStg4FHnKQ5YrEyqVqdDFjkqRaH9pdsUm-MmJmM_z0z0y3ebC3HTh5xQBgpYSa0m9ryqpPY_xF26cCiTqs2_za4MKiu508Fz-beCI9_Q38CitbUe6vBkkucN1jh_833ofkvu9dAmzjhwekT1bPia_fyx-wuz0S_0RZmUfRG0NIMy3nYKSayxaV09BlgaqFcrjm7LFWQUv0MLW1lCHyPAM7Hi8oQ_uuvTsDxB3Yu0wwMu_wmIIK_sAq-t8zhoqB-ffoVlgcaAGLrpA6ifk_Pjo7NPnsK_MEOo0ok1opVOp08YLX7HJIqelzU0kEyGU1l7ljY2gMeOOKceEE8ak1GRUas8wnaAsp0_JflmV9jmBSOQ2opQ7yzRTiVGWccZSqRxnOrM2INH2nxW6hy3H6hkXRec-p8Ww30W_3wF5NwxZdZgd_-r8FgmhwPPs59WyT0vwq0NkrGLGvYDsdVLOA3I46unPoR41v_GkdJsPvtoSW4FTYJBbaatNXSReto5z4VW8gDzriG-YjqYMzQdZQPiILIcOCBM-bimXixYuPEetN-Ivbrm-A3IvwRSPNiT5kOw36419Se7qq2ZZryfkDp-LSWu58M-vv44m7Sn8AxbbOkE |
| linkProvider | Oxford University Press |
| openUrl | ctx_ver=Z39.88-2004&ctx_enc=info%3Aofi%2Fenc%3AUTF-8&rfr_id=info%3Asid%2Fsummon.serialssolutions.com&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&rft.genre=article&rft.atitle=Why+APIs%3F+Anticipated+value%2C+barriers%2C+and+opportunities+for+standards-based+application+programming+interfaces+in+healthcare%3A+perspectives+of+US+thought+leaders&rft.jtitle=JAMIA+open&rft.au=Gordon%2C+William+J&rft.au=Rudin%2C+Robert+S&rft.date=2022-07-01&rft.pub=Oxford+University+Press&rft.eissn=2574-2531&rft.volume=5&rft.issue=2&rft_id=info:doi/10.1093%2Fjamiaopen%2Fooac023&rft.externalDocID=10.1093%2Fjamiaopen%2Fooac023 |
| thumbnail_l | http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/lc.gif&issn=2574-2531&client=summon |
| thumbnail_m | http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/mc.gif&issn=2574-2531&client=summon |
| thumbnail_s | http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/sc.gif&issn=2574-2531&client=summon |