Hi Sebastian! It is a very nice piece of work you and Stefan have done! I fully agree that we need to make archetypes compatibility checking explicit and this is a very good start.
It will be useful to publish the algorithm that you used for comparison so others could comment. And the same algorithm could be implemented in different tools to ensure interoperability of archetypes. Cheers, Rong On 9/10/07, Sebastian Garde <s.garde at cqu.edu.au> wrote: > > > > > Dear all, > > > > We have added prototype functionality to the Archetypefinder to compare two > versions/revisions of an archetype at > http://www.archetypes.com.au/archetypefinder/compare.html. This functionality > will later be integrated into the appropriate tools, but can be useful on its > own too. > > > > You can upload two archetypes and then see what changes have been made > between the two versions of an archetype. Also, the type of the changes with > regard to compatibility of the two archetypes (e.g. 'compatible with > revision', 'requires new version' or 'descriptive change') is shown. > > > > Have a look - USAGE: > > You can use URLs to archetypes as well as upload archetypes directly from > your local system . > > For example, you can use a modified blood pressure archetype and compare it > with the current blood pressure archetype from the openEHR site. For this just > > 1. Go to http://www.archetypes.com.au/archetypefinder/compare.html, > > 2. Copy the URL > http://svn.openehr.org/knowledge/archetypes/dev/adl/openehr/ehr/entry/observation/openEHR-EHR-OBSERVATION.blood_pressure.v1.adl > and paste it into the webform as URL for the original archetype (1st row, > last column) > > 3. Copy the URL > http://healthinformatics.cqu.edu.au/archetypefinder/openEHR-EHR-OBSERVATION.blood_pressure.v1.adl > and paste it into the webform as URL for the modified archetype (2nd row, > last column) > > 4. Click the 'Compare Archetypes'-button > > > > Please note that this is a prototype. We would be glad about any feedback, > bug reports, ideas, discussion. > > Especially, if you disagree with some of the conclusions about the > compatibility of two archetypes you submitted, please drop me an email or > discuss via this list! > > > > It is important to make the compatibility of archetypes explicit, so that > archetype-enabled software can decide this - we want to settle this issue > once and for all! > > > > Many thanks to Stefan Fuchs from the UMIT in Austria for heaps of hard work > on this during an internship with us! > > > > Best regards, > > Sebastian > > > > Dr Sebastian Garde > > Dr. sc. hum., Dipl.-Inform. Med, FACHI > > > > Research Fellow > > Faculty of Business and Informatics, Central Queensland University > > Austin Centre for Applied Clinical Informatics, Austin Health > > Heidelberg Vic 3084, Australia > > s.garde at cqu.edu.au > > Ph: +61 (0)3 9496 4040 > > Fax: +61 (0)3 9496 4224 > > http://healthinformatics.cqu.edu.au > > http://www.acaci.org.au > > Visit the new open access electronic Journal of Health Informatics (eJHI): > http://ejhi.net > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >
