[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] developing packs of Consumable substances / medicatio
Re: [Gnumed-devel] developing packs of Consumable substances / medications
Thu, 2 Jun 2011 09:40:01 +0200
On Wed, Jun 01, 2011 at 08:56:06PM -0700, Jim Busser wrote:
> Can I suggest / request that the default set of consumable substances
> (provided, I think, by vbanait) is
> - removed from default bootstrap installation, or
We can disable it being applied by default once data packs
are implemented and it has been turned into a data pack.
That won't affect existing v15 databases, though.
> - configured so as to be installed only when no alternative set of substances
> was available in whatever was the locale
That is not easily detectable.
> For example, in the case of CA, I would like to provide a
> set of data that could be part of a "pack" of medications
> which could be bootstrapped by people who would install
> GNUmed in CA.
Great. CA users would also benefit from using FreeDiams
which already comes with CA data which gets - on a case by
case basis - imported into GNUmed.
> This leads me to my next question, which is -- if I lack
> the skills yet to write my own pack (and I am still far away
> from that)
Especially since the data pack layout/format hasn't been
decided yet :-)
> -- if I can still help with preliminary work, by supplying
> the data in a way that makes it less work to be converted?
> What I am wondering is whether there is a preference to whether I would
> supply the data as
> - a single, monolithic (non-normalized) table whether it would be in
> comma-delimited or tab-delimited or sqlite format
> - or as a series of individual tables (each table being its own file)
> and what the field or columns and in what sequence would be contained.
I have no idea. It will depend on the complexity of the
original source, too. The "staging." schema is the intended
playground for such matters.
The key principle for data packs needs to be that they must
only provide passive data and not any custom scripts GNUmed
needs to run on their behalf.
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346