[Top][All Lists]

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

Re: [Gnumed-devel] Gui-Designers was the id_name debate

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Gui-Designers was the id_name debate
Date: Thu, 16 Sep 2004 19:39:53 +0200
User-agent: Mutt/

> 1. It is touted as Open Source GPL-licensed however it was developed 
It is handled pretty much the BSD way, it seems (not the BSD

> 2. Lack of a clear framework, and specifications on which to build. 
> One of the merits of an open source medical system ought to include 
> the ability to get one's data out, but in parts of OSCAR it may not 
> be possible. Vaccination information is for example stored as XML 
> blobs that are meaningless except relative to the form through which 
> the data was managed. Each form apparently permits the creation of an 
> associated table, specific to the form. Possibly every vaccination 
> form, and table, can be different.
This is both the power and the peril of such generic/general
frameworks that work with "models of models". OIO is the
perfect example.

> To enter a date of birth you must input the YYYY via keyboard but 
> having done so, the next press of the tab key skips the month and day 
> fields, and moves ahead into the health insurance number. This is 
> because the month and day are popups. OSCAR refuses to permit you to 
> create a patient without entering a date of birth,
As it should.

> yet permits you to enter a dob of Feb 31, 1990.
Sounds like it depends upon the data validity checks of the
backend - and this sounds like it talks to MySQL. PostgreSQL
wouldn't let you do that -- provided you have used an
appropriate datatype for the dob field...

> This goes back to the backend issues. If 
> you create a patient with a duplicate health insurance number, OSCAR 
> complains that "one of the keys has been duplicated" (it does not 
> tell you which key) but this is an after-the-fact prompt, after 
> having already permitted the duplicate record to be created.
Are you sure ?

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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