Re: [Gnumed-devel] GNUmed web interface - technologies

[Jim Busser]

On 2010-07-11, at 5:36 AM, Dave Cramer wrote:

> If you are indeed serious about keeping both clients web, and thick
> then I would think that both of them would have to access the data
> through some middleware in order to maintain data integrity and keep
> one codebase.

Sounds like the ability of *both* clients to access the *same* middleware would 
be useful. Is there an alternative?

It seems to me there are two modes of interacting with patients' records... one 
patient at a time, and multiple patients at a time.

There are also two modes of using clients... any one praxis (medical practice) 
could resolve to standardize on a single client, or it could decide to allow 
more than one client (web, thick client). 

Supposing a praxis decided it wanted to allow both, would it be possible to 
contextualize the postgres GNUmed databases, with respect to permitting or 
disallowing concurrent record access?

It seems to me that, provided a user is only allowed to work on one patient's 
(or one user's) records at a time then the danger of two users using two 
different clients that did not know about each other could be managed through 
controls that postgres might offer on the tables and records themselves? Sorry 
if it is either magical thinking, or theoretically workable but unsupported... 
<g>

-- Jim