Skip to main content

I am working towards implementing shield encryption in our environments.  During the implementation process we have discovered several limitations with shield.  The biggest problem is that Shield doesn't encrypt numbers. We have a group doing care management.  Because shield doesn't encrypt numbers.  i am unable to encrypt any of the PHI they are collecting around Height. Weight, BMI and Lab values.  This is a huge security issue for our data security department.  we have already secured the data through org wide defaults, profiles, sharing rules and field level security but our executives want the data encrypted.  I am curious how other health care systems have addressed this issue around encrypting PHI.  thanks.

5 条评论
  1. 2018年10月4日 18:39
    We turned on encryption on a number of fields and hid who the records belonged to. The approach was fine. however there was a couple problems we ran into. There was a cloud process builder flow that we used for patient matching from a web to case form. Cloud process builder cannot work with encrypted data, so we are in the process of reworking that. We didn't know about that process and it wasn't on our test plan. Also a number of our reports broke due to a known limitation with Shield. So it was expected. The reports that used "starts with" or "contains", couldn't find any matches. Shield cant match partial data because it encrypts the entire field.