Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "J.O. Aho" Newsgroups: comp.lang.php Subject: Re: getting started with encryption Date: Sat, 11 Oct 2014 09:07:08 +0200 Lines: 24 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net R5MhouMzzOyDm25g4frnqQzc07QhJEzrTKEcNfVTN+DTkW0L0m Cancel-Lock: sha1:A+qbrVv1QGKxoq6DOvI6a0/eLNE= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 In-Reply-To: Xref: csiph.com comp.lang.php:14311 On 10/10/14 20:46, bill wrote: > It has been decided that encrypting patient notes would be a good idea. > I anticipated this when I wrote the original code and all patient note > writes go through a null (now) function and all notes to be read, likewise. Most systems with patient data use encrypted columns or encrypted fields where you use key management system to decide which database user has access to the data. MySQL do not support this, so you need to build in something, not just the encryption/decryption functionality, but also access right system or key management system which limits who can and can't access the data. If you want to do it on database level, then you need to look at PostgreSQL or going with some commercial database like Cache from InterSystems (maybe the worlds most used database for health-care systems). If your system will include card payments, then you will get deep into troubles with the new PCI DSS 3.0. -- //Aho