Meeting user needs in national healthcare systems: lessons from early adopter community pharmacists using the electronic prescriptions service
© Harvey et al.; licensee BioMed Central Ltd. 2014
Received: 29 January 2013
Accepted: 4 March 2014
Published: 10 March 2014
The Electronic Prescription Service release Two (EPS2) is a new national healthcare information and communication technology in England that aims to deliver effective prescription writing, dispensing and reimbursement service to benefit patients. The aim of the study was to explore initial user experiences of Community Pharmacists (CPs) using EPS2.
We conducted nonparticipant observations and interviews in eight EPS2 early adopter community pharmacies classified as ‘first-of-type’ in midlands and northern regions in England. We interviewed eight pharmacists and two dispensers in addition to 56 hours recorded nonparticipant observations as field notes. Line-by-line coding and thematic analysis was conducted on the interview transcripts and field notes.
CPs faced two types of challenge. The first was to do with missing electronic prescriptions. This was sometimes very disrupting to work practice, but pharmacists considered it a temporary issue resolvable with minor modifications to the system and user familiarity. The second was to do with long term design-specific issues. Pharmacists could only overcome these by using the system in ways not intended by the developers. Some felt that these issues would not exist had ‘real’ users been involved in the initial development. The issues were: 1) printing out electronic prescriptions (tokens) to dispense from for safe dispensing practices and to free up monitors for other uses, 2) logging all dispensing activities with one user’s Smartcard for convenience and use all human resources in the pharmacy, and, 3) problematic interface causing issues with endorsing prescriptions and claiming reimbursements.
We question if these unintended uses and barriers would have occurred had a more rigorous user-centric principles been applied at the earlier stages of design and implementation of EPS. We conclude that, since modification can occur at the evaluation stage, there is still scope for some of these barriers to be corrected to address the needs, and enhance the experiences, of CPs using the service, and make recommendations on how current challenges could be resolved.
KeywordsUser-centric approaches Healthcare ICT Usability User experience Social informatics in healthcare Electronic prescription service release two
The electronic prescription service (Release 2)
In England, it is part of the government’s agenda to enable the writing and dispensing of electronic prescriptions to patients. The Electronic Prescription Service (EPS), released in stages one (EPS1) and two (EPS2) was designed to meet this agenda. Our study focused on EPS2. Sudgen and Wilson  who piloted and evaluated early models of the EPS, also known as the Electronic Transmission of Prescriptions, documented the concept behind its development. Rai  explains the process of writing and dispensing EPS2 prescriptions in detail, and Gourdrey-Smith  explains its functions. In summary, EPS2 is information and communication technology that automates prescription links between prescribing, dispensing and pricing bodies for better patient care in the following simplified format:
Patient to General Practitioner (GP): GP (or designated prescriber) writes prescriptions electronically.
Electronic prescription to Spine: The electronic prescription is sent to and stored on a national database called the N3, commonly known as the Spine.
Spine to community pharmacies: Community Pharmacists (CPs) and their teams
(CP professionals) in pharmacies nominated by the patient to dispense their prescriptions can access and download the prescription from the Spine, and dispense it to the patient.
Community pharmacies to remuneration agency: The remuneration agency, formerly known as Prescription Pricing Authority (PPA), is now called NHS Prescription Services. NHS Prescription Services receives prescriptions from dispensers, such as community pharmacies, calculates relevant payments for the items dispensed and remunerates dispensers for these. With EPS2, details of items dispensed are sent directly to NHS Prescription Services electronically.
Descriptive information of data collection sites
Percentage of EPS2 dispensed at time of interview
EPS2 live since
Information not supplied but noted to be greater than 10%
Since 2011, the National Health Service (NHS) in England, including EPS2 has been undergoing re-organisation. EPS2 was originally part of the National Programme for IT (NPfIT) to make Primary and Secondary care electronically interoperable in England , but it was designed to operate independent of other NPfIT programmes [2–5]. When NPfIT was dismantled in 2011, some of its stand-alone programmes such as EPS2 were retained. On 31 March 2013, the overseeing body of the NPfIT programmes CfH ceased to exist. Many of its functions, including the Electronic Prescription Service, have transferred to the new Health and Social Care Information Centre (HSCIC). On 1st April 2013, responsibility for supporting pharmacists in using these services transferred to NHS England (formally known as the NHS Commissioning Board) . The EPS2 national implementation programme is still on going.
The aim of the study was to explore initial user experiences of CP professionals, and to ask if their needs were met concerning the development and implementation of EPS2. In the following, we briefly discuss key factors in new technology adoption and frame our research questions within these contexts. We then discuss our methodology, present and discuss our findings. Please note that we use ‘early adopters’ to denote sites involved in the early stages of EPS2 implementation. Also, note that we use the term ‘real user’ to denote actual users of the system. In this paper, ‘real users’ are practising community pharmacists and their teams, and not any other type of pharmacist.
Some key factors in successful system delivery or adoption
New systems or innovations are usually developed to solve a problem or aid a process. A system development usually comprises several iterative stages in its lifecycle such as specification or problem-definition, feasibility study, analysis, design, implementation, evaluation and maintenance. When a new system is being developed, many factors influence the planning stage . Key factors include: a) Financial aspects, which comprise of the cost of the system and the overall benefits. b) Technical aspects, what can be accomplished by using existing technologies? and c) Social factors, which comprise changes the new system will be making to current work practices of the users, and how users will engage with the system comprehensively. Some authors recognise this last factor, the social factor, as the most important in a system development concerning the systems acceptance and diffusion [8, 9]. Rogers, for example, names five determinants including simplicity and ease of use, and, compatibility with existing values and practices as key factors in successful adoption, and argue that the innovation is usually what changes to suit the user and not the other way round . Many systems fail or fall into disuse not because of technical failure, but in how the technology is matched to the social environment . The disengagement by users, or a poor user experience directly affects financial and technical factors and can render the system unusable and detrimental [11–15]. Consequently, there needs to be a continuous engagement between the system and the social environment to render a product usable . In theorising the role technology plays in social structures, Greenhalgh and Stone  explained that, the technological component of social structures may be supported when people choose to use the technology, and, not supported when they actively refuse to use it or, importantly, cannot use it at all or in the ways they would like.
In healthcare, Benn et al.  lists “size, regional location, internal structure, management processes, history, external regulatory environment, culture and leadership” as key variables that contribute to successful delivery of care systems. However, similar to other theories, emphasis is placed on social elements as a key factor in technology adoption. Harvey et al.  for example conceptualised that “socio-technical interdependence” is a key dimension in the adoption of new technology into pharmacy work practice. Therefore, before new technology is effectively integrated into work practice, it is important to note how the intended users interact with existing technologies in that environment. In their study, which focused on the approaches to, and experiences of user engagement of the adoption of Lorenzo software into national EHR system in England, Cresswell et al.  placed emphasis on user (dis)engagement. For example, because real users such as hospital staff were not included in the system development process, this alienated them during the implementation process as they felt the system was then not sufficiently customised for their needs. Furthermore, Gagnon et al.  found that the boundary between barriers and facilitators in electronic prescription systems’ adoption were blurred, and recommended studies to be conducted from a variety of user group perspectives. Within these contexts, we frame our research questions: what were CP professionals’ experiences of EPS2, what were their perceptions and attitudes toward the new system, and what can be learned to improve user experience and feedback to the implementers in terms of meeting their needs?
The research was part of the national CfH evaluation programme commissioned by Department of Health to evaluate how EPS2 will alter work practices. The research protocol was designed by a multidisciplinary study team consisting of social scientists, academic and practising pharmacists and a general practitioner. The methodological framework was developed from literature reviews on ‘user perception’ studies of new technologies [21–23], electronic prescription adoption in healthcare [24–29] and listed potential benefits of EPS2 according to CfH . Rather than using standardised variables in ‘user perception’ study models such as perceived ease of use and perceived usefulness, we adopted a constructivist (qualitative) approach by using flexible themes based on user-perception studies, such as user’s perceptions on positive and negative issues, perceived benefits, and opinions on removing the system. This approach allowed us to delve deeper beyond standardised variables into users’ candid perceptions.
The data were collected between February and September 2011. In terms of sampling, we obtained a list of pharmacies classified as early adopters from CfH and selected pharmacies that were ‘live’ and dispensing above 5% electronic prescriptions. The eight pharmacies that fell into this category were in the midland and northern regions of England (Table 1). Sites with different computerised pharmacy management systems were chosen to get divergent perspectives. Other variations in the sites sampled included type of ownership of the pharmacy (independent or chain), geographic location and different software suppliers. Due to the small number of test sites (initial adopters) at the time of the study, providing detailed information in this paper would breech confidentiality and commercial sensitivity agreements. Permissions were sought from approval bodies at each of the study sites, including Primary Care Trusts, research governance teams, benefit realisation teams and informatics leads. The study protocol was submitted to the Cambridgeshire Research Ethics Committee who classed the study as a service evaluation.
Data were collected using ethnographically informed mixed methods including observations, formal (recorded) and informal interviews, and shadowing of pharmacy professionals. Our chief participants were pharmacists/pharmacist proprietors as they had overall insight of the EPS2 integration into work practice. We conducted audio-recorded interviews with all chief participants. We also audio-recorded one accredited checking technician and one dispenser as additional participants. We conducted 10 audio-recorded in-depth interviews. The interviews took 30 minutes to one hour, with transcripts for each averaging 3700 words. Notes were recorded from the participants too occupied with work to give audio-recorded interviews. While the pharmacists were generous in allowing us access to their sites and permitting interviews, the busy nature of the job meant there were time constraints.
Analysis showed that CP professionals were overall positive about the system and wished for it to be retained and improved, instead of being discontinued . They were however facing two types of challenges with the system. The first type of challenge was caused by missing electronic prescriptions. Sometimes, when the prescriber wrote the prescription, pharmacists nominated by the patient to dispense the prescription could not see or download the prescription for dispensing. This issue was especially challenging for pharmacists as there were different causes with no adaptable solution within pharmacy work practice. Pharmacists, however, considered this a teething issue that could be resolved by small modifications to the system . The second type of challenge was considered long-term and was specific to the system design. Although these design specific issues were adaptable into work practice with ‘add-on’ designs, pharmacists thought these issues were present because they were not involved in the system design and development. We decided to present the two challenges in two papers to allow us to discuss the issues (with user commentaries) in detail. In this paper, we present our set of second type challenge in the EPS2 adoption.
We found there were some essential user needs that were not met. These caused users to interact with the system in ways not intended by the system developers, and interfered with how CP professionals experienced the system. These were, 1) dispensing from printed-out tokens instead of screens, 2) using one Smartcard to log all dispensing activities by different staff, and, 3) problematic interface for claiming reimbursements.
I don’t know whether their initial aim was to dispense off the screen or check off the screen, you know, but I wouldn’t check off the screen or dispense off the screen at all. I need a piece of paper in front of me, so that defeats the purpose of the electronic prescriptions” (Site 3, Pharmacist).
“Often, you are too busy in a pharmacy to be able to dispense from the screen. You might have to run your labels off and you need something to check from” (Site 1, Pharmacist).
“I don’t ever see—I don’t know if you could ever get rid of the paper aspect, because I think that I wouldn’t like to check three prescriptions of five items, fifteen items looking at a TV screen. I think I would end up kind of cross-eyed. It’s much easier to look at a piece of paper” (Site 8, Pharmacist).
CPs felt they would have made this known had they been consulted in the EPS2 design. Consequently, instead of directly dispensing medication from computer screens, community pharmacists have deviated from the original EPS2 design by opting to print out the electronic prescriptions after downloading them onto their screens. These printed electronic prescriptions, commonly known as tokens, were then used to dispense medications. Although tokens are not legal prescriptions, they provide a hard copy of data from the electronic prescription, so were accepted by pharmacists for use in dispensing. In addition, printing the tokens enabled patients to have a physical possession of their medication information, as explained by this pharmacist:
“You might need the token to be able to check your items to the labels. Also, you need the repeat slip for patients attached to the token. Patients aren’t going to be able to order again unless they get something in their bag and they can order next time. To do that you need to print the token. If the patient is exempt in some way or pays for the prescription, it has to be filled in on the back if they are not age exempt. If they are under 16, or, over 60, you don’t have to use that paper copy. However you still need the repeat slips, you still need to fill in the exemption and get it signed on the back to show that the patient has an exemption or has a certificate to show that they don’t pay” (Site 1, Pharmacist).
On 10 October 2012, E-health Insider (EHI) featured an article that showed plans for the NHS to be paperless by 2015 . From these interviewee commentaries, it is apparent that the paper-free design of EPS2 is challenging to its users in practice. Paper prescriptions are small, light and mobile and can be annotated, for example, in the final safety check the pharmacist can tick each item on the paper as it has been confirmed correct, allowing them to be interrupted and regain their place without losing accuracy. Perhaps other ‘paper-free’ alternatives could be explored such as using tablets to take screenshots of the electronic prescription for portable dispensing. A challenge in relation to printing of tokens is the additional cost; that pharmacists take this on without reimbursement shows the printing has value to them.
EPS2 was designed to be a Smartcard system to enable access to the Spine. Health professionals who need access to the Spine have to apply for Smartcards from the Registration Authority usually the local Primary Care Trust (PCT) . Since EPS was designed to use ‘a single card’ model of access, individual Smartcards are required for each user. Users cannot share Smartcards or even share access sessions. The purpose of this is to have an audit trail of users of the Spine [3, 35]. Generally, the Smartcard system was not used as intended. Community pharmacies are places of constant rapid physical acts fulfilling the prescription; time at a terminal is a relatively small part of this and terminals are often used by several people. CPs felt that this was the more practical usable method since multiple users did not have to keep logging in and out of the system. Consequently, the first person who logged into the system left their Smartcard in until they finished work for the day then someone else would take over as the main logged-in user as the following excerpt demonstrates:
“We do all have individual Smartcards. We all can use an individual Smartcard. It would just tend to be whoever has been logged in first thing in the morning as the person who would end up doing that most of the day. S goes home at half past four, for instance, and then someone else would have to do it. SE would probably log-in, she leaves at six and then whoever is in this evening would log-in. It just depends really as to who is in first thing in the morning. But yeah, that’s just the way it goes” (Site 5, Pharmacist).
The main reason behind this approach was convenience as the logging in and out by different users would significantly interfere with workflow and reduce productivity, especially at peak hours. Some pharmacists also argued that the reason behind using one Smartcard was to distribute the workload as widely as possible. In the following, pharmacists give more explanation of their reasons for not using Smartcards for each member of staff:
“No, we should do [log-in individually], but we don’t. Because three dispensers, well three people, have the Smartcard in the pharmacy and in fact there is probably five people in the pharmacy that can do all of the jobs and if we kind of religiously stuck to the Smartcard [rule], two people would be isolated away from the computer not being able to dispense. I log-in at the beginning of the day and it’s left there. My responsibility if anything happens untoward, but I can’t understand what it could be, because they are doing NHS prescriptions all the time anyway, and they are used to doing that, and they’ve signed the Data Confidentiality and Data Protection Act” (Site 8, Pharmacist).
“We keep our own. We’ve [each] got a screen, a monitor each, maybe because there is only two of us so X keeps her Smartcard and if I’m not in and if there is a locum in, X will download all the prescriptions, because well, our regular locum does have her own Smartcard and she will bring that and use that. But if you use an agency locums, they wouldn’t necessarily have a card and then everything would go through X” (Site 6, Pharmacist).
Clearly, this was not how the system was designed, continued use this way could breach security and might become an issue if pharmacists have access to patients’ electronic health records. Since EPS2 is still undergoing product development through modifications, perhaps this feature could be modified in a way that would not require the logging of every user’s activity.
Prescription endorsing interface
Getting the interface right in any system development is often the biggest challenge. The interface of a system is a self-contained feature and includes getting a range of multiple items right such as the aesthetics, clarity in direction of use, colours, and user’s emotional connection with it . A key interface issue that has arisen at the evaluation stage of the EPS2 is interacting effectively with the endorsing and claiming interface. When prescriptions are dispensed, pharmacists have to send off the prescription details to NHS prescription service, which has several functions including reimbursing the price of the purchased medicines and the professional fees incurred by pharmacists. Under the paper system, the prescriptions are collated and sent off manually to the pricing body; under the EPS2, this is done electronically using the ‘endorsing and claiming’ interface. The problem some pharmacists appeared to be having with EPS2 interface is effectively interacting with it to claim back charges incurred after dispensing. Since a Common User Interface (CUI) that would integrate with different types of pharmacy systems was not developed , some pharmacy systems adapted better to endorsing and claiming than others. Consequently, some pharmacists had more issues than others. However, a common concern involved ‘NCSO’ claiming, as this pharmacist explains in detail:
“NCSO means No Cheaper Stock Obtainable. Normally everything gets endorsed by the computer, by the endorsing machine. Certain items have to be endorsed manually [not automatic but completed on screen] if it’s specialised and controlled drugs or NCSO. Every month, the Department of Health, they produce a list. Sometimes it’s quite a big list, ten, fifteen items and sometimes it’s only one or two items. For example, this month, 20 mg tablets is on the NCSO list. That list only gets published about the tenth of each month. Everything I’ve done from the first to the tenth, I don’t know whether that item is going to be on the NCSO list. With NCSO, what I have to do, I have to sign it, and I have to date it and I have to put the price I’ve paid for it. So the (Inaudible 00.12.22) might be £2.50 for example. What I’ve paid for it is £10. If I can’t endorse it as £10 I lose £7.50.” (Site 3, Pharmacist).
The encouragement by NHS Connecting for Health of pharmacists to regularly claim electronically for reimbursement (to reduce high flows at the end of the month) means that they may not get reimbursed for NCSO list items that they have dispensed and sent off for reimbursement early in the month. This issue has led pharmacists to become concerned about losing income as noted in the following extracts:
“We are still having problems transmitting a lot of data to pricing bureau. Last month, I think we had about two dozen in total that wouldn’t allow them to be electronically submitted. Our main problem is, when you come to do your ETPII endorsing on [software system 2], I think it was the same on [software system 1]. If you supply, say aspirin tablets and you say aspirin tablets and it has a manufacturer next to it Tabba Actevis. What we’ve done is, we’ve obviously ticked the NCSO button. Because we’ve logged in, we assume that’s as good as a signature for them, which it is, apparently and we sent the data off for months and months and months. We haven’t been paid for any NCSO for months” (Site 2, Pharmacist Proprietor).
“When we endorse, often there is prescriptions that just won’t go. They won’t send so we’ve [wrongly] paid for numerous prescriptions where I’m going to have to sit down with X from the PCT [Primary Care Trust] next week and go through them all and see whether we can chase these payments. Some of them are over six months old, so then we’d have to request the doctors to reissue. One of the endorsing issues was for PIs imports that should get paid the same as a normal English pack. The C programme was asking for a supplementary payment, which is not required for this item. But because I’ve spoken to pharmacists who work in a pharmacy and obviously [they’ve] spoken to a pharmacist who has been stuck in their computer room for the last ten years, they don’t realise what’s going on. They basically said to us, well, for it to go you need to put a payment in or a supplementary payment. They said, well, just put a penny in and they will pay you for the right amount. Some of these cost a lot of money. I said well, I tell you what then, if they are going to pay the right amount, why should I put a penny in and risk it. I’ll put £10,000 in shall I, and then I will get paid still the right amount and not the £10,000. If it goes wrong, I’m at least on the right side of it. So then I get the PPA ringing me up and wondering why I’ve endorsed a load of prescriptions for millions of pounds and then again I’m under stress again, because the PPA are accusing me then of trying to claim lots of money, I was just trying to prove a point” (Site 1, Pharmacist Proprietor).
These detailed commentaries define an interface problem that appears to be causing monetary stress to some pharmacists. Since the interface was not user-friendly, users had to look for alternative ways to claim reimbursements of NCSO items.
Usability and user experience: meeting user needs
In our findings, CP professionals’ needs were not met, particularly in how the system was designed so they had to find ways to adapt them to their needs. The usability and user experience issues identified did not conform with key facilitators of technology adoption such as ease of use and compatibility [9, 38]. While an explanation of the unintended uses could be attributed to CPs collective resistance to change, it does not appear as if the system was tailored to their needs in the first place, which is a key facilitator of technology adoption. A different explanation to these design specific issues could be due to the lack of CPs’ perspectives in the design and development of the EPS2, as demonstrated by this comment: “But because I’ve spoken to pharmacists who work in a pharmacy and obviously [they’ve] spoken to a pharmacist who has been stuck in their computer room for the last ten years, they don’t realise what’s going on”. Whether or not this statement is justified, in the following, we use the concept of user-centric principles to explore and discuss how the involvement of CPs as a key user group in the EPS2 development might have enhanced their experience.
User-centric approaches and active user involvement
To meet user needs in terms of system design, users are often involved in the system development process . Applying user-centric principles, such as user-centred design, which moulds the design of the system to suit its intended users, is recognised as best practice . Studies have shown that national healthcare Information and Communication Technologies (ICTs) development such as Electronic Health Records (EHRs) tend to fail in user engagement . A key reason for this is, users tend to be excluded from the initial stages, and are usually involved only at later stages, thereby making critical modifications to the system design either expensive or impossible [40–42].
Involving users in a new system development can take several approaches. While active involvement of users is sometimes seen as overindulging by allowing users to specify unnecessary functions , the application of user-centric design is usually seen and adopted as best practice in a system development. User-centred design, sometimes also referred to as ‘user-centred system design’ is a human-computer interaction strategy to involve end-users in a new system or service development. The meaning of UCD has become vague since it was coined by Norman and Draper , however, its aim is to place emphasis on user engagement, and improving how the user experiences the system when implemented. It focuses on users by learning about the context of their work, the environments they work in, and their needs for usable products . In short, the aim of UCD is to create a better user experience for the people for whom the system was designed. In practice, UCD faces many challenges as it can be applied using several approaches [39, 45]. Using common approaches to UCD, Gulliksen et al.  developed key principles that underpin its application in a system development, and these are:
The early focus on users’ work practices and tasks to control the development,
Active user participation in the analysis, design, development and evaluation,
Early prototyping to gradually build a shared understanding of user needs as well as future work practices,
Continuous iteration of designed solutions,
Multidisciplinary design teams, and
Integrated design that involves the system, the work practices, online-help, training, organisation, etc.
The theory about the application of these principles is that they will improve the usability of the product and its User Interface (UI) such as ease of use, efficiency, reduced error, and user satisfaction. UI has especially become a current focus of UCD practices as it enables users to familiarise themselves with the product’s interface early . When detailed iteration takes place in the later stages of the development, it is more expensive if the design follows a stage-gate model from conceptual to detailed design. Meaning each design step sets constraints on the next and hence any change in design at a later stage is more expensive than at an earlier stage . Using this perspective, we put into context how a UCD approach could have been used to mould CP professionals’ experience of EPS2.
Putting user-centeredness into context
While reasons such as lack of technical and other forms of support, no added value in terms of finance, or even resistance to change could be explanations for why CPs could not interact effectively with the design of EPS2 [9, 20, 38], active user-involvement could be another explanation. Firstly, in terms of dispensing directly from screens, CPs elected to print and dispense from tokens because various usability requirements such as equipment sharing, job sharing, multi-tasking, and providing advisory slips to patients made dispensing directly from screens challenging. This issue was evident during the piloting of various models at the concept evaluation stage . However, it appears the issue was not explored further or resolved before latter stages, as it would have also been evident during the prototype testing stage. Secondly, in terms of CPs electing to use a single smartcard for multiple users, a key practice of UCD is to perform detailed task analysis of users’ work to design systems that would improve (not interfere) with workflow . Using multiple user log-ins to achieve accurate audit trails appears a feasible concept. In practice however, the concept was challenging for CP professionals as it interfered with workflow. They therefore adapted the Smartcard’s usability to suit their needs by using one Smartcard to serve multiple users. This issue was evident in our EPS2 pre-implementation study of pharmacy work practice as pharmacists showed signs of not using EPS2 Smartcards as intended. We fed back our findings to participating PCTs as part of our formative evaluation . However, this issue could have been evident much earlier at the concept evaluation stage when the idea of EPS2 (and this function) was being marketed to users. It could also have been identified during the user’s task analysis or even the prototyping stages of user-centric approaches. Lastly, since a common user interface to integrate with different types of pharmacy managing systems was not developed, pharmacists had to find ways to deal with the NCSO claiming and endorsing function. Prototype testing by users from various dispensing systems could have aided a better NCSO UI design across all systems.
We do not know to what extent user-centric approaches were used and how rigorously they were applied as we could find very little information on this. It is possible that these design issues were identified at earlier stages but were not resolved at later stages of the system development, however, the purpose of active user involvement is to mould the system to user needs before it becomes too expensive to resolve . While, there may be other explanations for why users could not integrate these EPS2 features into work practice, our study suggests that lack of active CP user groups in the early stages of system development may have been the main problem. While engaging users at later stages allows them to touch and feel the actual product and not just a concept, active involvement in the initial stages is more participatory and allows users to contribute to the design based on their needs. The EPS2 at its evaluation stage clearly showed some important technical barriers that could have perhaps been eliminated had real users been meticulously and actively involved in the initial stages of its development.
We have built on work done by Cresswell et al.  on user engagement by focusing on community pharmacists and their teams as a key user as key user group in the delivery of the national Electronic Prescription Service (EPS) in England. Our focus on English community pharmacies (and primary care) in this paper contributes new knowledge because most of the user-perception literature on national electronic prescriptions systems relates to other parts of Europe and America, and focuses on general practice (GP) or secondary care [20, 24–29].
We emphasize that these are only preliminary findings from early adopter sites, and suggest further studies to establish how the system operates when more mature. We acknowledge that with a small sample our findings may not be generalisable to other community pharmacies, or fit with the experiences of pharmacies that adopted EPS later. However, our aim is to draw attention to involving user group perspectives into systems’ development regardless of whether the issues were still persistent at the time of writing this article. Overall, there is scope for further studies once EPS2 has been implemented more widely. This could help determine whether issues we have identified have been resolved and/or whether new issues have emerged.
Using detailed commentaries from the study of early adopters, we have drawn attention to some key issues in national healthcare system development from a community pharmacy perspective. Firstly, pharmacy professionals needs were not meet in terms of the system design as they had to appropriate certain aspects of the system to suit their needs. Secondly, the process of involving users should be made publicly available to reassure users and to make the development process transparent. Thirdly, our findings suggest that involving real users in the service or system design from the initial stages and throughout the development life cycle could help enhance usability and user experiences, or at least flag up cases in which national policy will be detrimental to local activities. While we acknowledge that many pharmacists were over all in favour of the system, EPS2 at this early evaluation stage clearly showed some key usability and user experience barriers that could have perhaps been eliminated had real users been meticulously and actively involved in the initial stages of its development. We conclude that since EPS2 at the writing of this article is in its evaluation stage, these issues can still be addressed through modifications and perhaps system redesign, and would help meet the needs of community pharmacies and improve their user experience.
Paperless alternatives to the prescription should be developed and assessed with users.
Alternative governance arrangements, or different technology (such as biometric identification), is needed to allow several different users to use the same terminals without delay.
In terms of interface challenges of claiming and reimbursement, pharmacists could be encouraged to make NCSO claims, after the list is published by the Department of Health, while EPS is evolving. In the long term, we recommend that pharmacists make their collective voice heard regarding this issue so that a more acceptable ‘standardised’ interface could be achieved.
Pharmacists should form powerful user groups to work with each of the pharmacy management system suppliers.
JH is a social scientist and specialises in Social Informatics, in particular, ethnological study of peoples’ (dis)engagement with technologies. She has a multidisciplinary background in human sciences, information science and information technology. She works with Professor Tony Avery at the School of Medicine, University of Nottingham. JH previously worked at the Department of Social Sciences, Loughborough University, and WMG at the University of Warwick.
AA is professor of Primary Health Care at the Division of Primary Care, School of Medicine, University of Nottingham. Among other interests, he specialises in patient safety and the use of information technology to aid clinical practice, and has an extensive portfolio and high starred academic papers for both quantitative and qualitative research in this field. AA is also an active general practitioner in the city of Nottingham.
RH was a Research Fellow at the Department of Practice and Policy, University College London School of Pharmacy, University of London. RH has a background in technical design and engineering. His position as the lead researcher of the EPS2 project enabled him to gain critical insight into EPS2 development as he has access to implementer and user group meetings and, liaised closely with Connecting for Health.
NB is professor of the Practice of Pharmacy at the Department of Practice and Policy, University College London School of Pharmacy, University of London. NB gave a critical insight throughout the research write up. NB is also a visiting professor of medication safety at Harvard Medical School and is a practising pharmacist.
We thank all the pharmacies that took part of the study despite having a lot to grapple with. We also thank the individuals from Connecting for Health and the technical architects who gave us insights into EPS2 planning and development. We thank the informatics leads from the Primary Care Trusts who allowed us access to these early adopter sites. Finally, we thank the wider project team for their feedback in the analysis and interpretation of the results.
This report is independent research commissioned by the National Institute of Health Research. The views expressed in this publication are those of the authors and not necessarily those of the NHS, the National Institute for Health Research or the Department of Health.
- Sugden B, Wilson R: Integrated care and electronic transmission of prescriptions: experience of the evaluation of ETP pilots. Health Informatics. 2004, 10: 277-290. 10.1177/1460458204048510.View ArticleGoogle Scholar
- Rai N: EPS put simply. Tomorrows pharmacist [online]. 2008, 56: [http://www.pjonline.com/news/eps_put_simply]Google Scholar
- Gourdrey-Smith G: Information Technology in Pharmacy: An integrated approach. 2013, London: SpringerView ArticleGoogle Scholar
- Department of Health: Delivering 21st century IT support for the NHS Department of Health, UK. [http://webarchive.nationalarchives.gov.uk/+/www.dh.gov.uk/en/publicationsandstatistics/publications/publicationspolicyandguidance/dh_4008227]
- NHS Connecting for Health: The national programme for IT implementation guide: guidance to support trusts when implementing National Programme products and services. 2007, [http://webarchive.nationalarchives.gov.uk/20070305124058/connectingforhealth.nhs.uk/systemsandservices/implementation/docs/national_programme_implementation_guide.pdf]Google Scholar
- Pharmaceutical Services Negotiating Committee (PNSC): EPS & the NHS Re-organisation. [http://psnc.org.uk/dispensing-supply/eps/eps-the-nhs-re-organisation/]
- Yeates D: Systems Analysis and Design. 1994, London: Pitman PublishingGoogle Scholar
- Kling R, Hert C: Social informatics in information science: an introduction. J Am Soc Inf Sci Technol. 1998, 49: 1047-1052. 10.1002/(SICI)1097-4571(1998)49:12<1047::AID-ASI1>3.0.CO;2-V.View ArticleGoogle Scholar
- Rogers E: Diffusion of Innovations. 2003, New York: Free PressGoogle Scholar
- Yu E: Information systems. Practical Handbook of Internet Computing. Edited by: Singh MP. 2004, New York: Chapman and Hall/CRC, 738-761.Google Scholar
- Zhang J: Human-centred computing in health information systems, part 1: analysis and design. J Biomed Inform. 2005, 38: 1-3. 10.1016/j.jbi.2004.12.002.View ArticlePubMedGoogle Scholar
- Giuse DA, Kuhn KA: Health information systems challenges: the Heidelberg conference and the future. Int J Med Inform. 2003, 69: 105-114. 10.1016/S1386-5056(02)00182-X.View ArticlePubMedGoogle Scholar
- Gruchmann T, Borgent A: The effect of new standards on the global movement towards usable medical devices. Proceedings of the HCI and Usability for Medicine and Health Care: Third Symposium of the Workgroup Human-Computer Interaction and Usability Engineering of the Austrian Computer Society: 22 November 2007; Graz. Edited by: Gruchmann T, Borgert A. 2007, Berlin Heidelberg: Springer, 83-96.Google Scholar
- Paulus RA, Davis K, Steele GD: Continuous innovation in health care: implications of the geisinger experience. Health Aff. 2008, 27: 1235-1245. 10.1377/hlthaff.27.5.1235.View ArticleGoogle Scholar
- Catwell L, Sheikh A: Evaluating ehealth interventions: the need for continuous systematic evaluation. PLoS Med. 2009, 9: 8-Google Scholar
- Greenhalgh T, Stones R: Theorising big IT programmes in healthcare: strong structuration theory meets actor-network theory. Soc Sci Med. 2010, 70: 1285-1294. 10.1016/j.socscimed.2009.12.034.View ArticlePubMedGoogle Scholar
- Benn J, Burnett S, Parand A, Pinto A, Iskander S, Vincent C: Studying large-scale programmes to improve patient safety in whole care systems: challenges for research. Soc Sci Med. 2009, 69: 1767-1776. 10.1016/j.socscimed.2009.09.051.View ArticlePubMedGoogle Scholar
- Harvey J, Avery A, Waring J, Barber N: The socio-technical organisation of community pharmacies as a factor in the electronic prescription service release Two implementation: a qualitative study. BMC Health Serv Res. 2012, 12: 471-10.1186/1472-6963-12-471.View ArticlePubMedPubMed CentralGoogle Scholar
- Cresswell K, Morrison Z, Crowe S, Robertson A, Sheikh A: Anything but engaged: user involvement in the context of a national electronic health record implementation. Inform Prim Care. 2011, 19: 191-206.PubMedGoogle Scholar
- Gagnon M-P, Nsangou É-R, Payne-Gagnon J, Grenier S, Sicotte C: Barriers and facilitators to implementing electronic prescription: a systematic review of user groups’ perception. J Am Med Inform Assoc. 2013, doi:10.1136/amiajnl-2013-00220Google Scholar
- Davis FD: Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Q. 1989, 13: 319-340. 10.2307/249008.View ArticleGoogle Scholar
- Heathfield H, Pitty D, Hanka R: Evaluating information technology in health care: barriers and challenges. BMJ. 1959–1961, 1998: 316-Google Scholar
- Pare G, Elam JJ: Physicians’ acceptance of clinical information systems: an empirical look at attitudes expectations and skills. Int J Healthc Tech Mnag. 1999, 1: 46-61. 10.1504/IJHTM.1999.001060.View ArticleGoogle Scholar
- Boonstra A: Interpretative perspectives on the acceptance of an optional information system: lessons from the introduction of an electronic prescription system for general practitioner. J. Inf. Technol. Cases Appl. 2003, 5: 27-49.Google Scholar
- Boonstra A, Boddy D, Fischbacher M: The limited acceptance of an electronic prescription system by general practitioners: reasons and practical implications. New Tech, work and employ. 2004, 19: 128-144. 10.1111/j.0268-1072.2004.00132.x.View ArticleGoogle Scholar
- Hellström L, Waern K, Montelius E, Åstrand B, Rydberg T, Petersson G: Physicians' attitudes towards ePrescribing – evaluation of a Swedish full-scale implementation. BMC Medical Inform and Decis Mak. 2009, 9: 37-10.1186/1472-6947-9-37.View ArticleGoogle Scholar
- Hyppönen H, Nykänen P, Salmivalli L, Pajukoski M, Ruotsalainen P, Vuorela S: Conducting interdisciplinary research: evaluation of the ePrescription pilot scheme in Finland. EJISE. 2005, 8: 187-194.Google Scholar
- Salmivalli L, Hilmola OP: Business pluralism of electronic prescriptions: state of development in Europe and the USA. Int J Electron Healthc. 2006, 2: 132-148.View ArticlePubMedGoogle Scholar
- Schuring RW, Spil TAM: Explaining stranded diffusion by combining the user-IT-success factors (USIT) and adopter categories: the case of electronic prescription systems for general practitioners. Int J Healtc Tech Mgmt. 2002, 4: 303-318. 10.1504/IJHTM.2002.001145.View ArticleGoogle Scholar
- NHS Connecting for Health: Electronic prescription service for dispensers. [http://www.connectingforhealth.nhs.uk/systemsandservices/eps/dispensing]
- NHS Connecting for Health: The electronic prescription service: guidance for community pharmacy contractors on implementing release 1. http://www.connectingforhealth.nhs.uk/systemsandservices/eps/library/comms/release1/guidance_comm_pharm_impr1%20.pdf]
- Harvey J, Avery AJ, Barber N: A qualitative study of community pharmacy perceptions of the EPS in England. Int Jour Pharm Practice. 2014, In printGoogle Scholar
- NHS Connecting for Health: Explaining the electronic prescription service: information for patients and carers in England. [http://www.connectingforhealth.nhs.uk/systemsandservices/eps/library/comms/release2/art.pdf]
- Todd R: NHS to be ‘paperless’ by 2015 – Kelsey. E-health Insider. [http://www.ehi.co.uk/news/primary-care/8113/nhs-to-be-‘paperless’-by-2015---kelsey]
- Bostan A: martcards in the Pharmacy Workshop. Connecting for Health. [http://www.connectingforhealth.nhs.uk/systemsandservices/eps/dispensing/smartcards/smartcardsguide.pdf]
- Höök K: User-centred design and evaluation of affective interfaces. From Brows to Trust: Evaluating Embodied Conversational Agents. Edited by: Ruttkay Z, Pelachaud C. 2005, Netherlands: Springer, 7: 127-160. 10.1007/1-4020-2730-3_5.View ArticleGoogle Scholar
- NHS Connecting for Health: Common User Interface (CUI) programme. [http://www.connectingforhealth.nhs.uk/systemsandservices/data/cui]
- Pitula K, Radhakrishna T: Proceedings of International Federation for Information Processing (IFIP) conference on Home Informatics and Telematics: ICT for the next billion. Edited by: Venkatesh A, Gunsalves T, Munk A, Bukner K. 2007, New York: Springer, 35-48. A set of heuristics for evaluating Inclusiveness of a technology, 22–25 August 2007 ChennaiGoogle Scholar
- Gulliksen J, Goransson B, Boivie I, Blomkvist S, Persson J, Cajander A: Key principles for user centred systems design. Special section “designing IT for healthy work. Behav Inform Technol. 2003, 22: 397-409. 10.1080/01449290310001624329.View ArticleGoogle Scholar
- Shah SGS, Robinson I: User involvement in healthcare technology development and assessment: structured literature review. Int J Health Care Qual Assur. 2006, 19: 500-515. 10.1108/09526860610687619.View ArticleGoogle Scholar
- Shah SGS, Robinson I: Benefits of and barriers to involving users in medical device technology development and evaluation. Int J Technol Assess Health Care. 2007, 23: 131-137.View ArticlePubMedGoogle Scholar
- Money AG, Barnett J, Kuljis J, Craven MP, Martin JL, Young T: The role of the user within the medical device design and development process: medical device manufacturers’ perspectives. BMC Med Inform Decis Mak. 2011, 11: 15-10.1186/1472-6947-11-15.View ArticlePubMedPubMed CentralGoogle Scholar
- Nielsen J: Usability Engineering. 1993, Boston: AcademicGoogle Scholar
- Norman DA, Draper SW: User Centred System Design: New Perspectives on Human-computer Interaction. 1986, New Jersey: Lawrence Erlbaum AssociatesGoogle Scholar
- Heinbokel T, Sonnentag S, Frese M, Stolte W, Brodbeck FC: Don’t underestimate the problem of user-centredness in software development projects – There are many!. Behav Inform Technol. 1996, 15: 226-236. 10.1080/014492996120157.View ArticleGoogle Scholar
- Wei X: User Experience Design: Beyond User Interface Design and Usability, Ergonomics - A Systems Approach. Tech. Edited by: Nunes IL. 2012, 171-192. [http://www.intechopen.com/books/howtoreference/ergonomics-a-systems-approach/user-experience-design-beyond-user-interface-design-and-usability]. ISBN 978-953-51-0601-2Google Scholar
- Andersson K: Proceedings of DESIGN, the 8th International Design Conference. Edited by: Marjanovic D. 2004, 91-98. [http://www.designsociety.org/publication/39/ds_32_proceedings_of_design_2004_the_8th_international_design_conference_dubrovnik_croatia], Simulation in product design: an iterative question, 18–21 May 2004; DubrovnikGoogle Scholar
- Harvey J, Avery A, Waring J, Hibberd R, Barber N: A constructivist approach? using formative evaluation to inform the electronic prescription service implementation in primary care, England. Studies in Health Technology and Informatics. 2011, 169: 374-378.PubMedGoogle Scholar
- The pre-publication history for this paper can be accessed here:http://www.biomedcentral.com/1472-6947/14/16/prepub
This article is published under license to BioMed Central Ltd. This is an Open Access article distributed under the terms of the Creative Commons Attribution License (http://creativecommons.org/licenses/by/2.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly credited.