Study guide
6.5 Securely Transmitting & Exchanging Patient Data
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
6.5 Securely Transmitting & Exchanging Patient Data
Key Takeaways Explain This Topic AI
Data transmitted to pharmacies, providers, agencies, and researchers must move over an encrypted, authenticated channel appropriate to the content and the recipient.
Direct secure messaging, TLS-protected interfaces, SFTP, and portal messaging are compliant channels; standard email, SMS, and consumer fax are not without added protection.
Purpose and audience determine what may be sent: treatment exchange is broad, while research, marketing, and most third-party disclosures require authorization or de-identification.
The minimum necessary standard applies to every non-treatment transmission, and highly protected categories require separate handling.
Every external transmission is verified for correct recipient address, correct patient, correct content scope, and successful delivery, and is logged.
Last updated: August 2026
Test plan task 2.B — "securely transmit and exchange patient data internally and externally (e.g., to pharmacies, other health care providers, other agencies) for research, analytics, and continuity of care" — is supported by four knowledge statements: requirements and procedures for secure transmission (2.K5), types of data that must be encrypted and the encryption processes (2.K6), types of information that can be shared externally (2.K7), and considerations such as purpose and audience (2.K8). Section 10.1 covers the interoperability standards themselves; this section covers doing it safely.
Choosing a Channel
- Channel Appropriate For Protection
- HL7 v2 / FHIR interface Orders, results, ADT between systems Private network or VPN; TLS for network transport
Direct secure messaging Referrals, summaries, transitions of care Encrypted, identity-verified push using trusted certificates
Query-based HIE exchange Retrieving records for unplanned care Participant agreements, authentication, audit
FHIR API with OAuth 2.0 Patient-authorized apps, third-party tools Token-based authorization scoped to the request
NCPDP SCRIPT Prescriptions to pharmacies Encrypted network, digital signature for EPCS
X12 EDI over a clearinghouse Eligibility, claims, remittance, authorization Encrypted transport with trading partner agreements
SFTP / managed file transfer Bulk extracts, registry submissions, research datasets Encrypted in transit and at rest, key-based authentication
Patient portal secure messaging Communicating with patients Authenticated session, encrypted transport and storage
Channels that are not acceptable for PHI without additional protection: standard unencrypted email, standard SMS text, consumer cloud file sharing without a business associate agreement, personal messaging applications, and unencrypted removable media.
Two frequently misunderstood cases:
Fax. Traditional fax remains widely used and is permitted, but it is high-risk because a misdialed number sends PHI to a stranger. Confirm the number, use pre-programmed entries, include a confidentiality cover sheet, and confirm receipt for sensitive material. Digital fax that terminates in an encrypted queue is preferable.
Appointment reminder texts. Permitted with documented patient consent and limited to minimum necessary logistics — date, time, location — with no clinical detail (Section 2.4).
What Must Be Encrypted
Knowledge statement 2.K6 asks which data must be encrypted and how. The practical standard used by health care organizations:
In transit — all ePHI leaving a device or crossing a network, using current TLS or an equivalent encrypted tunnel.
At rest — ePHI stored on servers, databases, backups, laptops, tablets, phones, and removable media, using a NIST-approved algorithm such as AES.
Under the HIPAA Security Rule as currently written, encryption is an addressable implementation specification: the organization must assess it, implement it where reasonable and appropriate, and document an equivalent alternative if it does not (Section 9.3). In practice, nearly every organization implements encryption, because encryption that meets HHS guidance also triggers the breach notification safe harbor described in Section 9.4 — encrypted data that is lost or stolen does not require notification. That single incentive is why "encrypt everything portable" is the operating rule regardless of the addressable designation.
Purpose and Audience Determine Content
Knowledge statements 2.K7 and 2.K8 make purpose the controlling variable.
Purpose Authorization Needed? Content Limit
Treatment (to another provider, pharmacy, or facility) No Minimum necessary does not apply to treatment disclosures
- Payment (to a payer or clearinghouse) No Minimum necessary applies
- Health care operations (quality, audit, credentialing) No Minimum necessary applies
- Public health reporting (required by law) No As specified by the reporting requirement
Research Yes, unless an IRB/privacy board waiver applies, a limited data set with a data use agreement is used, or the data is de-identified Strictly scoped
Analytics by a vendor No, if the vendor is a business associate under a BAA Minimum necessary; contract-limited
- Marketing or sale of PHI Yes, specific authorization required As authorized
- Any other third party Yes, valid HIPAA authorization (Section 3.3) Exactly what the authorization names
Categories requiring extra care regardless of channel: psychotherapy notes (standalone authorization), substance use disorder records under 42 CFR Part 2 (redisclosure prohibition must accompany the data), HIV and other state-protected conditions , and genetic information .
Verify Before You Send
Most real-world breaches in this area are addressing errors, not cryptographic failures. Before transmitting:
Right recipient. Verify the Direct address, fax number, or endpoint against a known record rather than a typed guess. Autocomplete selecting the wrong "Dr. Smith" is a leading cause of misdirected PHI.
Right patient. Confirm two identifiers on the outbound package.
Right scope. Send what the purpose or authorization covers and no more. "Entire chart" is rarely the minimum necessary outside treatment.
Right protection. Confirm the channel is the approved one for that content and recipient.
Confirm delivery. Check for the acknowledgment, transmission report, or interface ACK. An unacknowledged transmission is not a completed one.
Log it. Record what was sent, to whom, when, by whom, under what authority, and how it was verified. Non-exempt disclosures go into the accounting of disclosures (Section 3.3).
When a Transmission Goes Wrong
Misdirected PHI is handled as a potential breach: stop the workflow, notify the privacy officer immediately, attempt to retrieve or obtain attested destruction from the unintended recipient, document every step, and let the privacy officer run the four-factor risk assessment in Section 9.4. Mitigation evidence — a signed destruction attestation from a recipient who is itself a covered entity — directly affects whether the incident is reportable.