Re: [Gnumed-devel] clin_root_item

[Karsten Hilbert]

> At the moment, I was thinking of yamilizing user input, into one text 
> field, and then putting it on a clin_root_item.
a clin_root_item descendant, for sure

> e.g. I'm using clin_history with type = 2( past)
ah, ok

>  and storing it on the 
> narrative field.
yep, that's like i thought of doing it

but only past history date should be stored like that,
other stuff goes into other (possibly not-yet-existing) tables

> should there be a special field , or cross-referenced table for 
> application-specific input data ?
> (e.g. with fields like   application_name,  schema_url, version,  data, 
> application_data_path , id_clin_root_item)
if i understand you correctly, no, you'd need to set up your
own tables for that, as the schema we have now is supposed to
store data independant of the application used to retrieve it

Data-wise I MUST be able to successfully run my clinic on the
command line psql utility alone (in theory, at least). Given I
know enough SQL and psql, of course. But the data must make
sense without a specific application. That's one of the most
basic tenets.

> family_history can be mapped to clin_history with a different type,
> allery mapped to mapped to allergy
> vaccination mapped to vaccination
> prescription to prescription
absolutely

> ? what about measurement.
gmMeasurement.sql

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