Is there any roadmap/guideline to the implementation of graphical components
that work with openEHR data types?

 

Ricardo Correia

 

De: openehr-clinical-bounces at openehr.org
[mailto:openehr-clinical-bounces at openehr.org] Em nome de Stef Verlinden
Enviada: ter?a-feira, 10 de Julho de 2007 9:42
Para: For openEHR clinical discussions
Assunto: Re: Microsoft/NHS common health interface and openEHR datatypes

 

 

Op 10-jul-2007, om 1:07 heeft Sam Heard het volgende geschreven:





Dear All

We are beginning to use the Microsoft Common Health Interface controls in
our software. I think it would be good to keep this work open and shared so
that we get them working with the openEHR datatypes (it is a very good fit
at the moment). The first one off the rank will be the datetime control as
this is the only one that looks finalised.

Sounds very promising. What are the forthcoming CHI controls?




Should we keep the source on the openEHR site? I wonder if Tony Shannon or
Mike Bainbridge could give us any direction on how to do this most
effectively.

 

Yes please. Anything that helps the community to speed up the development of
usable implementations is very welcome.




Cheers, Sam

-- 

 

Cheers,

 

Stef






Dr. Sam Heard
MBBS, FRACGP, MRCGP, DRCOG, FACHI


CEO and Clinical Director
Ocean Informatics Pty. Ltd. <http://www.oceaninformatics.biz/> 
Adjunct Professor, Health Informatics, Central Queensland University
Senior Visiting Research Fellow, CHIME, University College London
Chair, Standards Australia, EHR Working Group (IT14-9-2)
Australia

    Ph: +61 (0)4 1783 8808
    Fx: +61(0)8 8948 0215
UK
     Ph: +44 (0)77 9871 0980
    Fx: +44 (0)207 1174610

 

_______________________________________________

openEHR-clinical mailing list

openEHR-clinical at openehr.org

http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20070710/2ad2c6b9/attachment.html>

Reply via email to