Re: [Gnumed-devel] gnumed ideas 0.1 and post-0.1

[Richard Terry]

I approach this entirely differently from you Karsten, ie that of 
funcitonality.

The way I would do it is as thus.

1) Get demographics working (do nothing else until it is) and demonstrate you 
can load a patient.

2) Choose an easy section like Family History. Do nothing else until you can 
enter data on the screen, clear the data, save to the list
        Next save the record to the database, and re-display it, and prove that 
this 
works. Next modify the record, and prove your modifications work. Next delte 
the record and prove that works. Put it back in again and then add a few 
more. When entirely thrashed out do the next section

3) Pick say the scratch pad - do as above
4) Pick recalls, do as above, vaccinations etc. Leave the difficult ones to 
last ie script.

But everyone works on this - It's no use running off developing other more 
complicated areas until you can do the basics.

Eventually even some of your underlying table stuctures are going to have to 
be changed, becuase though theoretically correct, I guarrentee you they will 
not work properly in practice.

etc etc. Anyway, you get my drift.

Regards

Richard

On Fri, 18 Feb 2005 06:07 pm, Karsten Hilbert wrote:
> > > > Have we real disagreement on the point?
> >
> > Yeah, nice to see my name is not included.
>
> That was surely not intentional.
>
> > The main reason a prototype isn't running is that no-one will agree on
> > someone to take control, direct the program, decided on a gui, and start
> > making it work.
>
> The problem word in here is "decide". And then stick to it.
>
> > 6 Months would kill it if the programming resources were correctly
> > aimed.
>
> We have disagreement *here* unless you tell me which resources
> you are talking about.
>
> Karsten