Study guide

6.1 Clinical 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.1 Clinical Vocabulary

Key Takeaways Explain This Topic AI

Domain 2 task A.1 tests clinical words that actually change informatics builds: dosage frequency, routes, body systems, and terms such as NPO, PRN, STAT, allergy, intolerance, and problem list.

Frequency and route are order-catalog and eMAR fields, not decoration: BID is not the same as every 12 hours, and a PO med does not survive an NPO diet unless the build says otherwise.

Allergy is an immune-mediated reaction; intolerance or side effect is a non-immune adverse effect. Mixing them in one allergy table corrupts clinical decision support.

A problem list is a maintained longitudinal record of active and resolved conditions. It is not the same as an encounter diagnosis or a billing ICD code.

STAT means immediate priority. PRN means as needed and requires an indication plus dose and frequency limits. NPO means nothing by mouth and must interact with oral medications and procedures.

Last updated: August 2026

6.1 Clinical Vocabulary

Quick Answer: Domain 2 task A.1 is the clinical language of informatics builds. Know dosage frequency (BID, Q8H, PRN, STAT), routes (PO, IV, IM, SQ, SL), body systems , and the chart words that become EHR fields: NPO , PRN , STAT , allergy versus intolerance , and problem list . They are design requirements, not medical-school trivia.

Clinical Informatics is 20% of CPHIMS. Task A.1 sits first because every later informatics choice—order sets, decision support, metrics, content lifecycle—assumes you can read a chart the way a clinician writes it. You do not need to be a licensed independent practitioner. You do need to know why a pharmacist will reject an order that says “QD PRN pain PO/IV,” why an NPO diet that leaves oral tablets active is a safety defect, and why coding metformin nausea as an allergy floods the next admission with false alerts.

Use free CPHIMS practice questions after this chapter to rehearse application stems. Adjacent quality and health-information credentials such as CPHQ and RHIA share some vocabulary; they do not replace this informatics reading of the same words.

Why clinical vocabulary is an HIT skill

An informatics professional translates spoken clinical language into structured fields. Frequency becomes a schedule. Route becomes a product filter and an administration check. Body system becomes a flowsheet grouping, a review-of-systems template, or a CDS scope. Allergy versus intolerance becomes two different safety behaviors. Problem versus encounter diagnosis becomes two different lists with two different maintenance rules.

Exam stems hide the vocabulary inside a build request: “the night nurse needs a now dose,” “the patient is NPO for endoscopy,” “the problem list is just ICD codes from last year’s claim,” “the allergy list is full of nausea and constipation.” Name the clinical concept first, then pick the system behavior that matches it.

Dosage frequency

Dosage frequency answers when and how often a medication or treatment should occur. In CPOE and the electronic medication administration record (eMAR), frequency is a coded schedule, not free text.

Common scheduled frequencies:

Abbreviation or phrase Meaning in an order catalog Informatics implication

Daily / every day Once per calendar day, usually at a standard administration time Map to a timed frequency, not a leftover “QD” string if your safety policy bans that abbreviation

  • BID Twice daily Two administration windows; not automatically every 12 hours
  • TID Three times daily Often with meals or at 08-14-20 style times, depending on pharmacy standards
  • QID Four times daily Four windows; not the same as every 6 hours unless the catalog says Q6H

Q4H, Q6H, Q8H, Q12H Every stated number of hours around the clock Clock-based, including overnight; different from meal-tied BID/TID

  • HS / at bedtime Once at bedtime Timing follows sleep, not a 24-hour clock start
  • AC / PC Before meals / after meals Needs a meal-time association, not a fixed clock
  • PRN As needed Requires indication, minimum interval, and often a maximum daily dose
  • STAT Immediately Highest priority queue for pharmacy, nursing, and often the lab

NOW / ASAP Very soon, but not the emergency STAT path Separate priority; do not collapse it into STAT or routine

BID is not Q12H. Twice-daily often means morning and evening waking hours. Every 12 hours means a 24-hour clock, including a nighttime dose. Antibiotics, anticoagulants, and anticonvulsants frequently need the clock interval. Sleeping pills and some antihypertensives frequently need the waking-hours pattern. If the catalog has only one “twice a day” concept, clinicians will pick it for both intents and the eMAR will fire at the wrong times.

PRN is incomplete without an indication. “Oxycodone 5 mg PO Q4H PRN” is not a finished order. PRN for what—pain, and at what severity? What is the lockout? What is the 24-hour ceiling when a second PRN opioid also exists? Informatics builds should force reason , minimum interval , and dose limits , then require effectiveness documentation after administration. A PRN without those fields is how double-dosing and incomplete pain reassessment hide in the data.

STAT is a priority, not a synonym for important. STAT means drop competing work and give or draw now. NOW or ASAP means soon, typically within a short operational window defined by the organization. Routine means the next standard cycle. If every “please do this today” order is built as STAT, pharmacy queues, lab couriers, and nurse worklists become useless. Design three (or more) discrete priorities and teach them; do not let STAT become a cultural shout.

The Joint Commission and many medication-safety programs treat some Latin fragments as dangerous abbreviations— QD , QOD , U , trailing zeros after a decimal. CPHIMS does not publish its own abbreviation statute. The informatics job is still to keep those strings out of pick-lists and to display daily , every other day , and units in plain language.

Dosage routes

Route is how the product enters the body. It drives which NDC or compound is selected, which barcode is valid, which device is needed, and whether an NPO state should block the task.

  • Route Meaning Build consequence
  • PO By mouth Blocked or questioned by NPO unless an “NPO except meds” rule exists
  • SL Under the tongue Not the same as swallow; still a mucosal route

IV / IVP / IVPB Intravenous, push, or piggyback Requires a product that is IV-compatible and usually a pump or flush workflow

  • IM Intramuscular Site and volume limits; not interchangeable with IV
  • SQ / subcut Subcutaneous Insulin, heparin, some biologics; site rotation documentation
  • PR Rectal Alternate when PO is not possible; still not IV
  • INH / NEB Inhaled or nebulized Device association; not a tablet
  • TOP / TD Topical or transdermal Patch timing and remaining-patch checks
  • NG / NJ / PEG Enteral tube Formulation must be tube-safe; do not crush every PO tablet
  • Ophthalmic / otic Eye / ear Laterality (left, right, both) is part of the order

A single medication name can have several safe routes and several unsafe ones. Potassium chloride oral is not potassium chloride IV push. The catalog must separate products by route so barcode medication administration cannot “succeed” on the wrong form.

Body systems

Clinicians organize assessment and problems by body system : cardiovascular, respiratory, gastrointestinal, genitourinary and renal, neurologic, endocrine, musculoskeletal, integumentary, hematologic, immune, reproductive, and HEENT (head, eyes, ears, nose, throat). Informatics uses the same map:

Flowsheets and device data (cardiac rhythm, respiratory rate, urine output) group by system so a rapid assessment is scannable.

Review-of-systems templates and history-and-physical structures follow the same headings.

Problem lists and order-set catalogs are often chaptered by system so a heart-failure set does not bury endocrine labs.

CDS scope is often system-specific: renal dosing for a rising creatinine, respiratory holds for a sedative in a CO2 retainer.

You will not be asked to recite every organ. You will be asked whether a build request belongs in the cardiovascular order set, the renal dosing alert, or a generic “misc” folder that nobody will find.

Chart words that become modules

NPO ( nil per os , nothing by mouth) is a diet and procedure state. It is not only a cafeteria instruction. A correct build coordinates diet orders, oral medications, oral contrast, and pre-procedure checklists. Variants such as “NPO except sips of water” or “NPO except medications” must be discrete values, because they change different downstream tasks. If diet NPO does not notify pharmacy or create a medication-route question, the eMAR will still offer the morning PO tablets.

Allergy versus intolerance. An allergy is an immune-mediated reaction—urticaria, angioedema, anaphylaxis, some severe cutaneous reactions. An intolerance , side effect, or adverse sensitivity is a non-immune unwanted effect: nausea from codeine, diarrhea from metformin, drowsiness from diphenhydramine. Both belong in the record. They do not belong in one unstructured “allergy” bucket with the same interruptive alert. If nausea is coded as an allergy to “opioids,” every future analgesic may hard-stop. If anaphylaxis to penicillin is coded as a mild intolerance, the next prescriber may re-expose the patient. Collect substance , reaction , severity , and type (allergy versus intolerance). Cross-sensitivity decision support depends on that structure.

Problem list. A problem is a condition the team is managing over time: heart failure with reduced ejection fraction, type 2 diabetes, chronic kidney disease stage 3. The list should support active , resolved , and sometimes historical states. It is not:

  • the encounter diagnosis for this visit only,
  • the billing diagnosis chosen to support a claim, or

a dump of every lab abnormality that ever filed.

Informatics consequence: prefer native clinical concepts (typically SNOMED CT, taught in 6.3) on the problem list, keep the list curated, and map outbound for reporting. A problem list that is only last month’s ICD codes is a claims residue, not a clinical tool.

Other terms that appear constantly in builds: NKA / NKDA (no known allergies / no known drug allergies) is a documented negative, not a blank field; code status and advance directives are discrete safety fields; I&O is intake and output, a flowsheet not a note phrase; MAR / eMAR is the administration record; hold parameters (hold beta blocker if heart rate below a stated value) are part of the order, not a sidebar comment; indication is why the drug is ordered and is required for many antimicrobials and PRN drugs.

How the vocabulary shows up in a real build

Imagine a pre-op order set for endoscopy. The surgeon wants the patient NPO after midnight , a STAT IV start if the patient arrives dehydrated, ondansetron 4 mg IV Q6H PRN nausea , and home lisinopril held. The informatics checklist is: NPO as a diet/state that questions PO meds; STAT as a true priority for the IV; PRN with indication nausea plus a lockout; hold parameters or a discrete hold order for the ACE inhibitor; problem-list hypertension left active because holding a dose does not resolve the disease. That is task A.1 in operational clothing.

Loading diagram... Clinical words that become EHR fields

Scenarios and exam traps

Scenario. A hospitalist writes “metoprolol 25 mg BID.” Cardiology wants Q12H for a post-MI patient. If the catalog has only BID, the night dose may never appear. Create both frequencies and display the difference in clinician language.

Scenario. The allergy list contains “morphine — nausea” and “penicillin — anaphylaxis” as the same allergen type. CDS will either over-block opioid choices or under-block beta-lactams. Split type and severity.

Scenario. Leadership asks IT to auto-add every billed ICD code to the problem list at discharge. The list will fill with encounter residue and lose clinical trust. Map claims outbound; do not let billing write the longitudinal record unreviewed.

Watch these traps:

Treating BID, TID, and Q8H as interchangeable “a few times a day.”

Building STAT as the only way to make an order visible.

Allowing NPO diets that do not touch PO medication tasks.

Storing intolerance and allergy as one concept.

Equating problem list, encounter diagnosis, and billed ICD.

Leaving PRN without indication or maximum frequency.

Those mistakes become later Domain 2 failures in order sets, decision support, and metrics. Learn the words here so chapter 7’s workflows have something safe to automate.