Congratulations - this is great news Tim. Keep up the good work. Cheers, Sam
> -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Tim Cook > Sent: Tuesday, 14 April 2009 8:56 PM > To: For openEHR technical discussions > Subject: Re: Archetype-triggered events for CDSS > > On Tue, 2009-04-14 at 12:59 +0200, Pariya Kashfi wrote: > > Hi all, > > In the paper "Archetype 101" by Heather and Sam, there's a short > > discussion about CDSS, here comes a quote from it: > > "Intelligent generic decision support programs can rely on > > archetype-triggered events and for the first time operate in > > real-time." > > > > > > I wonder what is the exact meaning of Archetype-triggered events. > > IS any research done in this area before or has any implementation > > based on that been used in a CDSS so far? > > > > Archetypes allow for embedded First Order Predicate Logic therefore in > an application they can do some simple internal processing. > > The Epidemiological Surveillance Support System (EpiS3)[1] has been > funded for development (for 3 years, by the INCT-Macc network in > Brazil) based on the Python implementation of openEHR; aka. OSHIP[2]. > > Though background work began last year, the funding is expected to be > released within the next few weeks and development in earnest can > finally begin. :-) The OSHIP framework also includes event triggering > and we will be exploring several options using both of these triggering > mechanisms in conjunction forward-chaining inference and Bayesian DSS. > > [1] https://launchpad.net/epis3 > [2] https://launchpad.net/oship/ > > Regards, > Tim > > -- > Timothy Cook, MSc > Health Informatics Research & Development Services LinkedIn > Profile:http://www.linkedin.com/in/timothywaynecook > Skype ID == timothy.cook > ************************************************************** > *You may get my Public GPG key from popular keyservers or * > *from this link http://timothywayne.cook.googlepages.com/home* > **************************************************************
