Syan, > on second thoughts, maybe just have a issue_script clin_root_item sub class, > and have a lnk_precendent_root_item table that refers to precedent and > consequent root_items , and this would take care of medication change, > which would be a clin_medication that has a lnk_precedent_root_item > that exists with it as a consequent link, and another clin_medication > as a precedent link. I sense something here that you want to convey but which I don't quite get yet that sounds like a useful idea. Maybe I understand better if you explain what about clin_medication does not allow to track medication changes. I think it got to do something with ...
> it would also track causative/rationale links between root_items. ... this. Which reminds me of a question posed once upon a time by Jim, namely how to interlink issues/episodes. > clin_request covers things like radiology, colonoscopy, gastroscopy, > nerve conduction study, lung function testing ,audiology, doesn't it ? Agree. > ( in au, these are non-consultation > direct specialist procedural requests issued by gps). This is possible in DE, too, but rarely used. > As well as all the paramedical stuff ( I'd still call physio, podiatry, > dietician, > district nursing , consultations though). Yep. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
