CPIA Certification Review

Certified Pharmacy Informatics Analyst (CPIA) Review

A Review Guide for the Certified Pharmacy Informatics Analyst (CPIA) Exam

ADC: Automated Dispensing Cabinet

API: Application Programming Interface

BCMA: Bar Code Medication Administration

CDS: Clinical Decision Support

CPOE: Computerized Provider Order Entry

DDI: Drug-Drug Interaction

DUR: Drug Utilization Review

EHR: Electronic Health Record

eMAR: Electronic Medication Administration Record

FDB: First Databank

HIMSS: Healthcare Information and Management Systems Society

HIPAA: Health Insurance Portability and Accountability Act

HL7: Health Level Seven

ISMP: Institute for Safe Medication Practices

IVR: Interactive Voice Response

KPI: Key Performance Indicator

LOINC: Logical Observation Identifiers Names and Codes

NCPDP: National Council for Prescription Drug Programs

NDC: National Drug Code

PIS: Pharmacy Information System

PM: Project Management

QA: Quality Assurance

RxNorm: A standardized nomenclature for clinical drugs

SQL: Structured Query Language

UAT: User Acceptance Testing

  • Core Definition: The scientific field that focuses on medication-related data and knowledge within the continuum of healthcare systems. It is the application of technology and data science to the medication-use process to improve patient outcomes and safety.
  • The Medication-Use Process: A foundational concept. Informatics touches every step: 1) Prescribing (CPOE, CDS), 2) Transcribing, 3) Verifying, 4) Dispensing (PIS, Automation), and 5) Administering (BCMA, eMAR).
  • Role of the Informatics Analyst: To act as a liaison between the clinical (pharmacy) and technical (IT) worlds. Key responsibilities include system implementation, optimization, maintenance, and user support for all medication-related technologies.
  • Core Domains:
    • Clinical Informatics: Focuses on using technology to improve patient care (e.g., building CDS rules, designing order sets).
    • Automation & Operations: Focuses on the technology used to dispense and distribute medications (e.g., ADCs, carousels).
    • Data Analytics: Focuses on extracting, analyzing, and reporting on medication-related data to support quality improvement and research.
  • System Architecture: Understanding the relationship between the core PIS and the enterprise Electronic Health Record (EHR). Some systems are fully integrated (e.g., Epic Willow), while others are standalone PIS products that interface with the EHR.
  • Master Files & Databases: The core building blocks of the PIS. Key files include:
    • Drug Master File: Contains all information about each medication (name, dose form, strength, NDC, cost, etc.).
    • Patient Profile: Contains patient demographic information, allergies, and a list of all current and past medications.
    • Formulary File: Defines which drugs are approved for use and any associated restrictions.
  • Key System Modules: Includes modules for order entry and verification, inventory management (ordering, receiving, tracking), reporting, and billing.
  • Integration vs. Interfacing: A key concept. An integrated system shares a single database across applications (e.g., CPOE and Pharmacy). Interfaced systems are separate and pass data back and forth via messages (e.g., HL7 messages).
  • Purpose of CDS: To provide clinicians with timely, relevant, and actionable information at the point of care to help them make better decisions. The goal is to make the right thing easy to do.
  • Types of Pharmacy CDS:
    • Passive: Providing information for the clinician to use (e.g., displaying relevant lab values, links to guidelines).
    • Active (Alerts): Interruptive alerts that fire when specific criteria are met (e.g., drug-drug interaction, allergy, duplicate therapy, dose range alerts).
  • Alert Fatigue: A major challenge in informatics. If clinicians are shown too many low-relevance alerts, they begin to ignore all of them, including critical ones. A key role of the analyst is to optimize alerts to reduce noise.
  • Building & Maintaining CDS: This involves configuring rules based on institutional policies and evidence-based guidelines, testing them thoroughly before implementation, and monitoring their performance (e.g., fire rate, override rate) post-live.
  • Automated Dispensing Cabinets (ADCs): Decentralized medication storage devices located on patient care units (e.g., Pyxis, Omnicell). The analyst manages the drug database, user access, and configuration to optimize safety and inventory.
  • Centralized Robotics & Carousels: High-volume robotic systems used in the central pharmacy to automate medication storage, retrieval, and dispensing.
  • Bar Code Medication Administration (BCMA): A system that uses barcodes to electronically verify the "five rights" of medication administration (right patient, right drug, right dose, right route, right time) at the patient's bedside.
  • IV Workflow Technology: Systems that use a combination of cameras, barcode scanning, and gravimetrics to guide and verify the process of sterile compounding, improving the safety of IV preparations.
  • Health Level Seven (HL7): The primary messaging standard used to exchange clinical and administrative data between different healthcare information systems. An analyst must be able to read and troubleshoot HL7 messages (e.g., an ADT message for patient admission or an ORM message for a new order).
  • NCPDP SCRIPT Standard: The standard used for electronic prescribing, facilitating communication between prescribers' EHRs and pharmacies' PISs.
  • Key Code Sets & Terminologies:
    • National Drug Code (NDC): The FDA's unique identifier for drug products. Used for billing and inventory.
    • RxNorm: A standardized nomenclature for clinical drugs that helps achieve semantic interoperability between different systems (e.g., mapping a branded drug to its active ingredients).
    • LOINC & SNOMED CT: Standards used to code lab results and clinical observations, which are crucial for building advanced CDS rules.
  • Medication Record Build: The detailed, multi-step process of adding a new drug to the PIS/EHR database. This involves entering product details, clinical information (e.g., default dose, frequency), operational details (e.g., storage location), and billing information.
  • Formulary Maintenance: The process of keeping the system's formulary file aligned with the decisions of the organization's Pharmacy & Therapeutics (P&T) Committee. This includes adding new drugs, removing old ones, and applying restrictions or usage criteria.
  • Order Set & Protocol Build: Designing, building, and testing standardized order sets (e.g., for community-acquired pneumonia) and complex clinical protocols (e.g., heparin or insulin infusion protocols) to promote evidence-based practice.
  • Drug Pricing & Charging: Ensuring that the system accurately charges for medications dispensed, which involves maintaining drug cost files and understanding different charging methodologies (e.g., charge-on-dispense vs. charge-on-administer).

Key Performance Indicators (KPIs)

Analysts are responsible for extracting and reporting on KPIs to measure system performance and quality. Examples include order verification turnaround time (TAT), ADC stock-out rates, BCMA scan success rates, and CDS alert override rates.

BCMA Scan Rate

A critical patient safety metric that measures how consistently nurses are using the barcoding system as intended.

$ \text{BCMA Scan Rate} = \frac{\text{Scanned Administrations}}{\text{Total Administrations}} \times 100\% $

Drug Utilization Review (DUR)

Analyzing medication purchasing and usage data to identify trends, evaluate adherence to prescribing guidelines, and uncover opportunities for cost savings or quality improvement.

Data Extraction with SQL

A foundational skill. Analysts often use Structured Query Language (SQL) to query relational databases and extract raw data for analysis and reporting. A basic SQL statement is structured as:

SELECT [column_names] FROM [table_name] WHERE [condition];
  • The Project Lifecycle: Understanding the phases of a technology project: 1) Initiation, 2) Planning, 3) Execution (building and testing), 4) Monitoring & Control, and 5) Closure (go-live and support).
  • Workflow Analysis: A critical pre-implementation step involving observing and documenting current state workflows to identify gaps and design optimized future state workflows that leverage the new technology.
  • System Testing:
    • Unit Testing: Testing individual components of the build.
    • Integration Testing: Testing how different systems or modules work together.
    • User Acceptance Testing (UAT): Having end-users test the system in a controlled environment to ensure it meets their needs before go-live.
  • Go-Live & Support: Providing at-the-elbow support for end-users immediately following a system implementation, and then transitioning to a long-term plan for system maintenance and optimization.

HIMSS EMR Adoption Model (EMRAM)

A framework that scores hospitals on an 8-stage scale (0-7) based on their level of EMR adoption. A key goal for many hospitals is achieving Stage 6 or 7, which requires a "closed-loop" medication administration process (CPOE -> PIS -> BCMA).

ISMP Best Practice Guidelines

The Institute for Safe Medication Practices (ISMP) provides evidence-based guidelines for the safe use of medication technology, such as recommendations for configuring ADCs, using Tall Man lettering, and designing effective CDS alerts.

Usability Heuristics

A set of general principles for user interface design. Nielsen's 10 Usability Heuristics (e.g., "Visibility of system status," "Error prevention," "Consistency and standards") are often used to evaluate the design of health IT systems.

  • HIPAA Security Rule: The analyst plays a key role in ensuring the confidentiality, integrity, and availability of electronic protected health information (ePHI). This includes managing role-based user access, auditing system activity, and participating in risk assessments.
  • Accreditation Body Standards: Ensuring that all pharmacy technology and workflows are configured to meet the standards set by accreditation bodies like The Joint Commission (TJC), particularly their National Patient Safety Goals (NPSGs).
  • Medication Error Analysis: Using informatics tools and data to investigate the root causes of medication errors, especially those involving technology, and then designing and implementing system changes to prevent recurrence.
  • System Downtime Planning: A regulatory requirement. The analyst helps develop and test comprehensive downtime procedures to ensure patient care can continue safely during planned or unplanned system outages.
  • Safety is the Default Setting: The primary directive is to design, build, and maintain systems that make the safest choice the easiest choice for the end-user. Every decision should be viewed through a patient safety lens.
  • Be the Bridge: Success in informatics depends on your ability to speak both "pharmacy" and "IT." You must be able to translate clinical needs into technical specifications and explain technical limitations to clinicians.
  • Optimize the Workflow, Not Just the System: Technology is only effective if it works for the people using it. The best analysts focus on improving the human-computer interaction and the overall workflow, not just on configuring software.
  • Question Everything, Test Everything: A healthy skepticism is a required trait. Never assume the system will work as intended. Every new build, rule, or change must be rigorously tested to ensure it is safe and effective before it reaches a live environment.
  • Data is Your Superpower: The ability to extract, analyze, and clearly present data is what separates a good analyst from a great one. Use data to identify problems, measure the impact of your changes, and tell a compelling story about quality and value.
Return to CPIA Certification Hub