Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E76B672E0 for ; Tue, 1 Nov 2011 13:49:07 +0000 (UTC) Received: (qmail 56878 invoked by uid 500); 1 Nov 2011 13:49:06 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 56843 invoked by uid 500); 1 Nov 2011 13:49:06 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 56834 invoked by uid 99); 1 Nov 2011 13:49:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 13:49:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.52] (HELO mail-vw0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2011 13:49:00 +0000 Received: by vws10 with SMTP id 10so2287648vws.11 for ; Tue, 01 Nov 2011 06:48:38 -0700 (PDT) Received: by 10.52.69.104 with SMTP id d8mr5249786vdu.77.1320155318100; Tue, 01 Nov 2011 06:48:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.116.7 with HTTP; Tue, 1 Nov 2011 06:48:17 -0700 (PDT) In-Reply-To: <4EAF56B3.6080601@thewordnerd.info> References: <4EAF56B3.6080601@thewordnerd.info> From: Cory Zue Date: Tue, 1 Nov 2011 09:48:17 -0400 Message-ID: Subject: Re: Health care software utilizing CouchDB To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Oct 31, 2011 at 10:17 PM, Nolan Darilek wr= ote: > What encrypted volume are you using? Ecryptfs. [1] We've had pretty solid performance with it, although haven't yet reached the scale where we might have to worry more about performance. The major downside is that you need to manually mount the drive in the case of a reboot which can be problematic if people with the credentials aren't around. This is only a small piece of the HIPAA puzzle, but does provide the "encrypted at rest" and "protection if the server walks away" bits. [1] https://help.ubuntu.com/11.04/serverguide/C/ecryptfs.html > > I'm actually not using CouchDB (I had an app based on MongoDB) but the No= SQL > solutions seem to be lagging behind in things like database encryption. I > wanted to go with the encrypted volume approach, but finding one that is = up > to HIPAA/HITECH spec was confusing for someone running a small business > targeting a niche market of mostly solo practitioners. > > > On 10/31/2011 02:43 PM, Cory Zue wrote: >> >> My organization supports many healthcare applications on CouchDB >> including multiple that are HIPAA compliant. We store our entire >> database on an encrypted volume and setup ssh-tunnels for encrypted >> replication. We have found that the schemalessness of couch is a big >> win when dealing with health protocols and systems. >> >> Cory >> -- >> Cory L. Zue >> Dimagi, Inc >> http://www.dimagi.com/ >> >> >> >> On Mon, Oct 31, 2011 at 3:06 PM, Alexander Shorin >> =A0wrote: >>> >>> On Mon, Oct 31, 2011 at 7:38 PM, Manor Lev-tov >>> =A0wrote: >>>> >>>> Hello, >>>> I was curious if anyone here has experience or knows of any company th= at >>>> has written an electronic medical record system or any other health ca= re >>>> related software using CouchDB as the data store? >>>> Thanks, >>>> Manor >>>> >>> Working on frond-end for Laboratory Information System based on >>> CouchDB. Front-end includes: application server, reports, data >>> collaboration, point of integration with other companies etc. It >>> perfectly fits to these tasks and could even more (e.g. mobile client >>> that allows you, as patient, to access your analysis result >>> everywhere). No success story yet, but all works fine for now(: >>> >>> -- >>> ,,,^..^,,, >>> > >