| Literature DB >> 26459233 |
Marjolein Lugtenberg1,2, Jan-Willem Weenink3, Trudy van der Weijden4, Gert P Westert3, Rudolf B Kool3.
Abstract
BACKGROUND: Despite the widespread availability of computerized decision support systems (CDSSs) in various healthcare settings, evidence on their uptake and effectiveness is still limited. Most barrier studies focus on CDSSs that are aimed at a limited number of decision points within selected small-scale academic settings. The aim of this study was to identify the perceived barriers to using large-scale implemented CDSSs covering multiple disease areas in primary care.Entities:
Mesh:
Year: 2015 PMID: 26459233 PMCID: PMC4603732 DOI: 10.1186/s12911-015-0205-z
Source DB: PubMed Journal: BMC Med Inform Decis Mak ISSN: 1472-6947 Impact factor: 2.796
Fig. 1Appearance of an NHGDoc alert button in an EHRS (MicroHIS X). Copyright: iSOFT NEDERLAND B.V., Mendelweg 32, 2333 CS Leiden, the Netherlands
Fig. 2Example of an NHGDoc alert. Copyright: ExpertDoc B.V., Veerkade 8d, 3016 DE Rotterdam, the Netherlands
Framework of barriers to using CDSSs
| Knowledge-related barriers |
| - 1. Knowledge regarding the (specific functions of the) CDSS |
| o Knowledge of basic functions |
| o Knowledge of user personalization functions |
| Barriers related to the evaluation of the features of the CDSS |
| - 2. Source and content of the CDSS |
| o Reliability of the source of the content |
| o Currentness of the content |
| o Relevance of the alert content for different user groups |
| o Relevance of the alert content for individual users, with varying needs across time |
| - 3. Format/lay out of the CDSS content |
| o Notification method of alerts (too intrusive or uninformative) |
| o Readability of the alert text (too wordy/verbose) |
| - 4. Functionality of the CDSS |
| o Responsiveness of the system (loading of an alert takes too long) |
| o Intensity of alerts (low threshold for triggering alerts) |
| o Flexibility (lack of adjustability to personal preferences) |
| o Learning capacity of the system (only fixed rules are used) |
| External barriers interacting with the CDSS |
| - 5. Patient-related factors |
| o Doctor-patient communication (too much time spent on the computer during consultation) |
| o Relevance of alert content for patient (discrepancy between patient’s reason for visit and alert content) |
| - 6. Environmental factors |
| o Limited time available (during and after consultation) |
| o Too much additional work required (during and after consultation) |
| o Lack of integration with other systems (no direct links to follow-up actions) |
| o Fear for misuse of data (patient data and medical practice) by third parties (i.e. health insurers) |
CDSS computerized decision support system
Characteristics of participants
| Number | Percent | Mean | |
|---|---|---|---|
| All PCPs | 24 | ||
| Sex | |||
| Male | 13 | 54 | |
| Female | 11 | 46 | |
| Age | 47 | ||
| Type of practice ( | |||
| Solo | 8 | 38 | |
| Duo | 9 | 43 | |
| Group (>2) | 4 | 19 | |
| Type of EHRS ( | |||
| MicroHIS X | 12 | 55 | |
| Promedico-ASP | 7 | 32 | |
| Other EHRs | 3 | 14 | |
| GPs | 15 | ||
| Sex | |||
| Male | 12 | 80 | |
| Female | 3 | 20 | |
| Age | 52 | ||
| GP trainees | 4 | ||
| Sex | |||
| Male | 1 | 25 | |
| Female | 3 | 75 | |
| Age | 30 | ||
| Practice nurses | 5 | ||
| Sex | |||
| Male | 0 | 0 | |
| Female | 5 | 100 | |
| Age | 47 |
PCPs primary care practitioners, EHRS electronic health record system, GPs general practitioners, GP trainees general practitioners in training
Examples of perceived barriers related to knowledge regarding the (specific functions of the) CDSS
| - Lack of knowledge regarding basic functions |
| • “I have no idea what this grey button [manually to be requested alerts] means. It used to have a color and now it’s grey so I think something is wrong”. |
| • “I didn’t even know there was a feedback option, never heard of it before”. |
| - Lack of knowledge regarding personalization functions |
| • “I had no idea about all these options! Now, I’m a lot more enthusiastic. I’m gonna use it right away!”. |
Examples of perceived barriers related to the source and content of the CDSS
| - Lack of trust in reliability of the source of the content |
| • “Well, then it makes me wonder: do they own any stock options? Yeah, I know it sounds a bit silly. But it makes me wonder which pharmaceutical company is backing this?”. |
| - Lack of trust in currentness of content |
| • “How current are the guideline recommendations? Are the alerts really up to date? That’s what you [the researchers] should include in your advice, that the content of NHGDoc should be updated on a daily basis”. |
| - Irrelevant alerts for different user groups |
| • “It shouldn’t be necessary to override so many alerts; only the sections that apply to us [PNs] should be highlighted”. |
| - Irrelevant alerts for individual users, with varying needs across time |
| • “Well, for example, you don’t wanna see the ‘advice to give up smoking alert’ again, when it’s already clear that it aint gonna happen with this patient. You don’t want to receive that alert over and over again”. |
PNs practice nurses
Examples of perceived barriers related to the format/layout of the CDSS content
| - Notification method (too intrusive or uninformative) |
| • “A pop-up means an additional action which might not be convenient at that time. Now, it’s under my own control”. |
| • “So, you should immediately see whether it concerns a content alert or an alert regarding patient data registration. And also the subject: diabetes, cardiovascular risk management….If you move your mouse over the alert you should be able to see it. That would be worth a whole lot!”. |
| - Readability of the alert text (too wordy/verbose) |
| • “I think the phrasing is sometimes very complex. ‘Research has shown that….’ or ‘You could consider…..’. This should be a bit more to the point really!”. |
Examples of perceived barriers related to the functionality of the CDSS
| - Responsiveness of the system (loading of an alert takes too long) |
| • “I gave up rather quickly because the loading of an alert took way too long”. |
| - Intensity of alerts (low threshold for triggering) |
| • “So it shouldn't be too much, not like ten alerts per patient right? Then you’ll get a little over-alerted right? Enough is as good as a feast!”. |
| • “… did you check kidney function, liver function…? At a certain point you’ll get overloaded with information that is actually quite straightforward…. 25 yellow |
| - Lack of adjustability to personal preferences |
| • “The customization options are still rather limited. You should be able to turn off specific types of advices, for instance the ‘give up-smoking-alerts’ rather than all life style advices at ones”. |
| • “I wanna be able to set the threshold myself, so not all at 40 for blood pressure, for example”. |
| - Lack of learning capacity of the system |
| • “This almost asks for a system that can be overruled. You don’t want the computer stupidly, not intuitively, to state the same thing over and over again. In practice, that will result in overriding alerts. The system should cooperate with how people think”. |
Examples of perceived barriers related to patient factors
| - Doctor-patient communication (too much time spent on the computer during consultation) |
| • “It just takes a lot of time and makes you focus too much on your computer and the patient just does not like that. I can see the patient thinking… while I’m only staring at that stupid screen”. |
| • “I click [on the computer] like there’s no tomorrow, also during patient consultation with the patient next to me. And I sometimes find it disturbing, that I spend so much time on the computer…”. |
| - Relevance of alert content for patient (discrepancy between patient’s reason for visit and alert content) |
| • “The patient’s reason for visiting that absolutely does not match the content of the alert. If someone visits with his ankle, you don’t want to receive an advice on statins”. |
Examples of perceived barriers related to environmental factors
| - Limited time available |
| • “In daily practice I can’t manage to create time for this. It just doesn’t fit in the regular consultation hours”. |
| - Too much additional work required |
| • “These systems, the way they’re currently introduced, just take too much time. And then I deliberately choose not to use them”. |
| • “It’s a lot of extra work! It has almost become a task of its own. With all the items you have to fill out”. |
| - Lack of integration with other systems |
| • “The alert screen should directly be linked to follow-up actions that need to be done! So, if you are to prescribe a statin, it should go directly to that screen. If you have to register blood pressure, you should be able to register it right there”. |
| - Fear of misuse of data by third parties |
| • “And then the healthcare inspectorate comes down to visit and asks: why didn’t you do this or that when there was an alert. It shouldn’t be used for this purpose!”. |