A national survey of digital health company experiences with electronic health record application programming interfaces
Objectives This 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 methods We developed and fielded a survey among companie...
Saved in:
| Published in: | Journal of the American Medical Informatics Association : JAMIA Vol. 31; no. 4; pp. 866 - 874 |
|---|---|
| Main Authors: | , , , , , |
| Format: | Journal Article |
| Language: | English |
| Published: |
England
Oxford University Press
03.04.2024
|
| Subjects: | |
| ISSN: | 1067-5027, 1527-974X, 1527-974X |
| Online Access: | Get full text |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Abstract | Objectives
This 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 methods
We 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.
Results
About 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.
Conclusion
A 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. |
|---|---|
| AbstractList | This 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.
We 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.
About 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.
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.
A 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. Objectives This 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 methods We 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. Results About 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. Conclusion A 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. This 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.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.We 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.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.About 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.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.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.DISCUSSIONThe 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.A 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.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. |
| Author | Adler-Milstein, Julia Rosner, Benjamin Barker, Wesley Israelit, Grace K Strawley, Catherine E Maisel, Natalya |
| Author_xml | – sequence: 1 givenname: Wesley surname: Barker fullname: Barker, Wesley email: wesley.barker@hhs.gov – sequence: 2 givenname: Natalya surname: Maisel fullname: Maisel, Natalya – sequence: 3 givenname: Catherine E surname: Strawley fullname: Strawley, Catherine E – sequence: 4 givenname: Grace K surname: Israelit fullname: Israelit, Grace K – sequence: 5 givenname: Julia surname: Adler-Milstein fullname: Adler-Milstein, Julia – sequence: 6 givenname: Benjamin orcidid: 0000-0003-3609-6481 surname: Rosner fullname: Rosner, Benjamin |
| BackLink | https://www.ncbi.nlm.nih.gov/pubmed/38281124$$D View this record in MEDLINE/PubMed |
| BookMark | eNpFkUlPwzAQhS1URBc4ckU-cgn1kjj1sarYJCQuIHGLXHvSukrsYCfQ_nvS0sJpnmaePs3MG6OB8w4QuqbkjhLJpxtVWzX1WgEh4gyNaMbyRObpx6DXRORJRlg-ROMYN4RQwXh2gYZ8xmaUsnSEtnPsVGu9UxWOXfiCHfYlNnZl276zBlW1a6x93Si3w7BtIFhwGiL-tv0AKtBt8M7qkzWA9sFg1TSV1QcwboJfBVXX1q2wdS2EUvWAS3ReqirC1bFO0PvD_dviKXl5fXxezF8SnTLaJhQyJdK8BMj6a_gyo6mWDCQRS0ZkTklJjCGUApdLJg0FIxTlAqgp91LyCbr95fZrfHYQ26K2UUNVKQe-iwWTTBIpZpL01pujtVvWYIom2FqFXXH61j_Ld83flJJiH0RxCKI4BsF_AMFBfzs |
| CitedBy_id | crossref_primary_10_1093_jamia_ocae051 crossref_primary_10_7189_jogh_14_03047 |
| ContentType | Journal Article |
| Copyright | The Author(s) 2024. Published by Oxford University Press on behalf of the American Medical Informatics Association. 2024 The Author(s) 2024. Published by Oxford University Press on behalf of the American Medical Informatics Association. |
| Copyright_xml | – notice: The Author(s) 2024. Published by Oxford University Press on behalf of the American Medical Informatics Association. 2024 – notice: The Author(s) 2024. Published by Oxford University Press on behalf of the American Medical Informatics Association. |
| DBID | TOX CGR CUY CVF ECM EIF NPM 7X8 |
| DOI | 10.1093/jamia/ocae006 |
| DatabaseName | Oxford Journals Open Access Collection Medline MEDLINE MEDLINE (Ovid) MEDLINE MEDLINE PubMed MEDLINE - Academic |
| DatabaseTitle | MEDLINE Medline Complete MEDLINE with Full Text PubMed MEDLINE (Ovid) MEDLINE - Academic |
| DatabaseTitleList | MEDLINE MEDLINE - Academic |
| 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 | Medicine |
| EISSN | 1527-974X |
| EndPage | 874 |
| ExternalDocumentID | 38281124 10.1093/jamia/ocae006 |
| Genre | Research Support, Non-U.S. Gov't Journal Article |
| GrantInformation_xml | – fundername: California Health Care Foundation grantid: G-31685 |
| GroupedDBID | --- --K .DC .GJ 0R~ 18M 1B1 1TH 29L 2WC 4.4 48X 53G 5GY 5RE 5WD 6PF 7RV 7X7 7~T 88E 88I 8AF 8AO 8FE 8FG 8FI 8FJ 8FW AABZA AACZT AAEDT AAJQQ AALRI AAMVS AAOGV AAPGJ AAPQZ AAPXW AARHZ AAUAY AAUQX AAVAP AAWDT AAWTL AAXUO ABDFA ABEJV ABEUO ABGNP ABIXL ABJNI ABNHQ ABOCM ABPQP ABPTD ABQLI ABQNK ABSMQ ABUWG ABVGC ABWST ABWVN ABXVV ACFRR ACGFO ACGFS ACGOD ACHQT ACRPL ACUFI ACUTJ ACVCV ACYHN ACZBC ADBBV ADGZP ADHKW ADHZD ADIPN ADJOM ADMTO ADMUD ADNBA ADNMO ADQBN ADRTK ADVEK ADYVW AEGPL AEJOX AEKSI AEMDU AEMQT AENEX AENZO AEPUE AETBJ AEWNT AFFQV AFFZL AFIYH AFKRA AFOFC AFXAL AFYAG AGINJ AGKRT AGMDO AGORE AGQXC AGSYK AGUTN AHGBF AHMBA AHMMS AJBYB AJDVS AJEEA AJNCP ALIPV ALMA_UNASSIGNED_HOLDINGS ALUQC ALXQX APIBT APJGH AQDSO AQKUS AQUVI ARAPS ATGXG AVNTJ AVWKF AXUDD AYCSE AZQEC BAWUL BAYMD BCRHZ BENPR BEYMZ BGLVJ BHONS BKEYQ BPHCQ BTRTY BVRKM BVXVI BZKNY C1A C45 CCPQU CDBKE CS3 DAKXR DIK DILTD DU5 DWQXO E3Z EBD EBS EIHJH EJD EMOBN ENERS EO8 EX3 F5P FDB FECEO FLUFQ FOEOM FOTVD FQBLK FYUFA G-Q GAUVT GJXCC GNUQQ GX1 H13 HAR HCIFZ HMCUK IH2 IHE J21 JXSIZ K6V K7- KBUDW KOP KSI KSN LSO M0T M1P M2P M2Q M41 MBLQV MHKGH NAPCQ NOMLY NOYVH NQ- NU- NVLIB O9- OAUYM OAWHX OBFPC OCZFY ODMLO OJQWA OJZSN OK1 OPAEJ OVD OWPYF P2P P62 PAFKI PCD PEELM PHGZM PHGZT PQQKQ PROAC PSQYO Q5Y R53 RIG ROL ROX ROZ RPM RPZ RUSNO RWL RXO S0X SSZ SV3 TAE TEORI TJX TMA TOX UKHRP WOQ WOW YAYTL YHZ YKOAZ YXANX ZGI ~S- CGR CUY CVF ECM EIF NPM 77I 7X8 |
| ID | FETCH-LOGICAL-c421t-1e5a647fee51063b514c92e906b209710f0dd011e39b29d1ed6a136e1dfed6a93 |
| IEDL.DBID | TOX |
| ISICitedReferencesCount | 4 |
| ISICitedReferencesURI | http://www.webofscience.com/api/gateway?GWVersion=2&SrcApp=Summon&SrcAuth=ProQuest&DestLinkType=CitingArticles&DestApp=WOS_CPL&KeyUT=001150420300001&url=https%3A%2F%2Fcvtisr.summon.serialssolutions.com%2F%23%21%2Fsearch%3Fho%3Df%26include.ft.matches%3Dt%26l%3Dnull%26q%3D |
| ISSN | 1067-5027 1527-974X |
| IngestDate | Sat Sep 27 22:11:16 EDT 2025 Mon Jul 21 05:50:10 EDT 2025 Mon Jun 30 08:34:52 EDT 2025 |
| IsDoiOpenAccess | true |
| IsOpenAccess | true |
| IsPeerReviewed | true |
| IsScholarly | true |
| Issue | 4 |
| Keywords | industry digital health application programming interface electronic health record |
| Language | English |
| License | This is an Open Access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted reuse, distribution, and reproduction in any medium, provided the original work is properly cited. The Author(s) 2024. Published by Oxford University Press on behalf of the American Medical Informatics Association. |
| LinkModel | DirectLink |
| MergedId | FETCHMERGED-LOGICAL-c421t-1e5a647fee51063b514c92e906b209710f0dd011e39b29d1ed6a136e1dfed6a93 |
| Notes | ObjectType-Article-1 SourceType-Scholarly Journals-1 ObjectType-Feature-2 content type line 23 |
| ORCID | 0000-0003-3609-6481 |
| OpenAccessLink | https://dx.doi.org/10.1093/jamia/ocae006 |
| PMID | 38281124 |
| PQID | 2929096890 |
| PQPubID | 23479 |
| PageCount | 9 |
| ParticipantIDs | proquest_miscellaneous_2929096890 pubmed_primary_38281124 oup_primary_10_1093_jamia_ocae006 |
| PublicationCentury | 2000 |
| PublicationDate | 2024-04-03 |
| PublicationDateYYYYMMDD | 2024-04-03 |
| PublicationDate_xml | – month: 04 year: 2024 text: 2024-04-03 day: 03 |
| PublicationDecade | 2020 |
| PublicationPlace | England |
| PublicationPlace_xml | – name: England |
| PublicationTitle | Journal of the American Medical Informatics Association : JAMIA |
| PublicationTitleAlternate | J Am Med Inform Assoc |
| PublicationYear | 2024 |
| Publisher | Oxford University Press |
| Publisher_xml | – name: Oxford University Press |
| SSID | ssj0016235 |
| Score | 2.4489574 |
| Snippet | Objectives
This study sought to capture current digital health company experiences integrating with electronic health records (EHRs), given new federally... This study sought to capture current digital health company experiences integrating with electronic health records (EHRs), given new federally regulated... |
| SourceID | proquest pubmed oup |
| SourceType | Aggregation Database Index Database Publisher |
| StartPage | 866 |
| SubjectTerms | Delivery of Health Care Digital Health Electronic Health Records Humans Medical Informatics Software |
| Title | A national survey of digital health company experiences with electronic health record application programming interfaces |
| URI | https://www.ncbi.nlm.nih.gov/pubmed/38281124 https://www.proquest.com/docview/2929096890 |
| Volume | 31 |
| WOSCitedRecordID | wos001150420300001&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 | |
| link | http://cvtisr.summon.serialssolutions.com/2.0.0/link/0/eLvHCXMwjV05T8MwFLagQoiF-yhHZSTWiDhOfIwVomJp6VCkbJET26gDKUraCv49z3FaEGVgiTLYTmT7-R3f8_cQuhOE8ULpJEiYtA5mVEEuBbgqsSOjEoYy7otN8NFIpKkct_GO-g8IX1JHEDRV93CyG8-tTRLhShVMntM1XAA6PGlgTZD6BBytlkxzo_evW2wbxmSjVAYH__-dQ7TfGo6471f6CG2Z8hjtDlto_AR99PEqsIfrRbU0n3hmsZ6-uqog2F93xIWXfmzWBMc1dpFY_F0NZ9XUR2_wD4Abt7lcb6DtsKOZqKzL5zpFL4PHycNT0JZVCIo4IvOAmESxmFtjQB4ZzcFkKmRkZMjyyDFKhTbUGsTeUJlHUhOjmSKUGaKte5X0DHXKWWkuENax5tTyxMS2gBPXSvDTY6KEDBVNhOVddAvznb174ozMA940a6Ywa6cQ2qxWI4Ot7fAKVZrZos4iMN3Aw4LRuujcL9N6KAqeIpiK8eU_vnCF9iIwRZp8G3qNOvNqYW7QTrGcT-uqh7Z5KuA5Gg97za76Ahztyko |
| 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=A+national+survey+of+digital+health+company+experiences+with+electronic+health+record+application+programming+interfaces&rft.jtitle=Journal+of+the+American+Medical+Informatics+Association+%3A+JAMIA&rft.au=Barker%2C+Wesley&rft.au=Maisel%2C+Natalya&rft.au=Strawley%2C+Catherine+E&rft.au=Israelit%2C+Grace+K&rft.date=2024-04-03&rft.pub=Oxford+University+Press&rft.issn=1067-5027&rft.eissn=1527-974X&rft.volume=31&rft.issue=4&rft.spage=866&rft.epage=874&rft_id=info:doi/10.1093%2Fjamia%2Focae006&rft.externalDocID=10.1093%2Fjamia%2Focae006 |
| thumbnail_l | http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/lc.gif&issn=1067-5027&client=summon |
| thumbnail_m | http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/mc.gif&issn=1067-5027&client=summon |
| thumbnail_s | http://covers-cdn.summon.serialssolutions.com/index.aspx?isbn=/sc.gif&issn=1067-5027&client=summon |