Dear Stef, Thanks for your question which is very important because it shows how clinical people understand the archetypes and Reference Model. I am sure you have got all responses to your question. In a word, the event time field is in the reference model which is not shown in the archetype editor. That's why you confused. I support Heather's suggestions. Archetype developer doesn't need to understand/know the reference model classes and all the fields in each class. They should be simply displayed in the archetype editor.
Cheers, Chunlan Heather Leslie wrote: >My view on this is simpler and more concrete - there will be a >date/time field displayed in the software User Interface (that comes >directly from the reference model, and that we don't need to >archetype). The default for that date/time may be now, but can be >changed to something else. > >Therefore don't need to archetype date and time separately. > > From my clinician point of view, the average clinical archetyper can >only imagine that what they see in the archetype will be what can >possibly be displayed on their User Interface. It would be ideal if we >can work to make the 'unseen' magic that comes from the reference model >clearer, as the UML diagram is (almost) totally unintelligible to >others, like me, and even if it can be understood, they may not >neccessarily be able to make the leap from the diagram to how it will >work in practice (ie a UI). > >Perhaps the apparently 'hidden' reference model stuff should perhaps >even be displayed, in an uneditable format, in the Archetype Editor and >Template Designer - to make this design process more transparent and >help bridge the clinical/technical divide just a little. > >Heather > >*Dr Heather Leslie >*Director, Senior Clinical Consultant >Ocean Informatics Pty Ltd >T 0418 966 670/+61 418 966 670 >Skype - heatherleslie > > >Thomas Beale wrote: > > >>Stef Verlinden wrote: >> >> >> >>>Maybe I've been looking for something that isn't there, so for now >>>I've solved it to add a date and time of measurement field to the AT >>>data section. >>> >>> >>> >>you don't need to so this - it is already in the reference model - not >>every attribute in the reference model classes are mentioned in >>archetypes. The reference model classes for History, Event etc are >>visible here - >>http://www.openehr.org/uml/release-1.0.1/Browsable/_9_0_76d0249_1109157527311_729550_7234Report.html >> >>When any class name is mentioned in an archetype (such as OBSERVATION, >>HISTORY, EVENT etc), all the attributes from the openEHR reference model >>are assumed to be there. The archetype only needs to mention those >>attributes that make sense to constrain ahead of time - typically this >>does not include date/time attributes or other specifics of locale or >>context. >> >>- thomas beale >> >> >> >>_______________________________________________ >>openEHR-clinical mailing list >>openEHR-clinical at openehr.org >>http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical >> >>__________ NOD32 2283 (20070521) Information __________ >> >>This message was checked by NOD32 antivirus system. >>http://www.eset.com >> >> >> >> >> >> >_______________________________________________ >openEHR-clinical mailing list >openEHR-clinical at openehr.org >http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical > > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Dr Chunlan Ma * * * * Ocean Informatics Pty Ltd * * Ground floor * * 64 Hindmarsh Square * * Adelaide, SA 5000 * * P +61 8 8223 3075 * * Skype - chunlan_ma * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20070523/cfa48bfd/attachment.html>
