Hi Gerard, My understanding is that demographic services collect, organize and process the characteristics of a 'population'. Presuming this, then I am a member of a large number of 'populations' regardless of intent. Narrowed to Healthcare the number of 'populations' shrinks but not to one.
Given the fact that modern 'populations' are not 'stationary' it appears that there are many of us that can claim or hold membership in multiple Healthcare 'populations' which themselves are subject to new additions, e.g., those genetically sensitive to drugs of a particlular family. Identifying the indiviudal may have to be a separate operation. Identifying whether the individual is a member of a 'population', or 'populations's a subsequent task. A 'demographic server' is likely to be specific and limited in scope to address 'super populations', e.g., persons residing within the boundaries of a specific geographical region, e.g., Africa. A 'network' of such server could provide additional coverage. Since one can apply a variety of rules to the specification of an individual 'population', the 'rules' become significant especially where the 'rules' are chosen to affect results, all Diabetes Patients in the London area. Due to a number of reasons one may not be able to claim that London-area Diabetes Patients are the same as those in other regions, and, of course, that the Healthcare systems are the same or equivalent. Foundational is 'personal identification'. Without it a 'demographic server' is handicapped. Hence a good test for the server is a seriously injured person arriving at a Healthcare facility unable to communicate with no other form of identification. Since there are many other 'issues' and 'factors' important to the design, development and deployment of a 'demographic server' one may have to accept discussions that attempt to integrate topics. They are valuable R&D efforts are results-oriented expectations are very likely to increase quickly. Regards! -Thomas Clark BTW: I tried to avoid bringing 'Public Health' into a discussion about 'demographic servers'. That would have been lengthy! Gerard Freriks wrote: > TNO, the institute I work for, is of the opinion that the archiving > solution is the preferred one. > > By the way. > The topic started discussing demographic services. > > In general interoperability translates into the need for many shared > points of reference. > So for identities of persons as wel. > Since persons are recorded in systems using a set of more or less > unique features and since these unique features vary in time, one > person will have many digital identities. > This calls for a mechanism that unites all these variations on one theme. > Eg the demographic server. > > > Gerard > > -- <work> -- > Gerard Freriks > TNO Kwaliteit van Leven > Wassenaarseweg 56 > Leiden > > Postbus 2215 > 2301CE Leiden > The Netherlands > > +31 71 5181388 > +31 654 792800 > On 05 Mar 2005, at 19:46, lakewood at copper.net wrote: > > Other: > -If something crucial shows up on your monitor screen, do a Screen > dump to a file > and create a time/date stamped archive. It is a record and a > mechanism exists to > produce a permanent copy easily reproduced on paper. > - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
