| Literature DB >> 34345802 |
Kensaku Kawamoto1,2, Polina V Kukhareva1,2, Charlene Weir1, Michael C Flynn2,3,4, Claude J Nanjo1,2, Douglas K Martin1,2, Phillip B Warner1,2, David E Shields1,2, Salvador Rodriguez-Loya1,2, Richard L Bradshaw1,2, Ryan C Cornia1,2, Thomas J Reese1, Heidi S Kramer1, Teresa Taft1, Rebecca L Curran1,5, Keaton L Morgan1,2,6, Damian Borbolla1, Maia Hightower2,4, William J Turnbull2, Michael B Strong2,4, Wendy W Chapman1, Travis Gregory2, Carole H Stipelman2,7, Julie H Shakib2,7, Rachel Hess2,4,8, Jonathan P Boltax9, Joseph P Habboushe10,11, Farrant Sakaguchi2,3,5, Kyle M Turner2,3,12, Scott P Narus1,13, Shinji Tarumi14, Wataru Takeuchi14, Hideyuki Ban14, David W Wetter8,15, Cho Lam8,15, Tanner J Caverly16,17, Angela Fagerlin8,18, Chuck Norlin2,7, Daniel C Malone12, Kimberly A Kaphingst15,19, Wendy K Kohlmann2,15, Benjamin S Brooke1,6, Guilherme Del Fiol1.
Abstract
OBJECTIVE: To establish an enterprise initiative for improving health and health care through interoperable electronic health record (EHR) innovations.Entities:
Keywords: CDS Hooks; FHIR; SMART on FHIR; clinical decision support; electronic health record; interoperability standards
Year: 2021 PMID: 34345802 PMCID: PMC8325485 DOI: 10.1093/jamiaopen/ooab041
Source DB: PubMed Journal: JAMIA Open ISSN: 2574-2531
Figure 1.Architectural overview.
ReImagine EHR vision
| Imagine as a doctor | Imagine as a patient |
|---|---|
|
|
|
Strategy, tactics, rationale, and associated considerations
| Strategy | Tactics | Rationale | Considerations |
|---|---|---|---|
| Establish a world-class team | Recruit and retain experts in relevant domains including standards, clinical informatics, user-centered design, implementation, and evaluation | The underlying technology is cutting-edge and requires an expert workforce with technical as well as sociotechnical expertise |
What expertise is needed for success? In what areas are we missing needed expertise? |
| Support continuing training in needed skills (eg, training in EHR-specific API development) | The field is evolving rapidly; some technologies are EHR vendor-specific and require specialized training |
Where is the field headed in terms of technological trends? Do we need additional training to meet current or expected needs? | |
| Create enabling infrastructure to support individual innovations | Address common technical challenges through infrastructure tools | Tools that address common challenges can accelerate the development of individual innovations |
What are the pain points in the development and implementation process? Is there a tool available to address the need, or do we need to create it? |
| Create a systematic program for evaluating individual innovations across project phases | Evaluation is needed to ensure that innovations meet user needs, are adopted, and lead to desired outcomes. Standardization of evaluation steps saves resources and provides higher quality evaluation for individual projects |
Are the tools being used? Do the tools meet users’ needs? How can we make them better? What impact are we having on users, patients and outcomes? What can we do to make future evaluations more efficient? | |
| Focus on the most impactful, sustainable, desirable, and feasible individual innovations | Maximize return on investment with regard to patient care, finances, provider satisfaction, deployment scale, scientific impact, and/or research funding | To be sustainable, investments in EHR add-on apps must have a favorable return on investment |
What is the anticipated impact in these areas? How many patients and/or providers could be positively impacted? Does the solution have commercialization potential? What is the cost of development, implementation, and sustainment? Will there be sufficient ongoing clinical value and/or potential for continuous external research funding to justify long-term institutional investment to sustain the innovation? Are additional resources (eg, grants) available? Will the project help foster the development of compelling new grant proposals? |
| Focus on areas where desired functionality cannot be effectively and/or efficiently achieved through the native EHR, in particular cognitively complex decisions with limited EHR support | It is often easier and less expensive to configure the native EHR to support a specific task than to create an EHR add-on app. However, native EHR tools may be inadequate for meeting user needs related to cognitively complex decisions. |
Does the EHR already do this sufficiently well? Has the EHR vendor committed to addressing this problem in an upcoming release? Is there a third-party product we should buy rather than building our own solution? | |
| Prioritize projects with a clear path to adoption | Lack of usage uptake is a common reason for an EHR add-on app to fail |
Is there a committed clinical champion? Can the tool be integrated into routine clinical workflow? Can the tool be successfully deployed with minimal training? | |
| Follow best practices for design, development, and implementation of individual innovations | Leverage interoperability standards such as FHIR, SMART, and CDS Hooks | While the use of standards can increase upfront development costs compared to using proprietary EHR configuration tools for which the workforce is predominantly trained, standards can reduce overall implementation costs and enhance dissemination potential |
Is a relevant standards-based approach available for what we seek to accomplish? Is the marginal cost of standards support justified? |
| Ensure security, privacy, and confidentiality | Securing patient privacy and confidentiality is paramount |
What patient data are shared outside the institution? Are appropriate security controls in place? Are additional protections required, for example, to filter data shared with third parties through the FHIR protocol? | |
| Employ user-centered design and implementation | Innovations must meet user needs and be integrated with user workflows to succeed |
What are the users’ needs in this area? What features would be most impactful for the user? What is the minimum viable product for early adopters? How will it best fit the users’ workflow? | |
| Maximize synergies | Seek research synergies | An academic medical center has access to leading researchers; the field is a focal area for research |
Are there researchers available with needed expertise? Are there research opportunities synergistic with what we are seeking to achieve? |
| Consider partnerships | No single institution has the expertise and resources needed to fully optimize the EHR on its own |
Does another group, either internal or external, possess relevant expertise or resources? Should we buy or license the tool? Does a partnership make sense? |
Challenges and associated infrastructure developed by ReImagine EHR
| Challenge | Infrastructure addressing challenge | Additional approaches and considerations |
|---|---|---|
| EHR systems may not support desired FHIR data interfaces | FHIR Wrapper: tool that “wraps” an EHR’s native FHIR interface and provides support for additional desired FHIR interfaces, for example by making use of available non-FHIR data interfaces |
Design applications so they can work with EHRs with differing levels of API support Help advance underlying interoperability standards and their adoption through leadership and service in organizations including HL7 (KK, GDF, CN) and the U.S. Health Information Technology Advisory Committee (KK) |
| EHR systems may support “standard” FHIR data interfaces differently | FHIR Wrapper: enables applications to interact with a consistent interface, with data requests and responses transformed as needed to accommodate divergent FHIR interface implementations specific to vendor products or product versions |
Standards such as the US Core FHIR API EHR vendors may offer only partial support for relevant standards |
| Sensitive data unnecessary for app functioning (eg, a patient’s HIV test results) may be transmitted to third-party apps by native EHR data interfaces due to a limitation of the current SMART on FHIR standard | FHIR Wrapper: enables filtering out unnecessary data. For example, if a third-party app developer needs only the patient’s glucose levels but queries for all laboratory results or for glucose levels as well as HIV test results, the tool enables returning only the glucose levels |
Host applications within the enterprise firewall Raise community awareness of this issue Advocate for addressing this issue through organizations including HL7 and the U.S. Health Information Technology Advisory Committee |
| Many tools require the definition of computable “value sets” containing a list of terminology codes that represent clinical concepts of interest | Terminology Suite: provides support for developing value sets in various domains, using available tools such as the National Library of Medicine’s Unified Medical Language System, RxNav, and Value Set Authority Center (VSAC) | Leverage VSAC value sets whenever appropriate. Modify these value sets when needed, and identify VSAC value set stewards that consistently provide high-quality value sets that require minimal or no modification upon detailed review (eg, organizations responsible for the development of national electronic clinical quality measures) |
| Significant effort is required to accurately map codes specific to a given EHR system or healthcare system to standard terminologies | EHR Mapping Tool: supports the mapping of local EHR data to standard codes expected by apps. For example, this tool can search through an EHR and identify all laboratory result types that contain the term “glucose.” The tool then displays relevant information such as frequency of use, example instances, units used, and context of use (eg, frequency of use within a basic metabolic panel versus a lumbar puncture) | Once a FHIR-based application has been developed, accurate terminology mapping is often the most time-consuming aspect of implementing the application in a given healthcare system. Consequently, a typical mapping approach may emphasize speed over accuracy (eg, identifying relevant codes solely by name or using a small number of examples to select and verify mappings). The goal of the EHR Mapping Tool is to enable rigorous terminology mapping comparable to an experienced analyst spending substantial time on each mapping, while significantly reducing the time required so as to make the approach practical for applying at scale |
| Applications used for patient care must be rigorously tested | Testing Suite: provides support for facilitating testing of standards-based EHR add-on apps, such as using FHIR payloads for testing and validating evaluation results delivered through the HL7 CDS Hooks standard. Due in part to the desire to facilitate such testing, the inferencing logic modules within our SMART on FHIR applications are often encapsulated within CDS Hooks services | Testing capabilities supported by our Testing Suite and associated tools include (1) the ability to develop and test against non-production EHR and FHIR server environments; (2) the ability to create de-identified FHIR data for testing, whether through user specification or de-identification of actual patient data; and (3) the ability to conduct regression testing using a large number of de-identified patient cases and their expected results |
| Rigorous evaluation is complex and expensive |
A formal evaluation program including a systematic approach to evaluating digital health innovations across all project phases Recruitment of a Director of Evaluation for the initiative | Collectively, an evaluation team for interoperable EHR innovations should ideally possess masters or doctoral-level expertise in areas such as sociotechnical evaluation, data science, health services research, implementation science, statistics, health economics, and health outcomes evaluation |
Figure 2.Bilirubin app.
Figure 3.MDCalc connect.
Figure 4.AI-facilitated diabetes decision support system.
Figure 5.Lung cancer screening shared decision-making app.
Figure 6.Disease manager.
Representative external funding for ReImagine EHR
| Funding source: project title (Principal Investigator Initials) | Project objectives |
|---|---|
| AHRQ R18HS026198: Scalable decision support and shared decision-making for lung cancer screening (KK) | To increase appropriate lung cancer computed tomography screening through the development and wide dissemination of EHR-integrated clinical decision support tools, including a SMART on FHIR shared decision-making app for lung cancer screening. |
| NCI U24CA204800: Scalable clinical decision support for individualized cancer risk management (GDF and KK) | To develop a standards-based population health management platform, with a focus on identifying, engaging, and managing patients who meet evidence-based criteria for genetic testing of familial breast and colorectal cancer. Standards used include FHIR and CDS Hooks. |
| NCI U01CA232826: Leveraging an electronic medical record infrastructure to identify primary care patients eligible for genetic testing for hereditary cancer and evaluate novel cancer genetics service delivery models (SSB and KAK) | To leverage the standards-based population health management platform described above to compare 2 approaches for delivering genetic counseling and testing for hereditary cancer to primary care patients: standard of care for genetic services or a self-directed approach assisted by an automated chatbot that provides education and explanation of results. |
| AHRQ U18HS027099: Enabling shared decision-making to reduce harm from drug interactions: an end to end demonstration (DCM) | To enable scalable shared decision-making dashboards that graphically communicate risks and decision options related to potential drug-drug interactions. Standards used include SMART on FHIR, CDS Hooks, and the Clinical Quality Language. |
| Hitachi: Clinical decision support system to optimize disease management (KK and CW) | To develop a standards-based, EHR-integrated diabetes management dashboard with predictive analytics about best treatment options and likely outcomes; and to conduct a clinical trial to evaluate the system’s impact. Standards used include SMART on FHIR and CDS Hooks. |
| CMS/Utah Department of Health (HITECH IAPD 182700537): Clinical health information exchange-based shared-care collaborative patient summary (CN and GDF) | To design, develop and implement a SMART on FHIR patient summary dashboard that integrates information from across healthcare systems through a statewide health information exchange to support the care of children with special healthcare needs. |
| ONC 90AX0013: Supporting closed-loop surgical referrals with a SMART on FHIR dashboard (BSB and GDF) | To implement a surgical referral SMART on FHIR dashboard that allows providers from different specialties to share a mental model of patient care and support surgical care transitions between the inpatient and outpatient settings. |
| NCATS 3UL1TR002538-03S4: Community-academic partnership to address COVID-19 among Utah community health centers (RH, DWW, and GDF) | To use multi-level CDS interventions (standardized symptom screening in the EHR, text messaging outreach to patients, and patient navigation) to increase the uptake of COVID-19 testing and immunization among underserved populations in community health centers throughout Utah. |
AHRQ: Agency for Healthcare Research and Quality; CDS: clinical decision support; CMS: Centers for Medicare & Medicaid Services; FHIR: Fast Healthcare Interoperability Resources; NCATS: National Center for Advancing Translational Sciences; NCI: National Cancer Institute; SMART: Substitutable Medical Applications, Reusable Technologies.