X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 731B9D1BB93 for ; Mon, 8 Mar 2004 11:09:16 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 64393-01 for ; Mon, 8 Mar 2004 07:09:16 -0400 (AST) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by svr1.postgresql.org (Postfix) with ESMTP id F1AAFD1B562 for ; Mon, 8 Mar 2004 07:09:12 -0400 (AST) Received: from host191-33.pool8248.interbusiness.it (82.48.33.191) by vsmtp3.tin.it (7.0.019) (authenticated as silvanadimartino) id 402CD18F00473B07 for pgsql-admin@postgresql.org; Mon, 8 Mar 2004 12:09:12 +0100 From: Silvana Di Martino To: pgsql-admin@postgresql.org Subject: HIPAA Date: Mon, 8 Mar 2004 12:07:23 +0000 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200403081024.06324.silvanadimartino@tin.it> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/120 X-Sequence-Number: 12689 It looks like that also USA-resident DBAdmins have to protect their data, at least when their data are related to someone else's personal health: http://www.cms.hhs.gov/hipaa/ http://www.hhs.gov/ocr/hipaa/ http://www.hipaa.org/ This seems to give to this "db encryption" issue the status of "global relevance" that would deserve a more systematic approach. I mean: no homegrown solutions - rather have the community to develop a specific, standard extension of PostgreSQL and put it into the distro. I wonder if it is the case to contact the PostrgreSQL developers and signal this (new and annoying) issue. Any comment? ----------------------------------------- Alessandro Bottoni and Silvana Di Martino alessandrobottoni@interfree.it silvanadimartino@tin.it