[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] What to do with information in popups
From: |
Richard Terry |
Subject: |
[Gnumed-devel] What to do with information in popups |
Date: |
Wed, 10 Nov 2004 08:27:16 +1100 |
User-agent: |
KMail/1.5.4 |
As in all information in the SOAP area it should not become medical records (I
beleive) until accepted as such by the user and implicitly saved - by either
hitting a function key (I use F12 to save all currently unsaved data) or
clicking a save icon on the task bar. It is not infrequent that we want to
modify details as we write - just as we do in written clinical notes.
REgards
richard
On Tue, 9 Nov 2004 09:00 pm, Karsten Hilbert wrote:
> > This is certainly coming on well. Almost useable !
>
> But it does not work on wxPython 2.4. Unless we don't want a
> SOAP control in 0.1 this will not help us.
>
> > - the SOAP control will always be visible on the screen - it is akin to
> > your paper page you are writing on on your desk. The OK.CLEAR buttons
> > when clicked needs to drop the contents of the SOAP control onto the
> > progress notes list underneath.
>
> Well, the SOAP control itself won't care what callers of it do
> with the information it delivers. If the user clicks OK it
> should just emit a dict keyed by section that contains the
> information entered into it. Whether the caller drops that
> into some list or writes it to the database or generates a
> song from it is of no concern.
>
> One thing I am wondering about is: How are we intended to deal
> with data having been typed into a functional popup ? Eg.
> imagine the user incantates the magic string that pops up the
> vaccinations control. After completing that control the user
> clicks OK. What happens next ? One thing is that we do want to
> drop a quick note about the vaccination into the SOAP widget.
> OTOH, we would also want to store the vaccination details into
> the database. Do we do this immediately when OKing the
> vaccinations popup ? If so how do we handle the case when the
> user CANCELs the master SOAP control ? If not where do we keep
> that information around and until when ?
>
> Getting this right is just as important as making it visually
> useful.
>
> Karsten
- Re: [Gnumed-devel] Carlos - Soap2 - design comments, (continued)
- Re: [Gnumed-devel] Carlos - Soap2 - design comments, Karsten Hilbert, 2004/11/10
- [Gnumed-devel] Comments on the 2.5 Design criticisms, Richard Terry, 2004/11/10
- [Gnumed-devel] Re: Comments on the 2.5 Design criticisms, Karsten Hilbert, 2004/11/11
- Re: [Gnumed-devel] Re: Comments on the 2.5 Design criticisms, Richard Terry, 2004/11/11
- Re: [Gnumed-devel] Re: Comments on the 2.5 Design criticisms - Oops +png, Richard Terry, 2004/11/11
- Re: [Gnumed-devel] Re: Comments on the 2.5 Design criticisms, Karsten Hilbert, 2004/11/14
- Re: [Gnumed-devel] Carlos - Soap2 - design comments, Karsten Hilbert, 2004/11/10
- Re: [Gnumed-devel] SOAP2.py questions from Richard, Karsten Hilbert, 2004/11/09
[Gnumed-devel] What to do with information in popups,
Richard Terry <=