HIPAA Considerations for Thoracic Surgery Referrals: What Providers Need to Know

Product Pricing
Ready to get started? Book a demo with our team
Talk to an expert

HIPAA Considerations for Thoracic Surgery Referrals: What Providers Need to Know

Kevin Henry

HIPAA

December 09, 2025

8 minutes read
Share this article
HIPAA Considerations for Thoracic Surgery Referrals: What Providers Need to Know

HIPAA Privacy Rule Overview

What counts as PHI in a thoracic surgery referral

Protected Health Information (PHI) in this context includes demographics, clinical notes, imaging and DICOM files (CT chest, PET-CT, echocardiograms), pathology and molecular reports, pulmonary function tests, medications and allergies, comorbidities, and preoperative risk assessments. When you transmit this PHI electronically (ePHI), both the HIPAA Privacy Rule and Security Rule apply.

Provider-to-Provider Disclosures for treatment

Under the Privacy Rule, you may share PHI with another covered entity for treatment purposes without patient authorization. Referrals, consultations, care coordination, and second opinions are all “treatment.” Provider-to-provider disclosures that support surgical planning—such as sending CT images and pathology slides to a thoracic surgeon—are permitted when reasonably necessary for that care.

When authorization is required or additional limits apply

Authorization is generally required for uses outside treatment, payment, and health care operations (for example, marketing). Some categories carry extra protections: psychotherapy notes require specific authorization; substance use disorder records may be restricted by 42 CFR Part 2; and many states impose added consent rules for HIV, genetic testing, reproductive health, or certain mental health records. Build your referral workflows to flag these exceptions before transmission.

Minimum Necessary Standard for Referrals

How the rule applies in practice

The minimum necessary standard does not apply to disclosures to or requests by a health care provider for treatment. Still, applying a “right-sized” approach improves privacy and reduces risk. Share what the receiving thoracic surgeon and perioperative team need to evaluate and manage the case, not an indiscriminate export of the full chart.

Essential elements to include for thoracic surgery

  • Reason for referral, working diagnosis, and clinical question (e.g., suspected lung carcinoma; staging and resection candidacy).
  • Key diagnostics: radiology reports and original imaging, pathology (biopsy/cytology, margins, molecular markers if relevant), cardiopulmonary testing (PFTs with FEV1/DLCO, ABG if available), ECG/echo, pertinent labs, and relevant prior operative reports.
  • Current medications, allergies, comorbidities (e.g., COPD, CAD), functional status, smoking history, and any prehab/optimization already completed.
  • Care coordination essentials: contact details for referring team, patient preferences (language/accommodation), and insurance/authorization notes necessary to schedule.

Avoid common over-disclosures

  • Resist sending full longitudinal records or unrelated sensitive notes.
  • Segregate data that triggers added protections (e.g., psychotherapy notes, SUD information) unless explicitly needed for treatment and permitted by law.
  • Use referral templates and role-based workflows so staff do not attach unnecessary documents by default.

Secure Communication Methods

Preferred, HIPAA-aligned channels

  • EHR-to-EHR secure messaging (e.g., Direct messaging) or exchange via a Health Information Exchange with strong identity proofing.
  • Standards-based APIs (e.g., FHIR) for structured data and imaging links when supported by both systems.
  • Encrypted email using S/MIME or equivalent with enforced TLS 1.2+ and verified recipient identity.
  • Secure file transfer (SFTP) or a vetted, access-controlled cloud repository with expiring links and download restrictions.
  • Enterprise secure messaging platforms with audit logging and Access Controls, covered by Business Associate Agreements (BAAs).

Encryption Standards and identity assurance

Use modern Encryption Standards in transit (TLS 1.2/1.3) and at rest (AES-256) implemented via FIPS 140-2/140-3 validated modules when feasible. Enforce multi-factor authentication for external access, verify destination addresses before sending, and apply sender-side protections (message recall not reliable; prefer time-limited, view-only links). For imaging, prefer secure exchange networks or gateways that preserve integrity checks.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

What to avoid or tightly control

  • Do not use SMS, consumer chat apps, or personal email for PHI.
  • If you must use legacy fax, confirm numbers, use cover sheets that minimize PHI, and control physical access to machines. Prefer e-fax services under a BAA with encryption and audit trails.
  • Disable auto-forwarding to unsecured destinations and prohibit downloading PHI to unmanaged devices.

Documentation Practices for Referrals

What to capture every time

  • Referral order with clinical question, urgency, and receiving provider information.
  • Contents of the referral packet (documents, imaging manifests) and confirmation of successful transmission.
  • Any special restrictions or patient preferences identified (e.g., language needs, data-sensitivity flags).
  • Internal handoffs and tasks (scheduling attempts, pre-op optimization steps) to demonstrate continuity.

Audit Logging and retention

Maintain audit logging for who accessed, compiled, sent, or viewed referral-related PHI. Retain HIPAA-required documentation—policies, procedures, risk analyses, training records, BAAs, and authorizations—typically for six years from date of creation or last effective date. Although an accounting of disclosures is generally not required for treatment, robust logs help with incident response and compliance reviews.

Use standardized tools

Adopt structured referral templates tailored to thoracic surgery. Configure EHR smart-sets to pull only necessary data, automatically include image links instead of bulky files where appropriate, and stamp each transmission with sender, recipient, date/time, and method.

Administrative and Technical Safeguards

Administrative safeguards you should operationalize

  • Risk Analysis and risk management plan specific to referral workflows, including imaging exchange and third-party platforms.
  • Workforce training on minimum-necessary concepts in practice, recognizing sensitive data types, and secure sending etiquette.
  • Policies for identity verification, misdirected transmissions, incident reporting, and sanctions.
  • Vendor due diligence and Business Associate oversight, including periodic security attestations.
  • Contingency planning for system downtime so urgent surgical referrals can proceed securely.

Technical safeguards to enforce

  • Access Controls: unique user IDs, role-based permissions, and multi-factor authentication for remote or external access.
  • Audit controls: immutable logs, regular log review, and alerts for anomalous export or download activity.
  • Integrity controls: hashing and checksums for files, secure imaging gateways, and version control on referral packets.
  • Transmission security: enforced TLS, message-level encryption where feasible, and data loss prevention on outbound channels.
  • Automatic logoff, endpoint encryption, remote wipe, and prohibition of PHI on unmanaged devices.

Business Associate Agreements

Who is—and isn’t—a Business Associate in referrals

Vendors that create, receive, maintain, or transmit PHI for you are Business Associates: EHR and imaging cloud hosts, e-fax or secure-messaging providers, HIEs, cloud storage or file-transfer services, and referral management platforms. The receiving thoracic surgery practice is a covered entity, not your BA; provider-to-provider disclosures for treatment do not require a BAA between the two practices.

BAA essentials to require

  • Permitted uses/disclosures, prohibition on re-identification or secondary use without your direction.
  • Security obligations aligned to your Encryption Standards, Access Controls, and Audit Logging requirements.
  • Breach notification timeframes, cooperation duties, and incident evidence preservation.
  • Subcontractor “flow-down” clauses and right to receive security attestations or summaries of Risk Analysis.
  • Return or secure destruction of PHI upon termination, with transition support for continued patient care.

Complying with State Privacy Laws

HIPAA is the floor—states may go further

HIPAA sets baseline protections. If a state law is more protective of patient privacy, you must follow the state requirement. Many states impose stricter consent, redisclosure, or segmentation rules for categories like HIV status, genetic testing, reproductive health, certain mental health records, and minors’ consented services.

Cross-state referrals and operational readiness

For cross-border referrals, validate the sending site’s and receiving site’s state rules. Build a practical state-law matrix, data-segmentation flags in the EHR (e.g., “do not redisclose without consent”), and supplemental consent forms where required. Train staff to recognize and route exceptions for quick legal or privacy review so surgery is not delayed.

Conclusion

For thoracic surgery referrals, HIPAA permits provider-to-provider disclosures for treatment, but you should still right-size the data, transmit it securely, log activity, and govern vendors through strong Business Associate Agreements. Pair these steps with a living state-law playbook, modern encryption, and disciplined access controls to protect patients while moving them swiftly to the operative care they need.

FAQs

What PHI can be shared without patient authorization during referrals?

You may share PHI necessary for treatment—referrals, consultations, and care coordination—without patient authorization. Send what the thoracic surgeon needs (imaging, pathology, cardiopulmonary testing, meds, allergies, comorbidities). Be cautious with specially protected information (e.g., psychotherapy notes, SUD records, and state-restricted categories) and obtain required consents when applicable.

How should providers securely transmit referral information?

Prefer EHR-to-EHR secure messaging, HIE exchange, or standards-based APIs. If using email, enforce TLS 1.2+ with message-level encryption (e.g., S/MIME), verify recipient identity, and avoid unmanaged devices. Secure file transfer or vetted cloud repositories with expiring links, Access Controls, and Audit Logging are effective. Avoid SMS and consumer apps; use e-fax only under a BAA with safeguards.

What documentation is required for HIPAA compliance in referrals?

Document the referral order, the exact materials sent, the transmission method, confirmation of receipt, and any special restrictions. Maintain Audit Logging, policies, procedures, Risk Analysis, training records, and BAAs—typically retained for six years. An accounting of disclosures is generally not required for treatment, but comprehensive logs support compliance and incident response.

Are additional state privacy laws applicable to thoracic surgery referrals?

Yes. HIPAA is a federal baseline; more protective state laws control. Many states require added consent or impose redisclosure limits for HIV results, genetic data, reproductive health information, certain mental health records, and minors’ services. For cross-state referrals, check both jurisdictions and adjust referral packets, consents, and data segmentation accordingly.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles