Re: [Gnumed-devel] describing use cases

[Ian Haywood]

> not id_ as was done in the names table so the changes should be
>           identity.id->identity. pk
>           names.id->names. pk
>           names.id_identity->names.fk_identity (referencing identity.pk)
>  will renaming this break anything badly?
Yes. Although it can and should be done, I would like to get demographics 
working first.
> - not sure how the tables identity and names work together... is a new 
> identity row to be created only through the creation of a new row in 
> names, and is the enforcement here at the middleware or gui level as the 
> schema cannot achieve it?

names stores all the present and past names of an individual.
So when Jane Smith marries Fred Jones, her herpes PCR from
two months ago (yes some labs take that long around here)
will still match in the database.

> HL7 (or specialist practices using gnumed) as yet non-existent in 
> Australia?
Not for referral, AFAIK.
To most specialists computers are for secretaries and residents,
certainly the older generation won't even look at the screen
(we have to print out all the path. to show them, sigh)

> >I am doing this now as part of the "Richard space" framework.
>
> Which would mean you are reinventing the wheel. What else
> would the built-in XML-RPC server started by the --slave
> option be for ? That can be used to drive the GnuMed GUI to do
> anything you desire. It may offer gaps for improvement, though.
Hmm, not sure we're talking about the same thing.
I am writing a demographics panel which can select identities
independently of loading the "global patient"

Ian

signature.asc
Description: OpenPGP digital signature