Hi,
I read the Template OM linked in the previous email(from wiki)
  
http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
, but I couldn't find complete information about Methods, their input  
values and outputs, etc.  In donated java code from Zilic company,   
there's no documentation either.
Can anyone suggest another resource?
I need to understand all those methods in detail to be able to create  
a GUI based on Templates for my application.

Regards
Pariya

On Nov 6, 2008, at 12:39 PM, Ian McNicoll wrote:

> Hi Olef,
>
> I'm sure someone from Ocean with more detailed technical knowledge  
> will give a more precise answer but you might consider using the  
> forthcoming formal openEHR Operational Template specification for  
> this sort of exercise. I have been working with Derek Hoy's Clinical  
> Templates project (www.ClinTemplate.org), which uses a simple web- 
> based approach to gathering clinical data entry requirements and at  
> present uses a custom internal XML format. We are lookng (fairly  
> quickly) to use the openEHR operational Template specificaction  
> (OPT) as the back-end formalism. We think this approach will be much  
> easier as the Oet files only contain the constraints on underlying  
> archetypes (effectively a diff) whilst the OPT format contains the  
> underlying archetypes themeselves and can be easily used to generate  
> XSDs or other artefacts.
>
> see 
> http://www.openehr.org/wiki/display/spec/openEHR+Templates+and+Specialised+Archetypes
>
> The openEHR specification is very close to completion.
>
> It would be interesting to know more about your project. We are  
> aware of a requirement for a data-entry/UI requirements gathering  
> tool which, though based on openEHR templates, goes somewhat beyond  
> their natural domain in capturing further UI requirements and rules.  
> The Clinical Templates work has more of a focus on generic  
> infomation standards capture, rather than specific local data-entry  
> but there is considerable cross-over.
>
> Regards,
>
> Ian
>
>
> Dr Ian McNicoll
> office / fax  +44(0)141 560 4657
> mobile +44 (0)775 209 7859
> skype ianmcnicoll
> ian at mcmi.co.uk
>
> Clinical Analyst - Ocean Informatics ian.mcnicoll at oceaninformatics.com
>
> Member of BCS Primary Health Care Specialist Group ? www.phcsg.org
>
>
> 2008/11/6 Olof Torgersson <oloft at chalmers.se>
> Hi,
>
> Sorry if this is the wrong forum.
>
> Is there a description somewhere of the oet-files produced by the  
> Ocean Informatics Template Designer?
>
> I would like to use the templates in an application as a basis for  
> input forms, but then I need
> a specification of the file-contents.
>
> Regards
>
> Olof Torgersson
>
> ---
> Olof Torgersson
>
> Associate Professor
> Department of Computer Science and Engineering
> Chalmers University of Technology and G?teborg University
> SE-412 96 G?teborg, Sweden
>
> email: oloft at chalmers.se
> phone: +46 31 772 54 06
>
>
>
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical

Regards
Pariya

PhD Student
Interaction Design Division
Department of Computing  Science and Engineering
Chalmers University of Technology

Email: hajar.kashfi at chalmers.se
Office:+46 (0)31 7725407
Mobile Phone: +46 (0)707222815
Web: http://www.cs.chalmers.se/~hajar.kashfi/
Visit: Room Simula B, House Svea, Campus Lindholmen
Postal adress:
Email: hajar.kashfi at chalmers.se

Phone: +46 31 772 5407

Office: Room Simula B, House Svea, Campus Lindholmen

Postal Address: Chalmers University of Technology, SE- 412 96  
Gothenburg, Sweden

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20081118/4443b91a/attachment.html>

Reply via email to