<?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/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question How to Encrypt PHI or Limit Access to Records Containing it in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/how-to-encrypt-phi-or-limit-access-to-records-containing-it/m-p/3079396#M1100</link>
    <description>&lt;P&gt;My organization is looking into how SNOW can handle PHI/PII. We would like to identify records that contain PHI and if possible, encrypt/blur the data that is PHI out.&lt;/P&gt;&lt;P&gt;I believe we can handle the first part pretty easily by creating a new field.&lt;/P&gt;&lt;P&gt;We are stuck on how to implement this second part. The data could reside anywhere is the problem. We cannot just create a new field called PHI and then encrypt it if needed. We would want to have the record identified, and if possible, have SNOW read the record and maybe with pattern recognition or something similar, block out some content? (I feel like this last ask is not possible, especially without isolating the PHI data)&lt;/P&gt;</description>
    <pubDate>Mon, 21 Oct 2024 19:15:55 GMT</pubDate>
    <dc:creator>chrisinhoff</dc:creator>
    <dc:date>2024-10-21T19:15:55Z</dc:date>
    <item>
      <title>How to Encrypt PHI or Limit Access to Records Containing it</title>
      <link>https://www.servicenow.com/community/community-central-forum/how-to-encrypt-phi-or-limit-access-to-records-containing-it/m-p/3079396#M1100</link>
      <description>&lt;P&gt;My organization is looking into how SNOW can handle PHI/PII. We would like to identify records that contain PHI and if possible, encrypt/blur the data that is PHI out.&lt;/P&gt;&lt;P&gt;I believe we can handle the first part pretty easily by creating a new field.&lt;/P&gt;&lt;P&gt;We are stuck on how to implement this second part. The data could reside anywhere is the problem. We cannot just create a new field called PHI and then encrypt it if needed. We would want to have the record identified, and if possible, have SNOW read the record and maybe with pattern recognition or something similar, block out some content? (I feel like this last ask is not possible, especially without isolating the PHI data)&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 19:15:55 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/how-to-encrypt-phi-or-limit-access-to-records-containing-it/m-p/3079396#M1100</guid>
      <dc:creator>chrisinhoff</dc:creator>
      <dc:date>2024-10-21T19:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to Encrypt PHI or Limit Access to Records Containing it</title>
      <link>https://www.servicenow.com/community/community-central-forum/how-to-encrypt-phi-or-limit-access-to-records-containing-it/m-p/3079401#M1102</link>
      <description>&lt;P&gt;This post can be closed.&lt;/P&gt;&lt;P&gt;I forgot I had a different one open named:&amp;nbsp;&lt;SPAN&gt;Identify PHI or PII in SNOW and Take Action&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Oct 2024 19:25:48 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/how-to-encrypt-phi-or-limit-access-to-records-containing-it/m-p/3079401#M1102</guid>
      <dc:creator>chrisinhoff</dc:creator>
      <dc:date>2024-10-21T19:25:48Z</dc:date>
    </item>
  </channel>
</rss>

