[Top][All Lists]

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

Re: [Gnumed-devel] Re: schema choice - patient names, aliases, duplicate

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Re: schema choice - patient names, aliases, duplicates and merging
Date: Thu, 25 Dec 2003 03:35:50 +0100 (MET)

> Syan's question included name and sex which made me wonder how it is 
> proposed to handle:
> - patients undergoing name changes where it remains helpful for their 
> other "aliases" to remain indexed
a patient can have as many name rows as needed, only one can be active, an
(academic/...) title does NOT belong to a name, it belongs to an identity

> - patients inadvertently duplicated (doubly-entered with duplicate, or 
> variant, name spellings and birth dates) who are later realized to have 
> multiple encounters/transactions on file under different identities 
> which require a "merge"
Well, yes. No code there yet, of course.

> - when creating a record (e.g. for a new patient), is there a useful 
> distinction between the *fixed* properties that identify an individual 
> (birthdate and USUALLY their sex and name) versus "variable" properties 
> such as their phone numbers, addresses, health insurance numbers - some 
> patients requiring multiple contact numbers. addresses, health 
> insurance numbers to be stored
Why of course. What else use would it be to stick to an RDBMS? You need to
read the schema, particularly the tables identity and names.

> ... also, I have been impressed with the look-up value of a telephone 
> number, for example when renting a movie at the local video store ---> 
In some countries reverse-lookup is illegal. OTOH, think of the lookup value
of a zip code. Then take a look at the views zip2data etc.

> The above affect how patient uniqueness is maintained while keeping it 
> easy to find them AND distinguish them from each other. If this is 
> already well developed and documented anywhere can anyone direct me, 
> else may it be of value/interest to discuss in a thread, or is there a 
> point person leading this service/module with whom I should exchange 
> questions/ideas offline?
We already have sort of a white paper for assigning a PUPIC. No one's got
around to putting forward a real proposal or even code on how to actually do
it. Please feel free to share your ideas on the list.


+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS!

reply via email to

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