oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi Otavio,

On Thu, 2009-09-03 at 13:12 -0700, Otavio Silva wrote:
>    I guess you are right, but I am still confused (or not anymore... I
> don´t even know if I am confused!)

Well, you are a little confused and probably some of the confusion
arises based on two things:

1) the work you did on the DSE demo
2) the fact that you are working on EpiS3 but not using the EpiS3
branch.

>    I have writen based on our (little) experience in the rabies and
> immunization models. 
>    In the rabies example, we don´t need an archetype for rabies for
> running a decision support engine, what we need is something that
> searches for values inside the archetypes.
>    But archetypes can do this. 
>    I thought for running DSEs and searching for values we will need a
> new ontology ( or a new semantic) that could make this easier. But you
> are right: archetypes are designed for it.
>    I guess I was wrong.
>    But I am going towards a complete compreension of the OpenEHR!!!!

First; there is a vocabulary (currently incomplete) for mammals in the
EpiS3 branch.  You will use this in the ontology of your archetypes.

Secondly; the work you did on the DSE demo was not archetyped data.  It
was a demo to demonstrate the syntax of communication with CLIPS via
PyCLIPS.

Remember that an Archetype as defined by the knowledge worker using the
archetype editor and expressed in ADL is a MODEL.  When used in an
application, portions of the archetype tell the application what type(s)
of data to capture and how to capture it.  These are data instances.
These instances are what are exposed to the DSE for processing. 

Does that help?

Cheers,
Tim

Attachment: signature.asc
Description: This is a digitally signed message part