1.4 Parts of the EHR & Core Functions of the Electronic Record
Key Takeaways
- 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.
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.
A medical assistant types 'patient says she gets hives from amoxicillin' into the narrative HPI field but does not open the allergy module. What is the most significant consequence?
Which item is part of the designated record set that a patient has the right to inspect and request to amend?
What distinguishes the legal health record from the designated record set?