<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Agate IT Services Blog</title>
    <link>https://www.agateit.org/agate-it-services-blog</link>
    <description />
    <language>en-us</language>
    <pubDate>Tue, 16 Jun 2026 16:59:06 GMT</pubDate>
    <dc:date>2026-06-16T16:59:06Z</dc:date>
    <dc:language>en-us</dc:language>
    <item>
      <title>Why Personal Email and HIPAA Do Not Mix</title>
      <link>https://www.agateit.org/agate-it-services-blog/choosing-hipaa-compliant-email-providers-for-secure-healthcare-communication</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.agateit.org/agate-it-services-blog/choosing-hipaa-compliant-email-providers-for-secure-healthcare-communication" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.agateit.org/hubfs/Protect-patient-trust-email-security.png" alt="Why Personal Email and HIPAA Do Not Mix" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p style="color: #87909e; background-color: #001129;"&gt;&lt;span style="font-weight: normal; font-size: 24px; color: #ffffff;"&gt;Why Personal Email Is a Compliance Risk in Healthcare&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;In healthcare, email is not just a convenience tool. It is often where appointment details, referral notes, billing questions, lab updates, and patient instructions get exchanged. That is why HIPAA matters here: the Security Rule requires covered entities and business associates to put reasonable and appropriate administrative, physical, and technical safeguards in place to protect ePHI, and it requires an accurate and thorough risk analysis of potential threats and vulnerabilities.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;A personal email account may be easy to use, but it is usually a weak fit for healthcare workflows. HIPAA’s safeguards include access control, audit controls, integrity, authentication, and transmission security, which are all much easier to manage in a controlled business environment than in a personal inbox tied to one employee’s private device, recovery settings, and personal habits. For a busy front desk, nurse, or practice manager, that can mean missed messages, unclear accountability, and no clean audit trail when something needs to be traced later.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;HIPAA also does not treat email as forbidden, but it does require reasonable safeguards. HHS says providers may use email with patients, including unencrypted email in some situations, but they should take precautions such as checking addresses carefully and limiting the amount or type of information disclosed. That is the key difference: HIPAA allows communication, but it expects it to be handled thoughtfully and securely. A personal inbox makes that harder because work messages get mixed with personal mail, and the organization loses control over how patient information is stored, accessed, and reviewed.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;This is where the BAA becomes important. HHS states that the HIPAA Rules generally require covered entities and business associates to enter into contracts with their business associates to ensure PHI is appropriately safeguarded. In other words, if a vendor is handling PHI on your behalf, there needs to be a formal business associate agreement in place. That is part of why secure, organization-owned email infrastructure is so important: it gives you the technology, policies, and contractual protections needed to support compliance.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;Protecting patient privacy in every email is not optional—it is a legal requirement that demands the right technology partner and security infrastructure. For healthcare providers, this is not about being overly cautious. It is about protecting patient trust, reducing avoidable risk, and making sure your team has a secure, auditable, professional way to communicate every day.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;If your practice is still relying on personal email for patient-related communication, now is the time to move to a secure, organization-controlled system. Agate IT Services helps healthcare providers put the right email safeguards, policies, and security infrastructure in place so your team can communicate confidently and compliantly.&lt;/span&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p style="color: #87909e; background-color: #001129;"&gt;&lt;span style="font-weight: normal; font-size: 24px; color: #ffffff;"&gt;Why Personal Email Is a Compliance Risk in Healthcare&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;In healthcare, email is not just a convenience tool. It is often where appointment details, referral notes, billing questions, lab updates, and patient instructions get exchanged. That is why HIPAA matters here: the Security Rule requires covered entities and business associates to put reasonable and appropriate administrative, physical, and technical safeguards in place to protect ePHI, and it requires an accurate and thorough risk analysis of potential threats and vulnerabilities.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;A personal email account may be easy to use, but it is usually a weak fit for healthcare workflows. HIPAA’s safeguards include access control, audit controls, integrity, authentication, and transmission security, which are all much easier to manage in a controlled business environment than in a personal inbox tied to one employee’s private device, recovery settings, and personal habits. For a busy front desk, nurse, or practice manager, that can mean missed messages, unclear accountability, and no clean audit trail when something needs to be traced later.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;HIPAA also does not treat email as forbidden, but it does require reasonable safeguards. HHS says providers may use email with patients, including unencrypted email in some situations, but they should take precautions such as checking addresses carefully and limiting the amount or type of information disclosed. That is the key difference: HIPAA allows communication, but it expects it to be handled thoughtfully and securely. A personal inbox makes that harder because work messages get mixed with personal mail, and the organization loses control over how patient information is stored, accessed, and reviewed.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;This is where the BAA becomes important. HHS states that the HIPAA Rules generally require covered entities and business associates to enter into contracts with their business associates to ensure PHI is appropriately safeguarded. In other words, if a vendor is handling PHI on your behalf, there needs to be a formal business associate agreement in place. That is part of why secure, organization-owned email infrastructure is so important: it gives you the technology, policies, and contractual protections needed to support compliance.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;Protecting patient privacy in every email is not optional—it is a legal requirement that demands the right technology partner and security infrastructure. For healthcare providers, this is not about being overly cautious. It is about protecting patient trust, reducing avoidable risk, and making sure your team has a secure, auditable, professional way to communicate every day.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #ffffff;"&gt;If your practice is still relying on personal email for patient-related communication, now is the time to move to a secure, organization-controlled system. Agate IT Services helps healthcare providers put the right email safeguards, policies, and security infrastructure in place so your team can communicate confidently and compliantly.&lt;/span&gt;&lt;/p&gt;  
&lt;img src="https://track-na2.hubspot.com/__ptq.gif?a=245669520&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.agateit.org%2Fagate-it-services-blog%2Fchoosing-hipaa-compliant-email-providers-for-secure-healthcare-communication&amp;amp;bu=https%253A%252F%252Fwww.agateit.org%252Fagate-it-services-blog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Tue, 16 Jun 2026 00:07:26 GMT</pubDate>
      <author>agonzalez@agateit.org (Abram Gonzalez)</author>
      <guid>https://www.agateit.org/agate-it-services-blog/choosing-hipaa-compliant-email-providers-for-secure-healthcare-communication</guid>
      <dc:date>2026-06-16T00:07:26Z</dc:date>
    </item>
  </channel>
</rss>
