Study guide
6.2 Healthcare IT Vocabulary
Certified Professional in Healthcare Information and Management Systems CPHIMS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Eligibility Pathways and Qualifying Experience 1.3 Scoring, Retakes, and Recertification 1.4 Domain-Weighted Study Strategy
2 Healthcare Organizations and Relationships
2.1 Hospitals, Clinics, Ambulatory, and Community Organizations 2.2 Payers, Regulators, Research, and Academic Organizations 2.3 Interrelationships, HIE, and Continuity of Care 2.4 HIT Professional Roles and Organizational Structures
3 Policy, Accreditation, and Care Trends
3.1 Privacy and Security Law: HIPAA and HITECH 3.2 Interoperability Policy and Information Blocking 3.3 Accreditation, Patient Rights, and Environments of Care 3.4 Telehealth, Portals, Wearables, and Population Health
4 Healthcare Applications
4.1 Clinical Applications 4.2 Administrative and Financial Applications 4.3 Consumer-Facing Applications 4.4 Business Intelligence Applications
5 Technology Infrastructure
5.1 Networks and Communications 5.2 Data Integration Architectures 5.3 Infrastructure Privacy and Security 5.4 Cloud, Devices, and Identity Infrastructure
6 Clinical Language, Terminologies, and Metrics
6.1 Clinical Vocabulary 6.2 Healthcare IT Vocabulary 6.3 Clinical Terminologies: SNOMED CT, LOINC, RxNorm, and ICD 6.4 Clinical Metrics and Operational Measures
7 Clinical Effectiveness and Workflows
7.1 System Functionality for Clinical Effectiveness 7.2 Workflows, Order Sets, and Pathways 7.3 Safety, Quality, and Clinical Informatics Design
8 Informatics Analytics
8.1 Analytics Tools, Reports, Tables, and Graphs 8.2 Interpreting Clinical and Operational Outcomes 8.3 Predictive Models in Care and Operations
9 Clinical Content and Decision Support
9.1 Clinical Content Lifecycle 9.2 Clinical Decision Support Types and Design 9.3 CDS Governance, Alert Management, and Knowledge Maintenance
10 Analysis, SDLC, and Improvement Methods
10.1 Systems Development Life Cycle 10.2 Project Management: Needs, Gap, and Requirements 10.3 Process Improvement: DMAIC and PDCA 10.4 Process Maps, Flow Diagrams, and Gap Analysis
11 Analysis: Solutions and the Business Case
11.1 Disparate Data Sets and Alternate Solutions 11.2 Strategic Alignment and Cost-Benefit Analysis 11.3 Proposals, RFPs, RFIs, SLAs, SOWs, and NDAs
12 Systems Design
12.1 Interoperability of Software, Hardware, Networks, and Devices 12.2 Design Compliance and Incorporating Industry Trends 12.3 Business Continuity and Disaster Recovery Design 12.4 Emerging Technologies and Data Governance
13 Selection, Implementation, Support, and Maintenance
13.1 Solution Selection Activities 13.2 Technical Change Management, Training, and Support 13.3 Implementation: Scope, Schedule, Budget, and Quality 13.4 Maintenance, Operations, and Problem-Trend Analysis
14 Testing, Evaluation, Privacy, and Security
14.1 Testing Methodology and Internal Controls 14.2 Validation and Benefits Realization 14.3 Privacy and Security Policies, Access, and Safeguards 14.4 Vulnerabilities, Roles, Data Controls, and Ongoing Validation
15 Strategy and IT Planning
15.1 Contributing to Organizational Strategic Planning 15.2 Assessing the Organizational Environment 15.3 Forecasting Technical and Information Needs 15.4 IT Strategic Plans and Departmental Objectives
16 Performance, Policy, Ethics, and Analytics
16.1 Evaluating Performance Against SLAs and Indicators 16.2 User Satisfaction and Service Effectiveness 16.3 Policies, Legal Compliance, and Ethical Principles 16.4 Comparative Analytics and Presenting Recommendations
17 Communication, Stakeholders, and Change
17.1 Promoting Stakeholder Understanding of IT Opportunities and Constraints 17.2 Business Communications and Consultative Technology Services 17.3 Facilitating Groups, Consensus, and Conflict Resolution 17.4 Organizational Change Management and Stakeholder Relationships
18 People, Projects, Vendors, and Finance
18.1 HIT Roles, Job Descriptions, and Staff Competency 18.2 Educational Strategies and Maintaining IT Competencies 18.3 Managing Projects and Portfolios 18.4 Vendor Contracts, Budgets, and Risk Management
6.2 Healthcare IT Vocabulary
Key Takeaways Explain This Topic AI
Domain 2 task A.2 tests healthcare IT words used in informatics settings: EHR, CPOE, CDS, HIE, ADT, MPI, interface, API, downtime, and uptime.
CPOE is the act of entering orders electronically. CDS is the knowledge and alerts layered on workflows. One can exist with a weak version of the other.
ADT is an event stream (admit, discharge, transfer, and related updates). MPI is the identity register that says which person those events belong to.
An interface is typically message-based exchange (often HL7 v2 through an engine). An API is a callable contract (often FHIR over HTTP). Both integrate; they are not the same pattern.
Downtime is unavailability, planned or unplanned. Uptime is availability. A down interface is not automatically a down EHR, and a high uptime percentage does not erase the need for downtime procedures.
Last updated: August 2026
6.2 Healthcare IT Vocabulary
Quick Answer: Task A.2 is workplace English for informatics. An EHR stores the longitudinal record. CPOE is electronic order entry. CDS is decision support. HIE shares data across organizations. ADT announces movement events. MPI keeps one person identity. An interface moves messages; an API exposes a callable contract. Downtime is unavailability; uptime is availability.
If task A.1 is how clinicians talk, task A.2 is how analysts, interface engineers, and nursing informatics coordinators talk in the same meeting. CPHIMS will not award points for using the words as decorations. It will ask who owns the failure when “ADT is down,” whether a new alert is CPOE or CDS, and whether a FHIR query is the same thing as the lab interface.
This vocabulary also appears in Domain 1 applications and Domain 3 interoperability. Learn the distinctions here so later chapters can assume them. Drill mixed stems in CPHIMS practice .
EHR — the system of clinical record
An electronic health record (EHR) is the organization’s (and, at its best, the person’s) longitudinal clinical record: problems, allergies, medications, immunizations, history, notes, results, orders, and often the visit and inpatient stay around them. People still say EMR (electronic medical record) for a single-organization chart. In CPHIMS conversation, do not waste time on a purity debate. Do lock the operational meaning: the EHR is the system of record clinicians document in, not the data warehouse, not the HIE, and not the billing system that happens to store a diagnosis.
Related modules you will hear in the same breath: eMAR (electronic medication administration record), BCMA (barcode medication administration), inpatient versus ambulatory charts, and the patient portal or personal health record view. Those are functions or layers. They are not substitutes for the word EHR when the stem is about the legal medical record.
CPOE and CDS — entry versus advice
Computerized provider order entry (CPOE) is the electronic capture of orders by a licensed ordering clinician—or, in some workflows, by a protocol or verbal-order entry with the right authentication. Medications, labs, imaging, diets, nursing orders, and referrals all sit in CPOE. The point of CPOE is a legible, structured, authenticated order that can drive pharmacy, laboratory, radiology, and nursing worklists. CPOE is not automatically safe. A complete CPOE catalog can still let a user order a fatal dose if no knowledge sits on top of it.
Clinical decision support (CDS) is the knowledge, logic, and presentation that help a clinician decide or act: drug-allergy checking, dose range, duplicate therapy, corollary orders (“you ordered a CT with contrast—check creatinine”), preventive reminders, order sets, infobuttons, and predictive flags. CDS can fire inside CPOE, inside documentation, at results review, or at handoff. CPOE without CDS is electronic handwriting. CDS without a workflow is a PDF of guidelines nobody opens.
Exam trap: a stem that says “build CPOE so the potassium cannot be given IV push” is really asking for product/route constraints plus CDS or hard stops , not for “more CPOE.” A stem that says “providers refuse to use order entry because of alerts” is a CDS design and governance problem, not proof that CPOE should go back to paper.
HIE — exchange across boundaries
A health information exchange (HIE) is the capability—and often the organization—that moves clinical data across unaffiliated or separately governed entities: hospital to independent clinic, emergency department to primary care, public-health reporting, or a regional query for outside encounters. HIE may use an interface engine, FHIR APIs, a record-locator service, and consent rules. The EHR can participate in HIE. The EHR is not itself “the HIE” just because two clinics share a vendor.
If the stem is about a patient arriving from another health system with no local history, the first vocabulary word is HIE (or at least external query), not “open a bigger EHR.”
ADT and MPI — movement versus identity
ADT means admission, discharge, and transfer . In operations it is both a set of real-world events and the classic HL7 v2 message family that announces them (and related updates such as cancel admit, change patient location, or merge). ADT messages keep downstream systems honest: lab needs a location, dietary needs a bed, radiology needs a visit, the bed board needs occupancy, the portal needs an encounter. When people say “ADT is down,” they usually mean the event feed is not updating subscribers. The EHR chart may still be open.
The master patient index (MPI) —and its enterprise form, EMPI —is the register of who the person is : identifiers, demographics, and the links among medical record numbers across facilities. MPI answers “is this the same human?” ADT answers “what just happened to an encounter or location for a human we think we know?” ADT demographics can update the MPI. They are not the MPI.
MPI failures have two famous shapes. A duplicate is two charts for one person—split history, missed allergies, repeated labs. An overlay is two people crushed into one chart—the worse safety event. Informatics language should keep those words distinct from “the ADT interface failed.”
Interface versus API
An interface in health-IT speech almost always means a message-based , often asynchronous connection: HL7 v2 ORM/ORU/ADT, X12 for claims, sometimes a vendor-specific feed, usually mediated by an interface engine . You reason about acknowledgements, queues, gap fills, and “the feed is backed up.”
An application programming interface (API) is a callable contract : a client requests a resource and gets a response. In current U.S. interoperability policy the usual clinical API is HL7 FHIR over HTTP, often with SMART-on-FHIR authorization. You reason about endpoints, scopes, rate limits, and versioned resources (Patient, Encounter, Observation, MedicationRequest).
Both move data. They fail differently. An interface engine can queue ADT while the EHR stays up. An API can return 401 Unauthorized while the lab interface is healthy. Saying “just build an interface” when a third-party app needs a patient-facing FHIR API is the wrong vocabulary and the wrong security model.
Downtime and uptime
Downtime is the period when a system or a critical function is unavailable. Planned downtime is a scheduled maintenance window. Unplanned downtime is an incident. Read-only downtime may still allow chart review from a replica or downtime viewer. Total downtime means document and medicate from downtime procedures—paper, downtime codes, or a backup device. Domain 3 will treat business continuity more fully; task A.2 only needs you to use the words correctly and to know that every production EHR needs a downtime procedure , not a hope that outages will not happen.
Uptime is availability—the complement of downtime, often discussed as a percentage over a month or year. CPHIMS does not publish an official uptime formula or a required 9’s target. Operationally, a vendor or internal SLA may state a percentage, and operations will still count minutes that mattered (CPOE down at 07:00 is not the same as a report server down at 02:00). Do not treat a high uptime slide as proof that barcode administration or ADT never failed. Partial functional outages are still downtime for the people who needed that function.
- Term What it names Common false synonym
- EHR Longitudinal clinical system of record HIE, data warehouse, claims system
- CPOE Electronic order capture CDS, e-prescribing alone, the entire EHR
- CDS Knowledge and interventions that guide decisions CPOE, the alert banner only
- HIE Cross-organization exchange Two departments sharing one EHR
- ADT Movement and encounter events / their messages MPI, bed board hardware
- MPI Person identity register The medical record number sticker, ADT
- Interface Message-based integration Any integration, including a FHIR API
- API Callable application contract A nightly flat-file drop
- Downtime Function or system unavailable Only a total building blackout
- Uptime Availability over a period “We had no tickets, so we were up”
Loading diagram... Where healthcare IT terms sit in a live environment
Scenarios and exam traps
Scenario. Nurses report “the EHR is down” because labels are not printing and dietary does not know the new room. The chart is open, CPOE works, and BCMA works. Vocabulary: the ADT interface (or a subscriber) is down, not the entire EHR. Page the integration on-call, not a full downtime paper chart—unless your procedure says otherwise for that failure mode.
Scenario. A quality committee wants “more CPOE” to stop duplicate CT scans. Providers already enter orders electronically. The gap is CDS (duplicate-study checking, indication capture) and perhaps HIE visibility of outside imaging—not a second order-entry module.
Scenario. A digital vendor asks for “an ADT interface so the patient can download their record in the app.” That request mixed three words. Patient access is usually an API (and a portal), identity is MPI , and ADT might still notify the vendor of encounters. Design the contract that matches the use case.
Watch these traps:
Calling shared-EHR visibility an HIE.
Treating CPOE and CDS as one word.
Using MPI and ADT interchangeably.
Calling every integration an interface, including SMART-on-FHIR apps.
Declaring uptime “fine” because the login page loaded while CPOE was frozen.
Skipping downtime procedures because last quarter’s availability slide looked green.
When a stem piles on acronyms, translate each one to a job: record, order, advice, exchange, event, identity, message, call, outage, availability. The right owner and the right fix follow the right noun.