Op vrijdag 11 maart 2005 11:42, schreef Karsten Hilbert: > On Fri, Mar 11, 2005 at 10:31:09AM +0100, Bert Verhees wrote: > > Op donderdag 10 maart 2005 13:48, schreef Karsten Hilbert: > > > > There are no fixed patterns for names or naming conventions. > > > > There are many societies where there are no 'Family' names at > > > > all. Some have Tribe names in lieu, some with father's or > > > > village name as 'names' somewhere wedged in the name string. > > > > Some with just unique names with nothing else. To add to this > > > > confusion you would then have to find sub-components for nick > > > > names and aliases. > > > > > > Yes, the whole gamut :-) > > > > > > In GnuMed we deal with it like this: > > > > Where do you put initials and how do you qualify them as such so they can > > be recognized in an automated process. > > We don't have dedicated initials support. Most of the time (I > know no other use) initials are the first character of the > first name(s). So we either store them as first names (if we > don't know the first name but know the initial) or we do not > store them. > > I do not completely understand why you need to be able to > *process* initials ?
I am extracting data from existing systems, and put them in a CEN-structure (this is simplified saying of what I am really doing). I do not want to loose vital information in this process There is one system that stores person-data as - Roepnaam (dutch for "call name") - Initials It is necessary that to distinguish as much as possible one person from another, both are known in the extracted data. The extracted data can be used for automated processing, so an automated process needs a qualifier to distinguish as callname from initials. That's why > > Karsten -- Met vriendelijke groet Bert Verhees ROSA Software - If you have any questions about using this list, please send a message to d.lloyd at openehr.org - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
