Study guide

1.4 Parts of the EHR & Core Functions of the Electronic Record

NHA Certified Electronic Health Records Specialist CEHRS

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the NHA CEHRS Exam The CEHRS Test Plan & How to Use This Guide

2 Chapter 1: Foundations — Medical Terminology, Health Care Settings & the EHR

1.1 Medical Terminology I: Roots, Prefixes, Suffixes & Combining Forms 1.2 Medical Terminology II: Body Systems, Directional Terms & Clinical Abbreviations 1.3 Health Care Systems, Settings, Personnel & Credentials 1.4 Parts of the EHR & Core Functions of the Electronic Record 1.5 Regulatory Agencies, Professional Standards & Population Health Concepts

3 Chapter 2: Non-Clinical Operations — Patient Registration & Scheduling

2.1 Patient Registration & Intake Workflows 2.2 Master Patient Index (MPI) & Demographic Management 2.3 Appointment Scheduling & Resource Management 2.4 Patient Communication, Portals & Front-Office Operations 2.5 Encounter Documentation: Face Sheets, Labels, Armbands & Check-Out

4 Chapter 3: Non-Clinical Operations — Health Record Administration & Archiving

3.1 Health Record Types, Hybrid Systems & Data Conversion 3.2 Record Retention, Storage & Archival Policies 3.3 Release of Information (ROI) & Authorization Procedures 3.4 Auditing, Chart Maintenance & Record Integrity

5 Chapter 4: Non-Clinical Operations — Data Sources, Devices & EHR User Support

4.1 Retrieving Patient Data from Internal Databases (Provider, Payer & Financial) 4.2 Acquiring Patient Data from External Sources 4.3 Importing from Integrated Devices & Managing EHR Hardware Inventory 4.4 Identifying, Reporting & Reconciling Data Discrepancies 4.5 End-User EHR Training, Competency & Training Documentation 4.6 Communicating Software Updates, IT Troubleshooting & Escalation

6 Chapter 5: Clinical Operations — Clinical Intake, Point-of-Care & Vitals

5.1 Clinical Intake, Rooming & Vital Signs Documentation 5.2 Chief Complaint, History of Present Illness (HPI) & ROS 5.3 Physical Exam Documentation & Clinical Notes Formatting (SOAP) 5.4 Allergy Documentation, Adverse Reaction Logging & Safety Alerts 5.5 Problem Lists, Medical History & Immunization Tracking 5.6 Patient Education Materials in the EHR & Scope of Practice

7 Chapter 6: Clinical Operations — Templates, Documentation Review & Data Retrieval

6.1 Developing Clinical Templates for Data Capture 6.2 Reviewing Clinical Documentation for Completeness & Accuracy 6.3 Point-of-Care EHR Support & Telehealth Workflows 6.4 Navigating the EHR to Retrieve Requested Patient Data 6.5 Securely Transmitting & Exchanging Patient Data

8 Chapter 7: Clinical Operations — CPOE, Orders & Decision Support

7.1 Computerized Provider Order Entry (CPOE) Fundamentals 7.2 Laboratory & Diagnostic Test Order Entry and Results Tracking 7.3 Medication Reconciliation, e-Prescribing & Formulary Checks 7.4 Clinical Decision Support Systems (CDSS) & Practice Guidelines 7.5 Clinical Care Coordination, Referrals & Discharge Planning

9 Chapter 8: Revenue Cycle & Financial Management

8.1 Insurance Verification, Eligibility (EDI 270/271) & Prior Authorization 8.2 Superbills, Charge Capture & Encounter Form Management 8.3 Coding Fundamentals for EHR: ICD-10-CM, CPT & HCPCS Level II 8.4 Claim Submission (EDI 837), Remittance (EDI 835) & Revenue Cycle 8.5 Providing Estimated Patient Costs & Good Faith Estimates 8.6 Patient Statements, Payment Collection & Balance Reconciliation

10 Chapter 9: Regulatory Compliance, HIPAA & Security

9.1 HIPAA Privacy Rule & Protected Health Information (PHI) 9.2 Minimum Necessary Rule, Permitted Uses & Patient Rights 9.3 HIPAA Security Rule: Administrative, Physical & Technical Safeguards 9.4 HITECH Act, Breach Notification Rule & Business Associate Agreements (BAAs) 9.5 Information Blocking Rules, 21st Century Cures Act & Compliance Audits 9.6 Allocating & Verifying EHR Access Controls and Role-Based Privileges 9.7 Educating Staff, Identifying Non-Compliant Behavior & Escalation 9.8 Abbreviation Policies, Professional Standards & EHR Downtime Procedures

11 Chapter 10: Data Management, Reporting & Health IT Standards

10.1 Health IT Interoperability: HL7, FHIR & Health Information Exchanges (HIE) 10.2 Standardized & Ad Hoc Financial Reports 10.3 Standardized & Ad Hoc Clinical Reports 10.4 Verifying Report Accuracy & Avoiding Common Reporting Errors 10.5 Quality Reporting, MIPS, Promoting Interoperability & Clinical Dashboards 10.6 Data Abstraction, Quality Improvement Studies & EHR System Security Management

1.4 Parts of the EHR & Core Functions of the Electronic Record

Key Takeaways Explain This Topic AI

The EHR is organized into administrative, clinical, order, results, and financial modules that share one patient identity through the master patient index.

Discrete (structured) data can be searched, trended, and reported; narrative (unstructured) data cannot, which is why structured entry is preferred wherever a field exists.

The designated record set is the legal subset of information a patient may inspect and request to amend, and it is narrower than everything stored in the system.

The legal health record is the organization's official output for disclosure and litigation, defined by policy rather than by the software.

Core EHR purposes are continuity of care, streamlined care delivery, safety through decision support, and data availability for reporting.

Last updated: August 2026

Two Core/Foundational Knowledge statements in the CEHRS test plan cover the record itself: CK6 (parts of the EHR, such as demographic information, clinical records, the medication administration record, diagnoses, laboratory reports, orders, and billing information) and CK10 (the general functions and purpose of the EHR, such as continuity of care and streamlined care). Almost every task statement in Domains 1 and 2 assumes you can name the module you are working in.

The Standard Modules

Module Contents Who Primarily Works Here

Registration / demographics Legal name, DOB, sex, address, contacts, language, guarantor, coverage Registration and front office

Scheduling / practice management Provider matrix, appointment types, resources, waitlist Scheduling staff

Problem list Active, inactive, and resolved conditions coded in SNOMED CT/ICD-10-CM Providers, with staff reconciliation

Medication list and MAR Home medications, active prescriptions, and the medication administration record Providers, nurses, pharmacy

  • Allergy module Allergen, category, reaction, severity, or an explicit NKDA entry Intake staff and clinicians
  • Clinical notes H&P, progress notes, consults, operative reports, discharge summary Providers

Flowsheets Vital signs, intake/output, assessments recorded as discrete values over time Clinical staff, interfaced devices

  • Orders (CPOE) Medication, laboratory, imaging, consult, and nursing orders Authorized clinicians
  • Results Laboratory values, imaging reports, pathology, cardiology tracings Interfaced ancillary systems
  • Immunizations Vaccine, lot, manufacturer, site, route, VIS date Clinical staff, IIS interface
  • Document imaging Scanned consents, outside records, ID and insurance cards HIM and front office
  • Charge capture / billing Superbill, codes, modifiers, claims, remittance, patient balance Billing staff
  • Patient portal Patient-facing view, messaging, scheduling, payment Patients, with staff support
  • Reporting / analytics Standard and ad hoc financial and clinical reports, dashboards Management, quality, HIM

The master patient index described in Section 2.2 is what makes these modules a single record rather than a dozen databases. Every module keys to one medical record number.

Discrete Data Versus Narrative Data

Discrete (structured) data is captured in a defined field with a defined value set: a blood pressure of 138/84 in a vitals flowsheet, a problem coded to SNOMED CT, an allergen selected from RxNorm. Discrete data can be trended on a graph, evaluated by clinical decision support, pulled into a quality measure, and exported to a registry.

Narrative (unstructured) data is free text: a paragraph in the history of present illness, a scanned handwritten form, a dictated operative report. It is rich for human readers but invisible to a rules engine unless natural language processing extracts it.

This distinction explains a rule that appears throughout the exam: when a structured field exists, use it . Typing "allergic to penicillin - rash" into a progress note does not populate the allergy module, so no drug-allergy alert will fire when penicillin is ordered. Section 10.3 shows the reporting consequence — a measure that counts a structured field will not see data buried in narrative text.

The Designated Record Set and the Legal Health Record

Two definitions are constantly confused, and both are testable.

The designated record set (DRS) is a HIPAA concept (45 CFR 164.501). It is the group of records a covered entity maintains that is used to make decisions about individuals — the medical and billing records maintained by or for a provider, and enrollment, payment, claims adjudication, and case management records for a health plan. The DRS defines what a patient has a right to inspect, copy, and request to amend . Psychotherapy notes and information compiled for legal proceedings are excluded.

The legal health record (LHR) is an organizational definition. It is the subset of documentation the organization designates as its official business record — the output it will produce in response to a subpoena or a request for the record. Because EHRs store far more than the LHR (audit logs, drafts, alert histories, interface messages), each organization must publish an LHR definition specifying which document types are released.

  • Designated Record Set Legal Health Record
  • Defined by HIPAA regulation Organizational policy
  • Purpose Patient access and amendment rights Disclosure and litigation response
  • Includes billing records Yes Usually, per policy
  • Includes audit logs No Generally no, but discoverable separately
  • What the EHR Is For

NHA frames the purpose of the EHR in terms a specialist can act on:

Continuity of care — one longitudinal record follows the patient across encounters, departments, and organizations, so the next clinician sees what the last one documented.

Streamlined care delivery — orders route electronically to the pharmacy, laboratory, and imaging without paper handoffs, shortening turnaround time.

Safety — decision support screens every order against allergies, interactions, and dose limits at the moment of entry.

Data availability — discrete data feeds quality measurement, population health, public health reporting, and revenue integrity.

Every one of those purposes fails the same way: if data is entered in the wrong chart, in the wrong field, or not at all. That is why Domain 1 opens with verifying patient identifiers before anything is documented.