Sam, I agree that it is most likely bad archetype design if one reuses a structure archetype for various archetypes as 'data'. The editor shouldn't support this as it is more likely than not leading to an inferior design. I don't see a structure archetype being reused in two data slots. Not sure however if we are sure enough about this yet to change the reference model for data not to be a slot. While you probably never want to reuse an archetype in two data slots, one (probably remote) possibility could be that you want to reuse a structure archetype that is used as part of an ACTION and INSTRUCTION archetype also within the (one) data slot of an OBSERVATION or EVALUATION archetype? I know the following is not a 100% correct example, but simply for the sake of discussing the possibility of this: A medication description (which is already used in Action and Instruction archetypes) is being reused in the data part of an Observation archetype to document the titer/actual amount of medicine found in the patient's blood. (It's more likely that - if at all - only part of the data would be the same and you would use CLUSTER archetypes rather than structure archetypes to do this, but someone else may come up with a better example.) Or consider an instruction for a patient to regularly use a bike with ~60 rotations/min and a maximum pulse rate of 150. The related Action/ Observation (what of the two would it be...?) could be documented as various between say 55-65 rotations/min and a constantly changing pulse rate. Cheers Sebastian
________________________________ From: Sam Heard [mailto:[email protected]] Sent: Tue 4/09/2007 9:28 PM To: openEHR-Clinical Cc: John Arnett Subject: Embedded archetypes - should there be any tooling constraints? Dear All A design issue has arisen from the NHS team as there is a bug in the archetype editor when you try and embed an archetype in the data page. You do this by clicking the embed archetype check box before you choose the structure type (list, tree, table...). This has traditionally been used to utilise the same structure for ordering as for recording the action as in medication or procedure. It is possible that archetypes could share the same state information (e.g. pulse and blood pressure) and even protocol - but it seems impossible that different archetypes could share the same data. I believe such a situation should be dealt with by specialisation as the data specification really defines the archetype. I am interested in other people's views. The consequence is that the embedding option will not be available in the editor for the data structure. We could put it forward as a change request for an invariant in the reference model (data is not a slot) if people strongly agree and there is no dissent. Cheers, Sam -- Dr Sam Heard Chief Executive Officer Ocean Informatics Director, openEHR Foundation Adj. Professor, Central Queensland University Senior Visiting Research Fellow, University College London Aus: +61 4 1783 8808 UK: +44 77 9871 0980 -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 12872 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20070904/807f9e48/attachment.dat>
