Re: [SPAM] Re: Key encryption and relational integrity

Il 01/04/2019 20:48, Rory Campbell-Lange ha scritto: On 01/04/19, Moreno Andreo (moreno.and...@evolu-s.it) wrote: ... I'm not forced to use pseudonimysation if there's the risk to get things worse in a system. I've got to speak about these"two opposing forces at work" to a privacy expert (maybe

Re: Key encryption and relational integrity

On 01/04/19, Moreno Andreo (moreno.and...@evolu-s.it) wrote: ... > I'm not forced to use pseudonimysation if there's the risk to get > things worse in a system. I've got to speak about these"two opposing > forces at work" to a privacy expert (maybe choosing another one, as > Peter suggested :-) ) a

Re: Key encryption and relational integrity

Il 29/03/2019 20:23, Adrian Klaver ha scritto: On 3/29/19 9:01 AM, Moreno Andreo wrote: And I tried to find a solution, and since I did not like that much what I found (and it seems that neither you do :-) ), I came here hoping that someone would share his experience to shed some light on the

Re: Key encryption and relational integrity

On 2019-03-29 17:05:41 +0100, Moreno Andreo wrote: > Il 28/03/2019 23:50, Peter J. Holzer ha scritto: > > On 2019-03-28 15:29:50 +0100, Moreno Andreo wrote: > > > here I'm trying to find a way so nobody can, without the use of the > > > application, match a patient with their clinical records (i.e.

Re: Key encryption and relational integrity

On 3/29/19 9:01 AM, Moreno Andreo wrote: And I tried to find a solution, and since I did not like that much what I found (and it seems that neither you do :-) ), I came here hoping that someone would share his experience to shed some light on the topic. From what you have posted the biggest i

Re: Key encryption and relational integrity

On 2019-03-29 17:01:07 +0100, Moreno Andreo wrote: > Il 28/03/2019 23:29, Peter J. Holzer ha scritto: > > On 2019-03-28 18:36:40 +0100, Moreno Andreo wrote: > > > it's just "separation" (that was OK with the last privacy act, but not > > > with GDPR > > I doubt that this is correct. The GDPR doesn'

Re: Key encryption and relational integrity

Il 28/03/2019 23:50, Peter J. Holzer ha scritto: On 2019-03-28 15:29:50 +0100, Moreno Andreo wrote: here I'm trying to find a way so nobody can, without the use of the application, match a patient with their clinical records (i.e. someone breaking into the server -- data breach) I think it is v

Re: Key encryption and relational integrity

Il 28/03/2019 23:29, Peter J. Holzer ha scritto: On 2019-03-28 18:36:40 +0100, Moreno Andreo wrote: Il 26/03/2019 18:08, Adrian Klaver ha scritto: To me it would seem something like: Table medications id    user_id    med 1    sgkighs98    Medication 2    sghighs98    Ear check Table us

Re: Key encryption and relational integrity

What Andrea Moreno's client seems to think is required by GDPR is clearly bogus -- it would render illegal any and all DICOM images existing today, because they contain programmatically easily processable personally identifying data right inside the clinical data. Karsten Hilbert -- GPG 40BE 5B0E

Re: Key encryption and relational integrity

On 2019-03-28 15:29:50 +0100, Moreno Andreo wrote: > here I'm trying to find a way so nobody can, without the use of the > application, match a patient with their clinical records (i.e. someone > breaking into the server -- data breach) I think it is very optimistic to assume that an intruder woul

Re: Key encryption and relational integrity

On 2019-03-28 18:36:40 +0100, Moreno Andreo wrote: > Il 26/03/2019 18:08, Adrian Klaver ha scritto: > > To me it would seem something like: > > > > Table medications > > id    user_id    med > > 1    sgkighs98    Medication > > 2    sghighs98    Ear check > > > > > > > > Table users > > id 

Re: Key encryption and relational integrity

On 3/28/19 10:36 AM, Moreno Andreo wrote: Il 26/03/2019 18:08, Adrian Klaver ha scritto: On 3/26/19 9:08 AM, Moreno Andreo wrote: Il 26/03/2019 15:24, Adrian Klaver ha scritto: On 3/26/19 7:19 AM, Moreno Andreo wrote: Hello folks :-) Is there any workaround to implement key encryption withou

Aw: Re: Key encryption and relational integrity

> I believe you when you say "they say that ..." but I truly doubt that > GDPR intended to make data processing fully impractical. > > (I work in the medical field) In Germany, that is, which usually takes things to the extreme, for better or worse. Karsten

Aw: Re: Key encryption and relational integrity

> Yes, but to be GDPR compliant I _have_ to remove that link. As you > reported in an earlier email, they say that you can't link patient and > medication if not with an external resource. In this case we are linking > them without an external resource I REALLY doubt that. I believe you when

Re: Key encryption and relational integrity

Il 28/03/2019 15:45, Adrian Klaver ha scritto: On 3/28/19 7:29 AM, Moreno Andreo wrote: Il 27/03/2019 07:42, Tony Shelver ha scritto: Not in Europe, but have worked a bit with medical records systems in the USA, including sharing across providers. The only other way to do it would be to store

Re: Key encryption and relational integrity

Il 26/03/2019 18:08, Adrian Klaver ha scritto: On 3/26/19 9:08 AM, Moreno Andreo wrote: Il 26/03/2019 15:24, Adrian Klaver ha scritto: On 3/26/19 7:19 AM, Moreno Andreo wrote: Hello folks :-) Is there any workaround to implement key encryption without breaking relational integrity? This is

Re: Key encryption and relational integrity

On 3/28/19 7:29 AM, Moreno Andreo wrote: Il 27/03/2019 07:42, Tony Shelver ha scritto: Not in Europe, but have worked a bit with medical records systems in the USA, including sharing across providers. The only other way to do it would be to store the encrypted key value in both user.id

Re: Key encryption and relational integrity

Il 27/03/2019 07:42, Tony Shelver ha scritto: Not in Europe, but have worked a bit with medical records systems in the USA, including sharing across providers. The primary key of the u

Re: Key encryption and relational integrity

Not in Europe, but have worked a bit with medical records systems in the USA, including sharing across providers. The primary key of the user is _should_ be system generated, and this is meaningless from a user identity standpoint. If you encrypt user name and other significant personal data on t

Re: Key encryption and relational integrity

On 3/26/19 9:08 AM, Moreno Andreo wrote: Il 26/03/2019 15:24, Adrian Klaver ha scritto: On 3/26/19 7:19 AM, Moreno Andreo wrote: Hello folks :-) Is there any workaround to implement key encryption without breaking relational integrity? This is going to need more information. OK, I'll try

Re: Key encryption and relational integrity

On Tue, Mar 26, 2019 at 9:39 AM Kevin Brannen wrote: > -Original Message- > From: Moreno Andreo > Sent: Tuesday, March 26, 2019 11:09 AM > To: Adrian Klaver ; PostgreSQL mailing lists < > pgsql-gene...@postgresql.org> > Subject: Re: Key encryption and relat

RE: Key encryption and relational integrity

-Original Message- From: Moreno Andreo Sent: Tuesday, March 26, 2019 11:09 AM To: Adrian Klaver ; PostgreSQL mailing lists Subject: Re: Key encryption and relational integrity In a master-detail relation, I need to encrypt one of master table PK or detail table FK, in order to achieve

Re: Key encryption and relational integrity

Il 26/03/2019 15:24, Adrian Klaver ha scritto: On 3/26/19 7:19 AM, Moreno Andreo wrote: Hello folks :-) Is there any workaround to implement key encryption without breaking relational integrity? This is going to need more information. OK, I'll try to be as clearer as I can For starters 'ke

Re: Key encryption and relational integrity

On 3/26/19 7:19 AM, Moreno Andreo wrote: Hello folks :-) Is there any workaround to implement key encryption without breaking relational integrity? This is going to need more information. For starters 'key' has separate meanings for encryption and RI. I could make some guesses about what you

Key encryption and relational integrity

Hello folks :-) Is there any workaround to implement key encryption without breaking relational integrity? Thanks Moreno.-