Study guide
9.7 Educating Staff, Identifying Non-Compliant Behavior & Escalation
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
9.7 Educating Staff, Identifying Non-Compliant Behavior & Escalation
Key Takeaways Explain This Topic AI
Security awareness training must be periodic and reinforced, and its implementation specifications include security reminders, malicious software protection, log-in monitoring, and password management.
The most common non-compliant behaviors are credential sharing, unlocked unattended workstations, unsecured PHI in public areas, and hallway or social media disclosures.
Phishing is the leading initial vector for health care breaches, and staff must verify unexpected requests through a known channel rather than replying.
Observed non-compliance is addressed at the moment when it is safe to do so, then reported through the compliance channel; serious incidents go straight to the privacy or security officer.
Non-retaliation protections and anonymous reporting exist so staff will report without fear, and failing to report an observed violation is itself a policy breach.
Last updated: August 2026
Test plan tasks 4.C and 4.D put the specialist on both sides of the compliance conversation: educating colleagues on best practices and assisting with enforcement, and identifying non-compliant behaviors that threaten the security of electronic information. Knowledge statements 4.K4 (best practices), 4.K7 (potential security breaches), 4.K8 (escalation procedures), 4.K10 (safeguard procedures), 4.K11 (adult learning), and 4.K17 (consequences of noncompliance) supply the content.
The Security Awareness Program
The Security Rule's Security Awareness and Training standard requires a security awareness and training program for all workforce members, including management. Its four implementation specifications are all addressable , which — as Section 9.3 explains — means they must be implemented where reasonable and appropriate, not that they are optional:
- Specification What It Looks Like in Practice
- Security reminders Periodic updates, posters, newsletters, login banners, and huddle topics
- Protection from malicious software Training on ransomware, malicious attachments, and reporting
- Log-in monitoring Training staff to notice and report failed login attempts and unfamiliar session activity
- Password management Rules for creating, protecting, and changing passwords, and for never sharing them
Training is delivered at onboarding, at least annually, and after an incident or policy change. Applying the adult-learning principles in Section 4.5 matters here more than anywhere: a slide deck about "the HIPAA Security Rule" changes no behavior, while "here is the phishing email that hit our organization last month, and here is what to do" does.
What Non-Compliant Behavior Looks Like
Test plan task 4.D names the pattern with two examples — sharing passwords and an unlocked room — and the full list is short enough to memorize:
Behavior Why It Is a Threat
Sharing credentials or letting someone work under your login Destroys attribution; every action is charged to the credential owner
- Unlocked, unattended workstation Anyone passing can read or alter records under that user's identity
- Unlocked room housing workstations, servers, or charts Physical access defeats technical controls
- Screens visible from public areas Incidental disclosure; fixed with privacy filters and repositioning
- PHI left at a printer, fax, or desk Uncontrolled disclosure to anyone who walks by
- Discussing patients in elevators, hallways, or cafeterias Verbal disclosure to unauthorized listeners
Posting about patients on social media Disclosure that is public, permanent, and frequently identifiable even without a name
- Emailing PHI to a personal account or copying to unencrypted media Moves data outside protected systems
- Snooping in co-worker, family, or VIP records Access without a permitted purpose (Section 6.4)
- Propping badge-controlled doors or tailgating Bypasses facility access controls
- Ignoring or clicking through security alerts Defeats technical safeguards
Using unapproved applications to store or share PHI Creates unmanaged, unencrypted PHI outside the organization's control
Phishing and social engineering
Phishing remains the leading initial vector for health care breaches. Teach the indicators — urgency, an unexpected attachment, a mismatched sender domain, a link whose displayed text differs from its destination, a request for credentials or a payment change — and teach one behavior above all: verify through a known channel . Call the person at the number in the directory, not the number in the email. Never reply to the message to confirm it is legitimate.
The same rule applies to phone and in-person social engineering: someone claiming to be from IT and asking for a password, a "physician's office" requesting records without an authorization, or a visitor in scrubs asking to be let through a badge door.
Educating Colleagues Day to Day
The specialist's most effective teaching is not a class. It is:
Modeling. Lock the workstation every time. Retrieve prints immediately. Ask "what is the purpose of this access?" out loud.
Just-in-time coaching. "Let me show you the secure message option so you do not have to email that" corrects the behavior and supplies the alternative.
Making the safe path easy. Most non-compliance is a workaround for friction. If people email PHI because the secure channel takes six clicks, fix the six clicks.
Explaining the why. Adults comply with rules they understand. "Shared logins mean the audit log cannot tell who did what, so you would be answerable for someone else's entry" lands better than "policy prohibits it."
Escalation
Knowledge statement 4.K8 covers escalation procedures. The path:
Address it in the moment when it is safe and appropriate — closing an unattended session, retrieving an abandoned printout, quietly redirecting a hallway conversation.
Report it through the defined channel: supervisor, privacy officer, security officer, or the compliance hotline. Most organizations offer an anonymous route.
Escalate immediately, bypassing the normal chain, for serious events — a suspected breach, ransomware or other malware, credential compromise, deliberate snooping, or any incident with potential patient harm.
Document what was observed, when, where, who was involved, and what was reported.
Do not investigate on your own. Do not pull audit logs, interview the person, or gather evidence unless that is your assigned role. Improvised investigation contaminates the real one.
Non-retaliation protections exist precisely so staff will report, and failing to report an observed violation is itself a policy breach in most organizations.
Consequences
Knowledge statement 4.K17 covers consequences of noncompliance. They run on three tracks simultaneously: the workforce sanction policy (counseling through termination, applied consistently — a Required element of the Security Management Process), organizational liability (OCR civil monetary penalties, corrective action plans, state enforcement, breach notification costs, and reputational damage, as covered in Sections 9.4 and 9.5), and individual liability (criminal prosecution under HIPAA for knowing misuse of PHI, plus loss of licensure or certification). Individual criminal exposure is the part staff most often do not know, and it is worth saying plainly during training.