Hi all,

I would like to be on the list as I am interested in developing
archetypes. I think there is much to be learnt regarding deciding how
to break up the data requirements into sensible (from interoperability
point of view) concepts, i.e. archetypes. For interoperability reasons
these concepts need to be fairly general. The specific requirements at
one site are then fulfilled by plugging them together and further
constrain them via templates.

Some kind of wiki documentation (howto, examples,...) would be cool to
gather the thoughts. However I can't promise to make much of a
contribution as I am very time restricted at the time.

Cheers, Thilo (medical student about to start with PJ)

On 2/5/07, Sebastian Garde <s.garde at cqu.edu.au> wrote:
>
>
> Dear all,
>
> We have a psychiatrist from Chile here for the next month who will work with
> us on developing an initial set of Mental Health archetypes.
>
> We would like to set up a little group to discuss these archetypes from a
> clinical point of view...so anybody with an interest in this area please
> drop me a quick email, we would very much love you to join us (most likely
> virtually...) and work together with us on these archetypes.
>
> Kind regards
> Sebastian
>
>
>
>
>
> Dr Sebastian Garde
> Faculty of Business and Informatics, Central Queensland University
> Austin Centre for Applied Clinical Informatics
> Austin Health
> Heidelberg Vic 3084, Australia
>
> s.garde at cqu.edu.au
> Ph: +61 (0)3 9496 4040
> Fax: +61 (0)3 9496 4224
>
> Skype: gardeseb
> http://healthinformatics.cqu.edu.au
> http://www.acaci.org.au
>
> Visit the new open access electronic Journal of Health Informatics (eJHI):
> http://ejhi.net
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at openehr.org
> http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
>
_______________________________________________
openEHR-clinical mailing list
openEHR-clinical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical



Reply via email to