[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] gnumed

From: scaredycat
Subject: Re: [Gnumed-devel] gnumed
Date: Thu, 14 Oct 2004 09:30:04 +1000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

James Busser wrote:

Quoting scaredycat <address@hidden>:

The web client is barely usable now; it can do demographic ( basic , no multiaddresses, no relative linking) insert and edit, find ; allergy, medication, clinical narrative, health issue , clin episode , vaccination ,
printable summary page , and INSERT into the database - but no UPDATE  :(
No scripts, specialist address book, messaging, path and radiology requests, referral letter printing,
document management , search and display;  appointments...
but at least it's using gnumed


BTW can I assume that the same gnumed database can be accessed by either, or both, of web clients and python/wxwidgets clients at the same time?

Well, sort of . They should be able to run concurrently unless the python client maintains transaction locks over the whole session and same patient data is being opened, which it doesn't AFAIK , and neither does the web client. The web client inserts data only on submit : this can be transactional over all the items entered, but at the moment, it can fail one clin_item insert while allowing the others ( after successfully inserting a new episode +/- health issue ) if no clin_items are inserted , then the original committed transaction of episode insert is reversed by a delete/commit.
(although I think any new health issue stays in the record) .
The python client creates empty rows on object creation, and I think these objects update the database when triggered by a save command on a widget. On the other hand, some tables such as clin_medication are guarded by a lot of constraints, and objects in this case might be easier to just do table insert .

The web client can put data into the schema , with it's current constrains intact, and extract it out again, but the python client does it only for some records updated by the web client. It's either a bug , or a python client (not backend) enforced
validation error .  That's on my TODO list .

reply via email to

[Prev in Thread] Current Thread [Next in Thread]