HIPAA Compliance Pros Featured Articles

Free Webinar Today: A Practical Guide to a HIPAA Security Risk Assessment

Security Risk Assessment for HIPAA ComplianceA missing or inadequate HIPAA Security Risk Assessment (SRA) can leave a major gap in your HIPAA compliance program. It is also one of the issues most frequently identified in OCR enforcement actions.

Yet many practices remain uncertain about what an SRA should cover, how often it should be updated, and what distinguishes a genuine risk analysis from a simple checklist.

Join Bradley King, Senior Compliance Consultant, for a practical 30-minute webinar that will explain the role of the SRA and help you identify your next steps. Whether you are completing an SRA for the first time or reviewing your existing documentation, you will leave with a clearer understanding of what your organization needs to do.

You will discover:

Get The FREE
HIPAA Compliance Checklist

Immediate Delivery of Checklist Link To Your Email Address

Please Enter Correct Email Address

Your Privacy Respected

HIPAA Journal Privacy Policy

  • What is-and-is-not a HIPAA Security Risk Assessment
  • Where the SRA fits within your wider HIPAA compliance program
  • When your SRA should be reviewed and updated
  • Why SRA deficiencies are a recurring focus of OCR enforcement
  • The practical steps your organization can take to strengthen its approach

The HIPAA Security Risk Assessment, or SRA, is arguably the most foundational document in your practice when it comes to HIPAA compliance. As your organization gets ready for the next year, compliance may not be at the top of your to-do list. However, the holidays present a perfect opportunity to finally catch up on administrative tasks, especially your annual SRA.

If you can’t attend the live event, then register anyway, and we will send you the recording.


Date of Live Webinar: October 28, 2026

Time: 12:00 – 12:30 PM ET, 11:00 – 11:30 AM CT, 10:00 – 10:30 AM MT, 09:00 – 09:30 AM  PT

Duration: 00:30 Hour

Can’t join live? Register and we’ll send you the recording. 


 

This webinar is presented by Abyde in partnership with The HIPAA Journal.

Speaker: Bradley King, Senior Compliance Consultant

Bradley King has many years of experience in HIPAA and OSHA compliance consulting. He has spoken at national conferences and delivered continuing education webinars on HIPAA and OSHA compliance best practices, and has worked directly with thousands of practices, from solo, owner-operator practices to multi-location, multistate healthcare organizations, on building and maintaining compliance programs.

Abyde is a leader in the compliance software industry, streamlining HIPAA & OSHA requirements for thousands of practices across the United States.

 


Date of Live Webinar: October 28, 2026

Time: 12-12:30 PM ET, 11-11:30 AM CT, 10-10:30 AM MT, 09-09:30 AM  PT

Duration: 00:30 Hour

Can’t join live? Register and we’ll send you the recording. 

The post Free Webinar Today: A Practical Guide to a HIPAA Security Risk Assessment appeared first on The HIPAA Journal.

Is Your Website Sharing Patient Data With Trackers? How to do a Web Scan

Website Privacy RiskWebsite privacy risks

Website privacy risks can remain hidden across a health provider’s digital estate until a patient, regulator, or plaintiff discovers them.

A pixel installed for one advertising campaign, a script introduced through a plugin, or an analytics tool added by an outside agency can continue operating long after anyone remembers approving it, creating a website tracking privacy risk.

Privacy and compliance teams may not know every tool that is operating, what information it collects, or where that information is sent. For a health provider managing multiple hospitals, locations, subdomains, service-line websites, and campaign pages, one forgotten or incorrectly configured script can affect hundreds or thousands of webpages.

Healthcare websites are constantly being updated

A large healthcare organization may operate a main corporate website alongside hospital websites, provider directories, service-line pages, campaign landing pages, patient portal login pages, recruitment sites, blogs, mobile applications, and websites inherited through acquisitions. Different marketing teams, agencies, developers, and technology vendors may all be able to introduce new code.

Your privacy respected – Read our privacy policy

Your privacy respected – Read our privacy policy

@media only screen and (min-width: 961px) { .inpage_mobile { display: none; } .inpage_banner_12838 { background-color: #D1D0CB; margin-bottom: 18px; max-width: 510px; display: block; margin: 0 auto 18px; padding: 20px 0; } .inpage_banner_12838 a img { margin-bottom: 10px; } .inpage_banner_12838 p.terms_title { text-align: center; font-family: sans-serif; font-size: 12px; font-weight: 400; color: #33342F; padding-bottom: 0; line-height: 19px; } .inpage_banner_12838 p.terms_title a { color: #33342F; text-decoration: underline; } .inpage_banner_12838 p.terms_title a:hover { text-decoration: none; } } @media only screen and (max-width: 960px) { .inpage_desktop { display: none; } .inpage_banner_12838 { background-color: #D1D0CB; margin-bottom: 18px; max-width: 300px; display: block; margin: 0 auto 18px; padding: 20px 0; } .inpage_banner_12838 a img { margin-bottom: 10px; } .inpage_banner_12838 p.terms_title { text-align: center; font-family: sans-serif; font-size: 12px; font-weight: 400; color: #33342F; padding-bottom: 0; line-height: 19px; } .inpage_banner_12838 p.terms_title a { color: #33342F; text-decoration: underline; } .inpage_banner_12838 p.terms_title a:hover { text-decoration: none; } }

The result is a constantly changing web environment in which compliance, privacy, and information security teams may not have a complete picture of every third-party technology operating across the organization.

Is your privacy policy accurate?

Research suggests that third-party data transfers are present on the overwhelming majority of hospital websites.

A 2024 study of a nationally representative sample of 100 nonfederal acute care hospitals found that 96% of their websites transferred user information to at least one third party. The websites communicated with a median of nine third-party domains, and 86% had at least one third-party cookie.

Only 71 of the 100 hospital websites had a publicly accessible website privacy policy. Among those 71 policies, just 40 specifically identified third-party companies or services receiving user information.

The findings highlight an important distinction: Having a privacy policy does not guarantee that an organization has full visibility into its data practices or that the policy accurately describes current activity. A privacy policy that was accurate when it was written can become outdated as new technologies, vendors, campaigns, and websites are introduced.

@media only screen and (min-width: 961px) { .inpage_mobile { display: none; } .inpage_banner_58549 { margin-bottom: 18px; } .inpage_banner_58549 a { max-width: 510px; display: block; margin: 0 auto; } } @media only screen and (max-width: 960px) { .inpage_desktop { display: none; } .inpage_banner_58549 { margin-bottom: 18px; } .inpage_banner_58549 a { max-width: 300px; display: block; margin: 0 auto; } }

Why larger healthcare organizations face greater challenges

Health systems and multi-location healthcare groups can have hundreds of people involved in their digital operations. Marketing may select an analytics platform, an agency may deploy advertising pixels, a service line may introduce a new scheduling application, and a recently acquired practice may continue using its existing website technology.

Each decision may appear reasonable in isolation. Collectively, however, they can create a complex and poorly documented network of data connections.

Common problems include:

  • No central inventory of websites, subdomains, microsites, and landing pages
  • Different privacy and consent practices across affiliated organizations
  • Inconsistent use of tag management systems
  • Technologies added without privacy, security, or legal review
  • Inherited tracking code following mergers and acquisitions
  • Expired campaigns with active tags
  • Privacy policies that do not reflect actual website behavior
  • Vendors introducing additional subprocesses or technologies
  • Unclear responsibility for approving and monitoring website tools
  • Script ownership that isn’t well documented, so when a team member moves on, their scripts keep running without anyone else realizing it

A review of the main health system homepage will not necessarily reveal what is happening on a specialty clinic website, an appointment page, a recruitment portal, or a location-specific landing page. That’s why it is important for any web scan to go beyond the homepage.

When does website tracking become a HIPAA issue?

For Covered Entities and Business Associates, the HIPAA Rules apply when information collected through tracking technologies or disclosed to tracking technology vendors includes PHI.

Pages that deserve particularly careful examination include:

  • Authenticated patient portals
  • Patient portal login and registration pages
  • Online appointment scheduling pages
  • Symptom checkers
  • Provider search tools
  • Pages that collect an email address or other identifying information
  • Forms through which an individual describes a condition or reason for seeking care
  • Pages containing treatment, prescription, billing, or medical record information

The Department of Health and Human Services’ Office for Civil Rights states that a privacy policy, website notice, or terms of use document does not, by itself, make a disclosure of PHI permissible. OCR also states that an ordinary cookie consent banner is not a HIPAA-compliant authorization.

If a tracking vendor creates, receives, maintains, or transmits PHI on behalf of a regulated entity for a covered function, the vendor may qualify as a Business Associate. The organization must determine whether the disclosure is permitted and whether an appropriate Business Associate Agreement is required.

The solution for website privacy risks

Automated website privacy monitoring tools can help close the visibility gap. Tools can scan public-facing pages for third-party scripts and cookies, identify external technologies operating across websites and subdomains, and flag activity that may require further investigation.

They can also compare observed website behavior with statements in the organization’s privacy policy and monitor for changes over time.

These tools do not replace legal analysis or determine whether a disclosure violates HIPAA, but they can help privacy, compliance, marketing, and technology teams find potential risks sooner, prioritize their response, and demonstrate ongoing oversight.

Not every visit to a healthcare webpage involves PHI

The legal position is more nuanced than some early reporting on tracking technologies suggested.

In June 2024, a federal court vacated part of OCR’s tracking technology guidance in American Hospital Association v. Becerra. The court rejected the position that an IP address combined with a visit to a public, unauthenticated webpage about a particular condition or healthcare provider was sufficient, by itself, to trigger HIPAA obligations.

OCR’s current guidance acknowledges that a visit to a public healthcare webpage does not automatically constitute a disclosure of individually identifiable health information simply because a tracking technology connects the visit with an IP address.

For example, someone may visit an oncology page because they are conducting academic research, helping a relative, reading the news, or looking for employment. The webpage visit alone does not establish that the visitor has cancer or is seeking cancer treatment.

However, the court decision did not create a general exemption for healthcare websites. HIPAA may still apply when identifiable information is connected with an individual’s health, care, or payment for care. Information entered into an appointment form, registration page, symptom checker, or authenticated portal presents a substantially different risk from an anonymous visit to a general information page.

Regulatory and litigation risks extend beyond HIPAA

In July 2023, OCR and the Federal Trade Commission (FTC) sent joint warning letters to approximately 130 hospital systems and telehealth providers. The letters drew attention to technologies such as Meta Pixel and Google Analytics and warned that they could disclose sensitive health information to third parties.

The FTC can take action when an organization makes misleading privacy promises or uses and discloses consumer health information in ways that are unfair or deceptive. State consumer protection, privacy, and wiretapping laws may also apply.

This means an organization should not conclude that a tracking activity is low risk merely because the information being shared with third parties does not meet the HIPAA definition of PHI.

The enforcement record illustrates the wider exposure:

  • The FTC alleged that GoodRx disclosed health information to Facebook, Google, and other companies contrary to its privacy promises. GoodRx agreed to a $1.5 million civil penalty and restrictions on sharing health information for advertising.
  • BetterHelp agreed to pay $7.8 million to resolve FTC allegations involving the disclosure of email addresses, IP addresses, and health questionnaire information for advertising purposes.
  • In a separate class action, patients alleged that tracking pixels on Advocate Aurora Health’s websites, app, and patient portal disclosed their information to Meta and Google. They brought claims under federal and state privacy laws, including the federal Wiretap Act. The court approved a $12.225 million settlement, without ruling on the underlying allegations. The case shows how website tracking can lead to privacy litigation outside a HIPAA enforcement action.

Private litigation has created additional risk. Plaintiffs have pursued claims against healthcare organizations under federal and state wiretapping, privacy, consumer protection, and contract laws. Not every claim has succeeded, and the outcomes frequently depend on the information involved, the wording of the relevant statute, the consent process, and how the technology operated.

The absence of a successful HIPAA enforcement action does not therefore mean that an organization has no legal exposure.

A cookie banner is not a complete solution

Website Privacy RiskConsent management is important, particularly under state privacy laws, but a cookie banner cannot compensate for a lack of technical visibility.

An organization needs to establish:

  • Which technologies operate before a visitor can make a choice about whether to opt out
  • Whether scripts are actually prevented from loading if a visitor rejects them
  • Whether the consent mechanism covers every relevant website and subdomain
  • Whether a visitor’s preferences are passed to connected systems
  • Whether the policy accurately identifies the information collected and its recipients
  • Whether HIPAA authorization or another legal permission is required

A banner may tell visitors that cookies are used, but it does not answer whether a particular script is receiving an appointment event, a patient identifier, or information entered into a form.

The evolution of the patient journey

Healthcare websites have become an important part of the patient journey. Visitors use them to research symptoms, compare services, find doctors, schedule appointments, complete forms, access patient portals, watch educational videos, use chat tools, and locate nearby facilities.

These functions often depend on third-party technologies, including:

  • Analytics platforms
  • Advertising and conversion pixels
  • Tag management systems
  • Appointment scheduling applications
  • Embedded forms
  • Chat and chatbot services
  • Session replay technologies
  • Heatmaps
  • Maps and location services
  • Embedded videos
  • A/B testing and personalization tools
  • Social media integrations

Many of these tools provide genuine operational or marketing value. The risk arises when an organization does not fully understand what information a technology collects, when that information is collected, where it is sent, or what the receiving company is permitted to do with it.

A technology added to measure conversions on one campaign page may later be deployed across an entire website. A script introduced by a plugin may communicate with additional companies that were not part of the original approval. A tool removed from the visible marketing stack may continue operating through a tag manager or legacy page template.

On a large and frequently updated web estate, these changes can be difficult to identify through manual reviews alone.

Visibility is the foundation of control

Healthcare organizations do not have to abandon digital analytics, advertising, or website personalization in order to comply with HIPAA and other federal and state privacy regulations. These technologies can provide meaningful value by helping patients find services and allowing organizations to understand whether their communications are effective.

The essential requirement is visibility.

A healthcare organization cannot assess a technology it does not know is present, enforce a policy it cannot test, or control a disclosure it cannot see. Understanding what operates across the organization’s websites, where information is sent, and whether those activities match the organization’s privacy policy is necessary for compliant use of many digital marketing capabilities.

@media only screen and (min-width: 961px) { .inpage_mobile { display: none; } .inpage_banner_58549 { margin-bottom: 18px; } .inpage_banner_58549 a { max-width: 510px; display: block; margin: 0 auto; } } @media only screen and (max-width: 960px) { .inpage_desktop { display: none; } .inpage_banner_58549 { margin-bottom: 18px; } .inpage_banner_58549 a { max-width: 300px; display: block; margin: 0 auto; } }

What information can website technologies collect?

The information disclosed to a third party will depend on the technology, its configuration, and the page on which it operates. It can potentially include:

  • The URL and title of the page visited
  • The visitor’s IP address and approximate location
  • Device and browser information
  • Cookie identifier
  • Advertising identifiers
  • Buttons, links, or menu options selected
  • Search terms
  • Form field activity
  • Appointment-related events
  • Information used to identify or recognize returning visitors

The presence of a third-party script does not automatically mean that Protected Health Information has been disclosed or that a law has been violated. The organization must examine the information involved, the context in which it was collected, the purpose of the disclosure, the recipient, and the applicable legal authority.

However, it is impossible to perform that assessment if the organization does not know the technology is present.

10-point website privacy governance checklist

A health system should treat its public website environment as part of its wider privacy and security program. A practical governance process should include:

Identify the complete web estate. Document websites, subdomains, microsites, mobile applications, landing pages, portals, and inherited digital properties.

Inventory third-party technologies. Identify scripts, cookies, pixels, plugins, embedded content, and the external domains with which each property communicates.

Prioritize higher-risk pages. Focus on scheduling, registration, provider search, symptom, portal, payment, and form pages.

Document purpose and ownership. Every technology should have a defined business purpose and an internal owner.

Assess the information involved. Determine what data is collected, when it is transmitted, and whether it may include PHI or other sensitive information.

Review vendors and agreements. Establish whether the recipient is a business associate, whether a BAA is required, and whether the proposed use is permitted.

Compare behavior with published promises. Website activity, consent choices, privacy policies, and notices should be consistent.

Control future changes. New tracking technologies should require appropriate marketing, privacy, security, and legal approval before deployment.

Monitor continuously. Repeat scans and investigate material changes instead of relying solely on periodic manual audits.

Document decisions and remediation. Maintain evidence of findings, approvals, risk assessments, corrective actions, and ongoing oversight.

A one-time website audit provides only a snapshot

Large healthcare websites change continually. New pages are published, campaigns launch, vendors update code, plugins change, and acquired organizations introduce additional domains.

A review conducted today may not reflect the organization’s website in practice next month.

Effective oversight therefore requires both an initial inventory and continuous monitoring. The organization should be able to quickly identify and act on:

  • New scripts and external domains
  • Changes to cookies and tracking behavior
  • New pages handling potentially sensitive information
  • Differences between locations, brands, or subdomains
  • Technologies that reappear after they were removed
  • Changes that create conflicts with the privacy policy
  • Unapproved additions made through a tag manager or plugin

Historical records can also help an organization determine when a technology first appeared, which pages were affected, and whether remedial or breach assessment work may be necessary.

Protecting your organization with a web scanner

A website scanner can monitor your sites automatically and keep a historical record of changes. Depending on the tool, it may also offer accessibility checks against WCAG 2.2 AA, Content Security Policy (CSP) and privacy policy scanning, AI-generated summaries, exportable reports, and other features.

@media only screen and (min-width: 961px) { .inpage_mobile { display: none; } .inpage_banner_58549 { margin-bottom: 18px; } .inpage_banner_58549 a { max-width: 510px; display: block; margin: 0 auto; } } @media only screen and (max-width: 960px) { .inpage_desktop { display: none; } .inpage_banner_58549 { margin-bottom: 18px; } .inpage_banner_58549 a { max-width: 300px; display: block; margin: 0 auto; } }

              *Web Scan report provided using Ours Privacy technology

Ours Privacy CDP Dashboard

The post Is Your Website Sharing Patient Data With Trackers? How to do a Web Scan appeared first on The HIPAA Journal.

Free Webinar Today: Is AI Putting Your Practice at Risk?

HIPAA Rusk analysis security risk assessment toolAI tools are already in your practice. The question is whether you know about them and whether they are HIPAA-compliant. 

Most practices are using AI in some form already, whether it’s an EHR feature, a note-taking assistant, or a chatbot tool; however, they may not be aware of all locations where AI is used.

Join Ryan Boudreau, Senior VP of Operations at the healthcare compliance company Abyde, as he walks you through where AI may already be hiding in your practice, the HIPAA and privacy risks it creates, and a simple framework for using AI while remaining HIPAA-compliant. 


Live Webinar: Wednesday, Sept 30 

12:00-1:00 PM ET | 11:00 AM-12:00 PM CT | 10:00-11:00 AM MT | 9:00-10:00 AM PT

 A recording will be made available to anyone who registers but is unable to attend the live event.

Get The FREE
HIPAA Compliance Checklist

Immediate Delivery of Checklist Link To Your Email Address

Please Enter Correct Email Address

Your Privacy Respected

HIPAA Journal Privacy Policy


Attendees will discover:

  • Where AI is most likely already in use in your practice, including the places you didn’t realize
  • A simple, four-question framework for evaluating any AI tool before you use it
  • The fine print that matters in vendor agreements to help avoid risk
  • Real-world cautionary tales on improper AI use in healthcare

Speaker: 

Ryan BoudreauRyan Boudreau – Senior Vice President of Operations 

Ryan Boudreau is the Senior Vice President of Operations at Abyde, where he leads a team of HIPAA and OSHA compliance experts. A cybersecurity and risk management veteran with nearly 15 years of experience, his team that has successfully navigated hundreds of OCR investigations on behalf of their clients.

Abyde is a leader in the compliance software industry, streamlining HIPAA & OSHA requirements for thousands of practices across the United States.


Live Webinar

Wednesday, Sept 30  | 12:00–1:00 PM ET | 11:00 AM–12:00 PM CT | 10:00–11:00 AM MT | 9:00–10:00 AM PT

 A recording will be made available to anyone who registers but is unable to attend the live event.

The post Free Webinar Today: Is AI Putting Your Practice at Risk? appeared first on The HIPAA Journal.

Free Webinar Tomorrow: Inside 250 HIPAA Investigations – What You Need to Know

Free Webinar Inside a HIPAA InvestigationLearn exactly what happens during a HIPAA investigation. Understand where organizations fail so you can avoid government fines and drawn-out investigations.

Based on real experience from over 250 actual OCR investigations.

When it comes to HIPAA investigations, many organizations lean on the hope that they will never be implicated. But, with the rise of ransomware breaches and patient complaints, your organization is much more likely to end up in the crosshairs of the Office for Civil Rights (OCR) than you might expect. 

While you can’t always prevent breaches from occurring, you can control your preparedness for everything that follows when it comes to your HIPAA compliance posture. 

Get The FREE
HIPAA Compliance Checklist

Immediate Delivery of Checklist Link To Your Email Address

Please Enter Correct Email Address

Your Privacy Respected

HIPAA Journal Privacy Policy

Join Jake Dewberry, Chief Legal Officer, and Ryan Boudreau, Senior Vice President of Operations from Abyde, as they walk through the details of what an investigation actually looks like and where organizations fail based on their experience in over 250 OCR investigations. They will be sharing real (redacted) examples from past investigations, detailing what the OCR asks for, how to respond safely, and how others failed so you can avoid government fines and drawn-out investigations. 


Live Webinar: Wednesday, August 19

12-1 pm ET | 11-12 am CT | 10-11 am MT | 9-10 am PT

 

 A recording will be made available to anyone who registers but is unable to attend the live event.


Attendees will discover:

  • What triggers an investigation
  • What to do immediately after receiving an investigation letter
  • A breakdown of what the OCR is really asking for, including the most commonly missed requirement
  • Best practices for building your response
  • The possible results of an investigation
  • Real examples of investigation letters

Speakers: 

Jake Dewberry Jake Dewberry – Chief Legal Officer

Jake Dewberry serves as the Chief Legal Officer at Abyde. With over 14 years of experience in the healthcare industry, Jake has worked closely with hospitals and small to mid-sized practices across the country, helping them navigate the evolving world of healthcare technology and regulatory requirements. Jake is also a licensed attorney based in Florida. At Abyde, he wears multiple legal hats — from advising clients during breach responses and audits, to managing the company’s day-to-day legal operations, and staying on top of federal and state regulatory changes impacting HIPAA and OSHA compliance.

 

Ryan BoudreauRyan Boudreau – Senior Vice President of Operations 

Ryan Boudreau is the Senior Vice President of Operations at Abyde, where he leads a team of HIPAA and OSHA compliance experts. A cybersecurity and risk management veteran with nearly 15 years of experience, his team has successfully navigated hundreds of OCR investigations on behalf of their clients.

Abyde is a leader in the compliance software industry, streamlining HIPAA & OSHA requirements for thousands of practices across the United States.


Live Webinar: Wednesday, August 19

12-1 pm ET | 11-12 am CT | 10-11 am MT | 9-10 am PT

 A recording will be made available to anyone who registers but is unable to attend the live event.

The post Free Webinar Tomorrow: Inside 250 HIPAA Investigations – What You Need to Know appeared first on The HIPAA Journal.

Free Webinar TODAY: HIPAA Email Security 101: PHI, Encryption, and What’s Required

According to the Paubox 2026 Healthcare Email Security Report, in 2025, 170 email-related data breaches were reported to the HHS’ Office for Civil Rights (OCR). While healthcare organizations are getting better at preventing email-related data breaches, an analysis of email security configurations found that in 2025, 41% of healthcare organizations fell into the high-risk category, an increase from the previous year.

On top of those large healthcare data breaches are the thousands of smaller breaches that affect fewer than 500 individuals, a large percentage of which are due to poor email security configurations and errors by healthcare employees. Each email incident erodes trust, can be costly to resolve, and potentially puts the organization at risk of a HIPAA penalty, yet email compliance failures are easily avoided.

On May 21, 2026, the leading healthcare email security company, Paubox, is hosting a webinar to explain HIPAA email security 101. The webinar consists of a practical session covering the fundamentals of HIPAA-compliant email, what constitutes PHI, and how to identify the indicators of PHI, as well as the key email security requirements that HIPAA-regulated entities must have in place to ensure that sensitive information is protected and patient privacy is assured. Attendees will also learn about the common compliance errors made by organizations and healthcare employees when communicating via email, and how to avoid them.

Webinar attendees will learn how encryption works and why it is vital for HIPAA compliance

Reserve your spot today to learn how HIPAA applies to email and the requirements for HIPAA-compliant email communications. 

Why Attend?

  • Attendees will learn the fundamentals of HIPAA-compliant email communications, what constitutes PHI, and the common compliance mistakes made by healthcare organizations, and how to avoid them. This webinar is eligible for 1 self-reported CPE. Attendees will receive a certificate of attendance that may be used as supporting documentation when submitting credits to applicable certifying bodies.

WEBINAR DETAILS

HIPAA Email Security 101: PHI, Encryption, and What’s Required

Wednesday, May 20, 2026

10 a.m. PT | 11 a.m. MT | 12 p.m. CT | 1 p.m. ET | 6 a.m. BST

Register for the Webinar


 

Speaker: Dawn Halpin, HIPAA Evangelist, Paubox

Dawn Halpin, Paubox

Dawn Halpin, a graduate of Marquette University and the University of Wisconsin-Milwaukee, is a HIPAA Evangelist at the email security firm Paubox. Paubox is a leader in HIPAA-compliant email security for the healthcare industry and is trusted by more than 8,000 organizations, including Cost Plus Drugs, Rippling, and Covenant Health.

 

 

The post Free Webinar TODAY: HIPAA Email Security 101: PHI, Encryption, and What’s Required appeared first on The HIPAA Journal.