On Mon, Apr 25, 2005 at 10:18:29PM +0800, Syan Tan wrote: > if consultation events had subtypes, > then change current medication , and issue script, should > be separate consultation events, which could be record in the EMR. > > actually , looking at the book again, change-current-medication, and > issue-script > would be instances of an action type class which an action attribute is an > instance of, since actually subtypes of action > class would be proposed action, abandoned action, implemented action, > completed > action, implemented-but-abandoned action. Probably inheritance is for the > later > heirarchy, because there might be additional attributes in the subclasses e.g. > when abandoned, when implemented, when completed. > > The outcomes of an action are observations (a subtype of observation, that > has a link to a precedent action), according to the book.
All this sounds like what OpenEHR does. We don't, however, have a metamodel, that is to mean we *implement* actions instead of *modelling* them (and subsequently executing the model). 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
