Re: [Gnumed-devel] An Analysis of Demographics - Comments RT

[Karsten Hilbert]

> Beyond the above, a patient may have several forms of health care 
> registration / coverage numbers (a Workmen's compensation file number 
> is also common), and while any one payer may be most relevant to a 
> given patient, perhaps in a lookup screen, to resolve excess matches, 
> it may only be practical to list whatever is the "main" health related 
> number for whatever is the locality.
Well, that is precisely why the patient selector widget has
the concept of patient_expander. When excess matches are found
a locale-dependant patient_expander is invoked which returns
arbitrary amounts of additional patient-specific data in a
well-defined format. The frowned-upon list popup knows how to
display this format no matter what's in it.

> Alternatively, to be able to 
> over-ride on a per-patient basis which number(s) to display in the 
post-0.1

> lookup, but then you;d have to provide a label in context with the data 
> as a 'column heading" would be meaningless.
That's one of the concepts the patient_expanders use: provide
labels for the fetched data.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346