Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of gs@redcometlabs.com designates
 74.125.82.170 as permitted sender)
From: Garren Smith <garren@apache.org>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_F181C7EE-FD57-4677-9C24-E27DC358C659"
Subject: Fwd: healthcare projects running on couched?
Date: Tue, 25 Mar 2014 12:13:45 +0200
References: 
 <CAMc++1Uw8Z5unYJi539huLck-Q0WtQm1RhCuqZSztw9xiv57TA@mail.gmail.com>
To: marketing@couchdb.apache.org
Message-Id: <0ECB9E75-4AD5-4388-A361-ECAE1B3129AD@apache.org>
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))

--Apple-Mail=_F181C7EE-FD57-4677-9C24-E27DC358C659
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This is something that could be added to Couchdb weekly. Taken from the =
user@couchdb.apache.org

Begin forwarded message:

> From: Albin Stig=C3=B6 <albin.stigo@gmail.com>
> Subject: Re: healthcare projects running on couched?
> Date: 25 March 2014 at 11:54:33 AM SAST
> To: "user@couchdb.apache.org" <user@couchdb.apache.org>
> Reply-To: user@couchdb.apache.org
>=20
> Thanks for all the replies, it seems couchdb is already used in many
> medical systems around the globe. I took the liberty to provide a
> summery.
>=20
> The reasons I think couchdb is an interesting fit are;
> from my developer point of view:
>=20
> 1. Relative ease of delpoyment, clean implementation, proven platform
> (erlang). Relativley simple configuration.
> 2. Easy synchronization let's you work without a single point of
> failure, spotty connections, in p2p configuration. Easy backups.
> 3. Ready for mobile (did I mention spotty connectinos in the hospital =
basement?)
> 4. Attachments (there are always scans, photos etc)
> 5. Changes streams provide easy notifications when something changed,
> new test results arrived etc. This is very convenient.
>=20
> Regarding conflict management, this is both and issue and a none
> issue. It has happened to me some times as a physician that I have
> experienced "conflicts" and that my changes were just overwritten by
> someone else (gasp). If there's a conflict both version always need to
> be saved. In medical records you never really delete or change
> anything, you make additions. Like a ledger.
>=20
> =46rom my physician point of view (and what I know my colleagues =
think):
>=20
> 1. It should just work, right away. When I push the button it should
> be saved. Physicians are used to eventual consistency because we
> dictate a lot and it was previously transcribed my secretaries so it
> didn't appear right away anyway. But we could be sure it would. No
> locks. NO LOCKS!!!
>=20
> 2. Maximize uptime (by using a p2p you have a redundant system)
>=20
> 3. When new data arrives the screen should updated automatically.
>=20
> --Albin
>=20
> Links provided in earlier replies:
>=20
> http://www.4medica.com
> Are aware of couchdb but we don't know to what extent they use it.
>=20
> http://www.commcarehq.org/home/
> Their backend is couchdb.
>=20
> http://www.mobiusmed.com/
> Use it as a backing store for at least two products.
>=20
> http://neurofoundation.in
> Use it as their backend for their EMR system.
>=20
> https://iilab.org
> Not sure how they use couchdb.
>=20
> On Tue, Mar 25, 2014 at 12:47 AM, Jens Alfke <jens@couchbase.com> =
wrote:
>>=20
>> On Mar 24, 2014, at 10:10 AM, =D7=90=D7=95=D7=A8=D7=9F =D7=A9=D7=A0=D7=99=
 <orenshani7@gmail.com> wrote:
>>=20
>>> How abiut couchDB's conflict resoloution mechanism vs SQL DB's using =
locks.
>>> Do you think that is a major concideration?
>>=20
>> You can=E2=80=99t use locking in a widely-distributed system, or one =
client forgetting to release a lock would block everyone else (either =
forever or until the lease runs out.) It also makes offline updates =
impossible.
>>=20
>> I=E2=80=99ve heard of relational-db-based systems that do =
replication, but they don=E2=80=99t attempt to propagate locks. Instead =
they do conflict resolution during replication the same way CouchDB =
does.
>>=20
>> =E2=80=94Jens


--Apple-Mail=_F181C7EE-FD57-4677-9C24-E27DC358C659--