Daniel Cortes, Jodie Leung, Andrea Ryl, Jenny Lieu
As technology and innovation continue to rapidly shape health care and medication management, the need for specialized roles to support and optimize clinical workflows, system usage, and data capture is ever more important.1 Health informatics is an established field that bridges health care with information technology as a means to improve clinical care, ensure patient safety, and increase the efficiency and effectiveness of organizational processes.2 Pharmacy informatics, a subset of health informatics, leverages both clinical expertise and knowledge about information technology to improve medication management processes and drug administration safety.3 Pharmacy informaticists are pharmacists with a solid background in clinical pharmacy practice, knowledge of pharmacotherapy, and extensive working knowledge of clinical information systems and drug distribution systems.
Hospital pharmacies are well known to embrace technology and automation to support drug distribution. Between the 1980s and the 1990s, information systems were primarily used to manage pharmacy inventory and produce financial reports; then, in the early 2000s, hospitals adopted computerized practitioner order entry (CPOE) and other computerized systems with clinical decision support* (CDS) software.4 Clinicians were required to oversee and tailor these systems to actualize their utility, yet the early experience and research of these investigators described only general benefits, and they could not report or measure the systems’ effectiveness or value.5,6 During this period of rapid technological growth, hospital pharmacy departments were challenged to manage and maintain new hardware and software, employing technical analysts to support the devices and applications, while pharmacy staff optimized system use to meet clinical and dispensing needs. By the late 2000s, the health informatics field was emerging, with specialization in pharmacy practice ultimately defining the pharmacy informatics role. Pharmacy informaticists became a natural fit to engage health technology advancements, evaluate system limitations and risk, educate pharmacy end-users, and investigate system issues related to medication safety, while supporting pharmacy practice. The American Society of Health-System Pharmacists (ASHP) first described the pharmacist’s role, responsibilities, and competencies in informatics in 2006, with a recent statement update in 2016.7
The diversity in skills and pathways of those who work in pharmacy informatics has prompted the definition of core competencies that promote a technologically optimized medication-use process that is safe, effective, efficient, and timely. The ASHP defined 5 major competencies critical for pharmacy informaticists to successfully contribute to any health care organization: data, information, and knowledge management; information and knowledge delivery; practice analytics; applied clinical informatics; and leadership and management of change7 (Table 1).
Table 1 Core Competencies for Pharmacy Informaticists8*
In the remainder of this article, we discuss the advanced practice of a pharmacy informaticist within our own Canadian hospital network by highlighting past work completed and projects currently underway within our hospital organization. Using these interrelated core competencies, as outlined below, we describe how pharmacy informatics aligns people, processes, and technologies with medication management.
Pharmacy informaticists support the medication-use process through best practice management of data, information, and knowledge. Health care data, such as patients’ birthdates, laboratory test results, or drug doses, are represented by discrete numbers, descriptions, or measurements. Information is a collection of data that has been interpreted via relationships within and between separate data points, with knowledge transforming information into deliberate action.8 For example, a single blood glucose reading cannot compare (in terms of usefulness for diagnosis and treatment) to an assessment of the patient’s blood glucose trend, family history, oral glucose tolerance test result, and hemoglobin A1c (HbA1c) level. When considering these data points and information together, a clinician develops knowledge about the patient’s blood glucose control, which can be used to determine if the patient is diabetic. Related information is organized into records and files, which make up a database.
Pharmacy informaticists manage the databases that support the pharmacist’s clinical and administrative role, which is guided by the pharmacist’s practice setting and responsibilities. It is necessary that the databases, electronic medical records (EMRs), and drug distribution systems are built to promote the safe use of high-risk medications, to highlight therapeutic order sets or dosing guidelines for clinicians, and to deliver and document best practices in pharmaceutical care. The other core competencies (described in subsequent sections) are critically dependent on how data, information, and knowledge are managed, and the various examples we discuss later will relate back to this competency. The remainder of this section focuses on management of the drug database.
Developing standardized drug and order set nomenclature in the drug database is important, to provide a consistent description of a medication regardless of which system is being used. Standardized nomenclature avoids confusion within and between systems and ensures that a clinician who is ordering, validating, or administering a drug can safely identify the intended medication. In our organization, we faced numerous challenges in creating a safe medication-use system, such as identifying drugs despite character limits within our pharmacy and prescriber systems, using a US National Drug Code system for Canadian drug content, and integrating data between overlapping clinical information systems. As such, it was necessary to develop guiding principles and standard operating procedures that specified the use of generic names (versus brand names), an approval process for use of medication abbreviations, and truncation rules that prioritized the display of a drug’s salt, formulation, extended-release modifier, or strength. For example, new drug additions to the medication databases must undergo an evaluation process to ensure alignment with the database conventions and to prevent selection errors by the end-user. In a recent review for subcutaneous (SC) rituximab (Rituxan SC 120 mg/mL), we mitigated the risk of erroneously selecting intravenous (IV) rituximab (10 mg/mL) by adding the concentration and route to the drug name. We also employed this strategy when new biosimilar drugs were recently added to the formulary. In the case of filgrastim, the brand names Grastofil and Neupogen were displayed and capitalized in all systems. The naming convention we chose also aligns with Health Canada’s policy statement9 on the naming of biologic drugs, which was released earlier this year.
In another example from our organization, pharmacy informaticists discovered a system limitation that led to a database improvement. In a case of a “wrong drug” administration error, a patient incorrectly received Humalog instead of the intended order Humalog Mix 25. A review highlighted that, because of a limit on the number of characters available, the “Mix 25” text wrapped to a second line in the medication administration software, which obscured the critical information required for the nurse to select the correct product right before medication administration. In response to this incident, a comprehensive risk reduction review was completed, which led to the renaming of multiple medications to ensure that key drug data needed for identification would always be visible to clinicians at the time of medication ordering, dispensing, and administration.
The next core competency, information and knowledge delivery, involves how the databases are utilized. Pharmacy informaticists ensure that there is interoperability between the pharmacy information system and all other medication-related systems. With constant changes to clinical practice and complexities within health care, integrated systems are needed to support the delivery of accurate medication-related information to the end-user at the point of clinical decision-making. Pharmacy informaticists support best practices and apply knowledge of informatics principles, human factors, and systems design to the user interface, to ensure that there is no confusion or incorrect information at the point of care. This information delivery can be provided before decisions are made or passively as reference information. Pharmacy informaticists not only support and oversee the creation, application, delivery, and management of clinical information and knowledge, but they also inform how systems should be developed and why interoperability is essential to safe medication management.7
CDS software aids clinicians during the decision-making process by way of event-driven alerts, forcing functions, care plans, evidence-based order sets, documentation templates, and patient data summaries. With in-depth knowledge of EMR functionalities and limitations, pharmacy informaticists can translate clinical requirements and determine the best way to incorporate CDS to meet the needs of clinical workflows and patient safety. Considerations of national practice standards or locally created policies and procedures should also drive the selection of the types of CDS tools that are best suited to specific clinical scenarios, such as managing high-risk medications or guiding dose adjustments in special populations.
One such example involves using evidence-based research and clinical quality outcome data for thromboprophylaxis risk assessment to develop preprinted order sets or guideline-based risk assessment models10 and thus to reduce the unnecessary use of pharmacologic thromboprophylaxis. One of the sites within our organization implemented a mandatory CPOE module for venous thromboembolism (VTE) prophylaxis within all admission order sets, whereby the prescriber is required to document if pharmacologic thromboprophylaxis is required or contraindicated. This mandatory module serves as a forcing function for assessment and documentation for VTE prophylaxis within 24 hours of admission.
At another site in our organization, the use of medical logic modules allows flexibility to develop and customize electronic CDS tools, such as custom pop-up alerts that prompt independent double checks to be completed by nursing staff for specific medications or automatic display of important patient-specific laboratory values (e.g., serum creatinine) or key findings (e.g., weight) on the order screen to aid with decision-making at the point of order entry. In our organization, pharmacy informaticists worked with the Antimicrobial Stewardship Program to create custom reports that consolidate unit-specific treatment courses and antibiotic information to trigger prompt reassessment on the basis of specified criteria, such as critical care patients presenting with sepsis.11 CDS has also been developed to guide antibiotic prescribing based on indication, renal function, and clinical criteria for use.
Although the use of CDS systems is an asset to clinicians and their workflows, it is important to monitor and evaluate the effectiveness of these systems on the basis of ordering practices or user feedback, and adjust when required. Pharmacy informaticists play an integral role in reviewing medication safety incidents to determine whether the root cause is information system–based. They also identify opportunities to incorporate changes that will prevent potential medication incidents in the future. Given the quantity of alerts presented to clinicians, including drug interactions, allergy verification, and critical laboratory values, alert fatigue can develop. It has been reported that the override rate for medication alerts often exceeds 80%–90%, which can result in preventable adverse events leading to morbidity or mortality.12 Guidelines exist on how to effectively use and monitor alerts, given that alerts with low effectiveness and ones upon which clinicians may not agree can lead to the creation of work-around solutions.13 To mitigate these issues, it is necessary for pharmacy informaticists to take alert fatigue and data overload into account when designing CDS. At our organization, retrospective data are collected concerning alert use and overrides associated with medical incidents; these data are then reviewed by both a committee and the clinicians who commonly override alerts. It is necessary to continually perform system maintenance to ensure that CDS remains clinically appropriate, relevant, and effective for the end-user.14
The third core competency of pharmacy informaticists is to play a significant role in practice analytics with respect to medication management. Practice analytics refers to a business intelligence process that uses technology and database creation to study clinical and fiscal processes and to improve decision-making in these areas.15 Pharmacy informaticists must understand the capabilities of their system, as well as the “big picture”, to help drive pharmacy practice improvements and increase performance in the medication-use process.
As an opportunity to evaluate and measure pharmacy practice and services, one of the sites in our organization recently launched documentation of clinical pharmacy key performance indicators (cpKPIs)16 within our EMR. The existing pharmacist assessment form was enhanced, piloted, and implemented. Our updated documentation tool allowed clinical pharmacists to document their initial patient assessment with follow-up notes, and now they can select which cpKPIs have been completed throughout a patient’s admission. The data from this electronic form can be easily extracted and audited with the intention of improving clinical pharmacy services and achieving optimal patient care and safety.17
Another major undertaking at one of our sites involved the development of an enterprise data warehouse. Pharmacy informaticists were involved in this project as subject matter experts, collaborating with the decision support, project management, and research departments. The warehouse will provide clinicians with easier access to a large repository of business, operational, and clinical data that can be used for research, quality improvement initiatives, and predictive analytics. Data generated from the enterprise data warehouse are reviewed by the pharmacy informaticists to provide background understanding, to ensure queries are accurate, and to ensure that data are used in the correct context.
The next core competency of pharmacy informatics practice is applied clinical informatics, which improves clinical practice and the usability, efficiency, and safety of systems by applying “user experiences, research, and theoretical informatics principles”.7 Applied clinical informatics focuses on providing solutions that are advantageous to clinical workflows and improve every stage of medication use: ordering, processing, dispensing, and administration. Pharmacy informaticists leverage their clinical experiences to identify and evaluate the feasibility of technology-based solutions, identify gaps, and determine risks to support departmental and organizational initiatives related to medication use and electronic systems. At one of our sites, pharmacy informaticists recently led the implementation of automated dispensing units (ADUs) on inpatient and outpatient clinical units, collaborating with nursing leadership to develop key principles for system configuration and decisions surrounding emergency overrides and discrepancy management.
Although ADUs represent one of our latest improvements in stock management, our pharmacy informaticists continue to collaboratively manage back orders, nonformulary ordering, and the use of autosubstitution or therapeutic interchanges. With increased integration of technology in the drug procurement process, system changes have a broader impact, and careful consideration is required before such changes are implemented. Drug shortages and back orders have become increasingly difficult to manage in the hospital setting and require that pharmacy informaticists work alongside pharmacy technical operations staff. The severity of each shortage is assessed by evaluating existing inventory, estimated usage patterns, and availability of alternative products, while considering the impact or degree of changes on order entry and medication administration. CDS may be added to CPOE or pharmacy order processing systems to alert system users to the shortage and offer alternative actions as appropriate. For example, one site in our organization followed best practices and customized various strategies during a recent shortage of IV levofloxacin that considerably affected multiple clinical areas and medical specialties. Depending on the clinical scenario, prescribers were instructed to change the order to oral levofloxacin, use a different IV antibiotic, or use some of the limited supply of IV levofloxacin if indicated. Pharmacy informaticists updated all systems to provide guidance and information to prescribers, and careful monitoring and ongoing collaboration with distribution team members enabled pharmacy informaticists to respond rapidly when the back order was lifted.
The final core competency calls upon pharmacy informaticists to be engaged and to participate in impact analyses and change initiatives while also providing oversight of and leadership concerning the medication management systems.7 Pharmacy informaticists can manage and lead change through their involvement in project work, engagement at any stage of the project life cycle (from initiation to closing), and participation in a variety of tasks such as building, testing, and optimizing a solution. A pharmacy informaticist’s scope of practice includes clinical and policy knowledge, change management skills, project management, and also an understanding of systems technology enabling participation in or leadership of projects and initiatives within or across all sites.
Over the last few years within our organization, pharmacy informaticists have contributed their specialized knowledge and strong guidance to corporate projects such as the implementation of CPOE, IV smart pumps, ADUs, and electronic medication reconciliation. They continue to work with stakeholders in drug distribution, drug information and utilization, pharmacy clinical and technical operations, and corporate medication safety. To facilitate change management processes and knowledge transfer, one of the sites in our organization formed a committee to coordinate upcoming changes to clinical systems, determine potential impacts on end-users, support upcoming initiatives, and manage issues related to drug shortages or formulation changes. The committee includes staff members involved in medication management, such as pharmacists, pharmacy technicians, nurses, informatics specialists, and managers, and acts as a forum for continuous process improvement through biweekly meetings, which ensure that issues arising are addressed in a timely manner. A recent example of our pharmacy informaticists being leaders in change involved revision of IV bag labels to include diluent volume plus overfill. This labelling change was evaluated by the committee, and a clear communication plan was developed to address changes to the clinical systems, batch labelling, worksheets, and IV pumps to ensure that all parties involved were aware and on board.
Our pharmacy informatics team has also worked on national initiatives such as Choosing Wisely Canada. A recently implemented recommendation consisted of decreasing unnecessary blood work monitoring (e.g., international normalized ratio [INR], HbA1c, and thyroid-stimulating hormone [TSH]), improving formulary management, and revising order sets. Work efforts included decoupling the laboratory orders for INR and activated partial thromboplastin time, and the addition of CDS to affected admission order sets helped prescribers to select the suggested options. Also, routine orders for TSH and HbA1c were discouraged, both to educate prescribers about the utility of these tests and to disallow repeat ordering within specified time frames.
There are many more interesting areas within health and pharmacy informatics to learn about and further develop. We have described only some examples of a pharmacy informaticist’s operational responsibilities and current initiatives, but we foresee that the future holds many exciting changes.
The health informatics curriculum is well established in medical and nursing training; however, in pharmacy, it has been slower to evolve.18 A 2017 survey of pharmacy curriculums in the United States showed that only 36% included an informatics course, which was not much of an improvement from 10 years before.19 Pharmacy or health informatics courses are now offered in most Canadian pharmacy faculties; however, many of those currently working in the field entered with little to no formal education or training. Rather, skills have been gained through on-the-job experience, by working alongside nonpharmacy clinical informatics colleagues, through education provided by information system vendors, by attending public interest conferences, or through continuing education. There is a recognized need for advanced training in the pharmacy informatics field to support systems innovation to “enable a shift to a more fully system-supported pharmacy practice”.20
“Big data”, a term referring to large and complex data sets from many data sources,21 is being leveraged to improve clinical decision-making and pharmacy research.22 Artificial intelligence and machine learning are becoming the future of health care, whereby computers are used to simulate learning, analysis, and prediction.23 In terms of application to pharmacy and medication management, development is currently underway to assist in many areas, such as drug design,24 formulary selection, choice of drug therapy,25 treatment predictions and results, health care data processing (e.g., diagnostic tests, wearable devices, and natural language processing26), potential drug interactions or adverse event alerts, and adherence monitoring.27 In the coming years, pharmacy informaticists will be essential to the development and adoption of artificial intelligence tools to ensure that data currently captured and used for computation are meaningful and accurate.
The creation of larger hospital networks will prompt the work of understanding needs across various clinical and financial systems for the affected institutions. Challenges to harmonize the practices of multiple hospitals of different sizes, using different information systems and with different levels of patient acuity, must be anticipated, and it is important that pharmacy informatics is represented at all sites, with collaboration at all organizational levels.28 Increased representation of pharmacy informatics would certainly create opportunities to encourage further growth of the field and to promote pharmacy informaticists’ role as leaders at the place where information technology and medication management meet.
Although it is not new, the practice of pharmacy informatics is in a state of rapid growth. This diverse and evolving field leads the use of technology at multiple levels of pharmacy practice, from departmental projects to national collaboratives. Equipped with a strong understanding of medication management workflows and knowledge of clinical system functionalities, pharmacy informaticists are in a great position to collaborate with other health care providers to optimize information management, improve workflow, and reduce medication errors. By supporting and developing the pharmacy informaticist role, the profession of hospital pharmacy can optimize innovations to medication-related processes so that pharmacists can continue to improve patient care and outcomes.
1 Better information for improved health: a vision for health system use of data in Canada. Ottawa (ON): Canadian Institute for Health Information; 2013. Available from: https://www.cihi.ca/en/hsu_vision_report_en.pdf
2 El Morr C. Introduction to health informatics: a Canadian perspective. Toronto (ON): Canadian Scholars; 2018. Available from: https://www.canadianscholars.ca/books/introduction-to-health-informatics
3 Pharmacy informatics community. Chicago (IL): Healthcare Information and Management Systems Society; 2019 [cited 2019 Jan 17]. Available from: https://www.himss.org/library/pharmacy-informatics
4 Pitre M. Should pharmacy informatics officer positions be based in, and report to, the pharmacy department, rather than the health information technology department? The “pro” side. Can J Hosp Pharm. 2011;64(6): 459–60.
5 Jones SS, Rudin RS, Perry T, Shekelle PG. Health information technology: an updated systematic review with a focus on meaningful use. Ann Intern Med. 2014;160(1):48–54.
6 Hersh WR, Totten AM, Eden KB, Devine B, Gorman P, Kassakian SZ, et al. Outcomes from health information exchange: systematic review and future research needs. JMIR Med Inform 2015;3(4):e39. 
7 American Society of Health-System Pharmacists. ASHP statement on the pharmacist’s role in clinical informatics. Am J Health Syst Pharm. 2016;73(6):410–3.
8 Fox BI, Thrower MR, Felkey BG, editors. Building core competencies in pharmacy informatics. Washington (DC): American Pharmacists Association; 2010.
9 Notice to stakeholders – policy statement on the naming of biologic drugs. Ottawa (ON): Health Canada; 2019 [cited 2019 Jul 19]. Available from: https://www.canada.ca/en/health-canada/services/drugs-healthproducts/biologics-radiopharmaceuticals-genetic-therapies/biosimilarbiologic-notice-to-stakeholders-drugs-naming-of-biologics.html
10 Rafizadeh R, Turgeon RD, Batterink J, Su V, Lau A. Characterization of venous thromboembolism risk in medical inpatients using different clinical risk assessment models. Can J Hosp Pharm. 2016;69(6):454–9.
11 Taggart LR, Leung E, Muller MP, Matukas LM, Daneman N. Differential outcome of an antimicrobial stewardship audit and feedback program in two intensive care units: a controlled interrupted time series study. BMC Infect Dis. 2015;15(1):480.
12 Brodowy B, Nguyen D. Optimization of clinical decision support through minimization of excessive drug allergy alerts. Am J Health Syst Pharm. 2016;73(8):526–8.
13 Troiano D, Jones MA, Smith AH, Chan RC, Laegeler AP, Le T, et al. ASHP guidelines on the design of database-driven clinical decision support: strategic directions for drug database and electronic health records vendors. Am J Health Syst Pharm. 2015;72(17):1499–505.
14 Lam JH, Ng O. Monitoring clinical decision support in the electronic health record. Am J Health Syst Pharm. 2017;74(15):1130–3.
15 Dumitru D, editor. The pharmacy informatics primer. Bethesda (MD): American Society of Health-System Pharmacists; 2009.
16 Fernandes O, Toombs K, Pereira T, Lyder C, Bjelajac Mejia A, Shalansky S, et al. Canadian consensus on clinical pharmacy key performance indicators: knowledge mobilization guide. Ottawa (ON). Canadian Society of Hospital Pharmacists; 2015. Available from: https://www.cshp.ca/sites/default/files/files/publications/Official%20Publications/CPKPI/CSPH-Can-Concensus-cpKPI-QuickReferenceGuide_June_2017.pdf
17 Lo E, Rainkie D, Semchuk WM, Gorman SK, Toombs K, Slavik RS, et al. Measurement of clinical pharmacy key performance indicators to focus and improve your hospital pharmacy practice. Can J Hosp Pharm. 2016; 69(2):149–55.
18 Fox BI, Flynn A, Clauson KA, Seaton TL, Breeden E. An approach for all in pharmacy informatics education. Am J Pharm Educ. 2017; 81(2):Article 38.
19 Clauson KA, Breeden EA, Fingado AR, Kaing CL, Flynn AJ, Cutler TW. A progress report on the state of pharmacy informatics education in US pharmacy schools and colleges. Am J Pharm Educ. 2018;82(7): Article 6332.
20 Flynn A, Fox BI, Clauson KA, Seaton TL, Breeden E. An approach for some in advanced pharmacy informatics education. Am J Pharm Educ. 2017;81(9):Article 6241.
21 Stokes LB, Rogers JW, Hertig JB, Weber RJ. Big data: implications for health system pharmacy. Hosp Pharm. 2016;51(7):599–603.
22 Flynn AJ, Stevenson JG. The future of data, analytics, and information technology. Am J Health Syst Pharm. 2018;75(2):31–4.
23 Weins J, Shennoy ES. Machine learning for healthcare: on the verge of a major shift in healthcare epidemiology. Clin Infect Dis. 2018;66(1):149–53.
24 Mak KK, Pichika MR. Artificial intelligence in drug development: present status and future prospects. Drug Disc Tod. 2019;24(3):773–80.
25 Salmasian H, Tran TH, Chase HS, Friedman C. Medication-indication knowledge bases: a systematic review and critical appraisal. J Am Med Inform Assoc. 2015;22(6):1261–70.
26 Wong A, Plasek JM, Monteclavo SP, Zhou L. Natural language processing and its implications for the future of medication safety: a narrative review of recent advances and challenges. Pharmacotherapy. 2018; 38(8):822–41.
27 Dasta JF. Application of artificial intelligence to pharmacy and medicine. Hosp Pharm. 1992;27(4):312–5,319–22.
28 Chalmers J, Siska M, Le T, Knoer S. Pharmacy informatics in multihospital health systems: opportunities and challenges. Am J Health Syst Pharm. 2018;75(7):457–64.
Competing interests: None declared. ( Return to Text )
*Bold indicates terms that are defined in Appendix 1. ( Return to Text )
The authors are grateful to Linda Stoyanoff for her contributions to content research, writing assistance, technical editing, and proofreading in advance of submission.
Canadian Journal of Hospital Pharmacy, VOLUME 72, NUMBER 4, July-August 2019
