[Gnumed-devel] Re: Gnumed-devel Digest, Vol 7, Issue 2

[sjtan]

On Mon, 2003-06-02 at 01:33, address@hidden wrote:
> Send Gnumed-devel mailing list submissions to
>       address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://mail.gnu.org/mailman/listinfo/gnumed-devel
> or, via email, send a message with subject or body 'help' to
>       address@hidden
> 
> You can reach the person managing the list at
>       address@hidden
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Gnumed-devel digest..."
> 
> 
> Today's Topics:
> 
>    1. old tables (Karsten Hilbert)
>    2. important point regarding episode/health issue (Karsten Hilbert)
>    3. clin_transaction (Karsten Hilbert)
>    4. v_i18n_allergy (Karsten Hilbert)
>    5. Re: error in gmPG? (Karsten Hilbert)
>    6. Re: error in gmPG? (Karsten Hilbert)
>    7. Re: tried different call (Karsten Hilbert)
>    8. Re: important point regarding episode/health issue
>        (Karsten Hilbert)
>    9. self.locked in gmTmpPatient (Karsten Hilbert)
>   10. dropping RO conns to backend (Karsten Hilbert)
>   11. what does cooked mean? (sjtan)
>   12. widget connecting (sjtan)
> 
> 
> ----------------------------------------------------------------------
> 
> Date: Sun, 1 Jun 2003 13:34:25 +0200
> From: Karsten Hilbert <address@hidden>
> To: GNUmed list <address@hidden>
> Subject: [Gnumed-devel] old tables
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Precedence: list
> Message: 1
> 
> Or maybe I was and didn't update parts of the code yet :-)
> 
> Karsten
> -- 
> GPG key ID E4071346 @ wwwkeys.pgp.net
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
> 
> 
> ------------------------------
> 
> Date: Sun, 1 Jun 2003 13:24:18 +0200
> From: Karsten Hilbert <address@hidden>
> To: GNUmed list <address@hidden>
> Subject: [Gnumed-devel] important point regarding episode/health issue
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Precedence: list
> Message: 2
> 
> These CANNOT under any meaningful clinical circumstances be
> created automatically. They MUST be chosen by the clinician.
> Creation of new episodes/health issues is POST-HOC *most* of the
> time.
> 
> Any data being entered for a patient will belong to
> "last_active_episode" by default. If there is none a
> "__default__" episode must be created (along with a
> "__default__" health issue) and registered as
> "last_active_episode".
> 
> "Allergies" is /perhaps/ one of the debatable cases for
> auto-generation of a Health Issue - if there's one there's a
> higher susceptibility to have more (these days anyways).
> However, episodes cannot be created by the system
> automatically (not reliably, anyways).
> 
> The rub here is that the GnuMed client GUI does not yet
> offer facilities for selecting the active episode/issue.
> 
> While technically OK the current allergy creation code is
> semantically wrong (apart from the debatable auto-issue).
> 
> BTW: Feel free to correct the spelling of definate...
> 
> Karsten
> -- 
> GPG key ID E4071346 @ wwwkeys.pgp.net
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

The sql script says the clin_episode_id field must be not null in
clin_root_item, which forces someone to decide which episode a root_item
is supposed to attach to at the time of entry. If the episode doesn't
yet exist, then you really need a episode and health issue browse and
entry ui  along side the normal UI  , else it is hard to make any
entries, due to the not null or referential integrity constraints.
If the system automatically generates or finds the episode and issue (
when possible, as in an episode of a Drug allergy ) , you can always
allow it to change the association later .