At 9:48 PM +0100 1/1/06, Karsten Hilbert wrote:
> attached is a first attempt at the aust nips schedule which passes the
integrity constraints of the gnumed vaccination regime
schema. hopefully this is acceptable for the au database config.
I have added it to the standard bootstrapping process and it works.
So two questions:
1. Does the standard bootstrapping process "read" some machine
configuration, to decide the country to which the machine is
configured (and if it finds none, prompt the user) and, with this
information, the bootstrapper installs country-specific data sets? It
is just that -- for example -- even though I live and work in Canada,
it would be useful for the tables to be populated with (for example )
state/province/territory values for other countries on account of
travellers who may become patients.
So it is helpful to clarify if we have a structure and process that
*limits* what gets imported as opposed to one that imports while
*preserving* country/region specific information so it can be
recognized and treated separately later, if that should prove
important. I don't remember the details but it sounds a bit like the
drugref design in which it would be possible to "pull out" the data
sets that had been provided but later withdrawn by the provide (e.g.
drug company)
2. Specifically regarding what Syan has put together on top of
anything that already existed for vaccinations, is there any summary
useful for the wiki? Are there any key posts that describe main
design drivers? If not, I can wait until I have a chance to "try"
these parts and ask from a user point of view.
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
