| Literature DB >> 31984353 |
Laura Haak Marcial1, Douglas S Johnston2, Michael R Shapiro3, Sara R Jacobs4, Barry Blumenfeld3, Lucia Rojas Smith5.
Abstract
OBJECTIVES: To illustrate key contextual factors that may have effects on clinical decision support (CDS) adoption and, ultimately, success.Entities:
Keywords: HCIA; clinical decision support; evaluation; qualitative; radiology
Year: 2019 PMID: 31984353 PMCID: PMC6952024 DOI: 10.1093/jamiaopen/ooz002
Source DB: PubMed Journal: JAMIA Open ISSN: 2574-2531
Mapping framework elements to constructs as identified in the inductive analysis
| Element in process redesign framework | Critical construct (identified during inductive process) |
|---|---|
| Intervention characteristics | Evidence strength and quality, adaptability, trialability and compatibility, workflows |
| Process of implementation | Goal setting, champions, engaging and executing, reflecting and evaluating, measurement capability and data availability |
| Measures of implementation | Acceptability, adoption, and abandonment; reach and replicability; sustainability; penetration and evolvability |
| Outer setting | External networks, technological environment |
| Inner setting | Implementation climate |
| Characteristics of individuals and teams | Role, skills and competencies, and collective efficacy |
| Outcomes | Effectiveness and efficiency, cost |
Focus areas for this research.
Mapping of results according to framework elements and corresponding constructs for each awardee
| Framework element/construct | Both | Altarum | Imaging advantage |
|---|---|---|---|
| Outer setting | |||
| External networks | Altarum and IA approached the problem of appropriate cost and quality of radiological imaging selection with clinical decision support aimed at general practice clinicians | Altarum worked with 2 large outpatient practice partner organizations, McLaren Physician Partners (MPP) and United Physicians (UP) with employed and independent physicians in Michigan | IA implemented its CDS innovation in the EDs of 4 Tenet Healthcare hospitals in the Chicago area |
| Technical environment | The preferred technical environment for the CDS solutions for both Altarum and IA was either within the EHR or tightly coupled with the EHR | Technical partners for Altarum engaged early on with UP but were less established, resulting in limited EHR integration for initial launch | Technical partners for IA (medCPU and Tenet hospitals IT) were well established |
| Clinical environment | The choice of clinical environment for Altarum and IA came down to existing partner organizations | Altarum, because of the decentralized structure of its partner organizations (UP and MPP), struggled to find a willing and widely used EHR partner | For IA, working within the Tenet hospital EDs provided a specific context for technical integration, training, and rollout |
| Inner setting | |||
| Implementation climate | Working with end users was largely done through third party organizations for both Altarum and IA | Altarum largely used its partners to establish a connection with the provider end users of ImageSmart | With each change, IA and medCPU coordinated a manual test of any new algorithms with radiologists before incorporating them and measured their effect via key performance indicators (KPIs) |
| Intervention characteristics | |||
| Adaptability | While some aspects of the intervention were new for both Altarum and IA, the partner relationships and clinical environments were generally well known to both | Development of ImageSmart was a nascent experience for Altarum, which had done other work with these partners but never application development. Refinement of the tool resulted from a usability survey conducted by Altarum after initial launch of the tool | RadAdvisor was developed, tested, and implemented prior to use by IA |
| Workflows | Both Altarum and IA understood and valued the importance of tailoring the intervention to the existing workflow | Users of ImageSmart could eventually order imaging tests through the tool but were required to follow up on test results using the EHR | From a workflow standpoint, users of the RadAdvisor application were almost seamlessly linked to it from the EHR environment |
| Evidence strength and quality | Totally independently, Altarum and IA worked to create CDS based on accepted best practices drawn from existing guidelines | In terms of application development, Altarum worked closely with American College of Radiology (ACR) and American College of Cardiology (ACC) guidelines to translate these into a usable CDS tool, ImageSmart | IA’s partner, medCPU, an experienced CDS application developer, used an algorithm to combine guidelines from multiple sources |
| Trialability and compatibility | Elements of usability and user-centered design were important to both Altarum and IA and they worked to either build these in at the outset or address them in the implementation stages | Altarum solicited post-implementation feedback via a usability survey, which resulted in significant changes to ImageSmart. At launch, Altarum had to adjust to the limitations of the EHR context by initially providing access to ImageSmart through a separate provider portal rather than directly from the EHR. After noticing that adoption was low, Altarum was planning to provide EHR-specific access with its partners | medCPU incorporated an element of user-centered design through interaction with an advisory team lead by a radiologist from one of the Tenet hospitals to develop the final RadAdvisor application |
| Process of implementation | |||
| Goal setting | As stated in their proposals, the goals of both Altarum and IA were to address cost and quality with radiology CDS | Addressing a clear return on investment as a barrier to adoption was a challenge for both awardees | Addressing a clear return on investment as a barrier to adoption was a challenge for both awardees |
| Champions | Altarum and IA worked hard to build internal champions both within and across their partner organizations | For Altarum, given the nature of its partnership arrangement, building an internal champion at every practice the innovation targeted was much more challenging | At IA, identifying and retaining key internal champions was hampered only by staff turnover |
| Engaging and executing | Though their approaches differed, Altarum and IA provided, either directly or through their partner organizations, critical training needed to use their CDS tools | Altarum relied heavily on its respective partners to provide the necessary training using a train-the-trainer model, with limited success. The use of ImageSmart was not required | IA and medCPU provided an ongoing in-person presence at the 4 Tenet hospitals for training and throughout rollout. The use of RadAdvisor was considered mandatory |
| Reflecting and evaluating | Both Altarum and IA understood the importance of and sought ways to act upon soliciting and responding to feedback throughout the design, development, and implementation processes | To solicit ongoing input on the development of ImageSmart, Altarum formed a high-tech steering committee. This effort also helped ensure the incorporation of local guidelines into ImageSmart. Altarum explored whether using ImageSmart would be helpful in getting imaging pre-approval, but the payer community knew nothing about the CDS, which did not change over the implementation period | Although IA and medCPU actively sought feedback on use of the RadAdvisor tool during their monthly visits and in meetings with ED directors, this meant often relying on the ED directors to be a “single voice” in gathering, reporting, and brainstorming solutions to issues. Turnover in the ED or lack of buy-in often resulted in suboptimal communication |
| Measurement capability and data availability | While the grant specification indicated some degree of evaluation be conducted, little else about the methods and measures was specified. Both Altarum and IA sought to plan and measure according to their long-term outcome goals | Altarum was more experienced with evaluations and focused on near-term measures of adoption and use followed by longer-term measures of patient impact. Altarum identified a key staff member to design and manage the evaluation including all data collection and reporting | IA focused almost exclusively on the ability to report on longer-term measures of patient impact and was largely unable to provide data on adoption and use. IA chose to handle data collection almost entirely electronically, with input from a subset of Tenet key stakeholders and providers, and provided reporting information through a dashboard and manual reports through the project manager |
| Measures of implementation | |||
| Acceptability, adoption, and abandonment | Fundamentally, both Altarum and IA understood the need to develop and implement a technical solution that could ideally be seamlessly integrated into the traditional workflow to ensure clinical adoption | Altarum struggled with a weak technology contractor for UP to provide access to ImageSmart through its loosely-connected provider portal. Even when an EHR vendor was identified, get the EHR vendor’s attention was difficult because of the demand on their time to meet MU criteria. This meant a long, slow process for EHR or system integration of ImageSmart | Despite working closely with the Tenet hospital IT group to “append” its RadAdvisor service to the existing EHR in all 4 EDs, the initial launch of IA’s RadAdvisor was fraught with user interface issues, according to surveyed users. Working in concert with users, medCPU quickly adjusted and, in some cases, tailored changes for the ED environment |
| Sustainability | Organizationally, both Altarum and IA were committed to developing a CDS solution that would exist and be supported beyond the grant period | For Altarum, given the fact that so many EHR systems were in place across their provider practices, and multiple systems were using ImageSmart, much more planning was needed on their part to ensure successful ongoing adoption and use | Although using RadAdvisor required only minimal training, staff turnover and workflow changes required planned training opportunities after rollout |
| Reach and replicability | Part of the overall sustainability plans for both Altarum and IA were launching their CDS solution beyond the target markets for the grant. If successful, these would represent new business for both organizations | Altarum, adding a partner in MPP, demonstrated that ImageSmart could be effectively rolled out with another provider system as well. Altarum demonstrated that ImageSmart could be used for radiology CDS and cardiac imaging CDS and could launch a mobile app, but it had limited success in full EHR integration and lacked significant technical experience in developing CDS | IA demonstrated that RadAdvisor could be effectively rolled out at all 4 Tenet hospitals at different times. In terms of expanding RadAdvisor into other areas (eg, cardiac) and markets (other hospital systems), IA identified a strong key partner in medCPU and appeared well positioned to be successful in broadening the use of the tool |
| Penetration and evolvability | To drive adoption, both Altarum and IA considered the value of using incentives | Altarum did explore the use of incentives with only short-term and mixed results | IA did not explore the use of incentives to improve adoption and utilization. For IA, ED directors among the 4 Tenet hospitals saw the use of RadAdvisor as integral to their practice and did not think incentives would be appropriate. However, they did note that using incentives to obtain user feedback would have been helpful |
| Characteristics of individuals and teams | |||
| Role, skills and competencies, and collective efficacy | Motivated to better ensure successful adoption, Altarum and IA worked diligently to develop or acquire the relevant skills to develop and implement their CDS innovations | Altarum, a non-profit research organization with a great deal of experience working with government contracts, had little to no experience developing and implementing radiology CDS tools. Altarum, a non-profit research organization, may have had different goals than a for-profit company would | In contrast, IA, a for-profit organization with a great deal of experience in working with radiology departments to deliver improved radiology services, was working with its new partner, medCPU, a technology company with sophisticated algorithm development expertise to develop RadAdvisor. As a for-profit organization, Imaging Advantage may have had different drivers for reaching its goals with this innovation |
| Outcomes | |||
| Effectiveness and efficiency | Measures of success based on the desired outcomes were important to both Altarum and IA and were established and tracked to the best of their abilities | Altarum’s reports focused more on training, adoption, and utilization, and Altarum was developing methods to look at impact on provider behavior change and patient outcomes. Altarum was unable to look at adoption more discretely than at the practice level based on its data capture plans and the way the train-the-trainer model was implemented, because it did not necessarily ensure that providers themselves were trained at each practice (sometimes it was an office manager or another paramedical staff member) | IA reported based on KPIs developed in concert with hospital providers, focusing on reductions in inappropriate image orders, with some information on training, adoption, and utilization |
| Cost | Altarum and IA shared similar long term goals with the additional of partners, spending on the initiative, and commercialization strategy | Altarum identified a problem with a key partner early on in its technical development of ImageSmart which cost them both time and money. Given the time constraints of the award, perhaps Altarum should have acted sooner to identify a new partner | From a business standpoint, IA had the advantage of having experience with commercialization and was perhaps better positioned to envision what would be needed to sustain the innovation |