Bert, The Ocean Archetype Editor was the first Archetype Editor written some 6+ years ago. It was implemented to support only EHR archetypes in a way that these RM types where implemented explicitly within the Editor providing the specific capability for clinicians to easily develop archetypes with minimal knowledge of the RM.
Certainly a generic archetype editor would need to support the features you suggest below, but the Ocean Archetype Editor is not a generic Archetype Editor. Even with its limitations known best by Ocean, I think we can all agree that it has served the openEHR community well in bringing the mind shifting concepts of archetypes to a point where the openEHR architecture is in demand internationally. Regards Heath From: [email protected] [mailto:openehr-technical-bounces at openehr.org] On Behalf Of Bert Verhees Sent: Sunday, 15 March 2009 11:26 PM To: For openEHR technical discussions Subject: Re: Why is the editor not opening ADL files? Williamtfgoossen at cs.com schreef: In a message dated 14-3-2009 17:23:18 W. Europe Standard Time, caultonpos at gmail.com writes: How many more types of archetypes are we envisioning to support? I think the tools need to support ANY archetype that represents valid content in health care. An archetype editor should simply support any archetype which represents a valid locatable according to the reference model, plus, it must adapt the other archetype-rules as defined in the reference model, such as header requirements, etc. That is why I don't understand the trouble with supporting demographic archetypes, it are just locatables, with a few extra characteristics, but that is also the case for composition or other archetypes. It are all just locatables. Maybe some one can explain this. In a few months, I will have more time, I will add the support myself, I even install Windows, if necessary. Maybe I find out by then what I have overlooked all the time. Bert -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090316/bd0a9595/attachment.html>
