Screenshots of newly developed Java Archetype Editor

Dear All,

As some of you might know, we are a couple of master's thesis students at Linköping University in Sweden that will be finished with our work of developing an archetype editor in the near future. The application is developed entirely in java and the source code is to be published as open source when our work with it is done. The URL below shows a couple of screenshots of the java archetype editor based on the Acode implementation of the openEHR reference model.

http://www.cyd.liu.se/users/~johhj833/openehr/

The current ADL-version that the java kernel and thereby our editor supports is ~0.9, but we would like to see support for ADL 2.0 in the future.

Best regards,

Johan Hjalmarsson
Mattias Forss

Dear All,

As some of you might know, we are a couple of master's thesis students at Linköping University in Sweden that will be finished with our work of developing an archetype editor in the near future. The application is developed entirely in java and the source code is to be published as open source when our work with it is done. The URL below shows a couple of screenshots of the java archetype editor based on the Acode implementation of the openEHR reference model.

http://www.cyd.liu.se/users/~johhj833/openehr/

Hi Johan,

This looks very good indeed. I am starting to play around with archetype design, based in Scotland ,UK and would be very interested to try out your editor when you feel it is ready for public consumption (or testing). I am an ex-doctor and experienced programmer, though in Delphi rather than Java, and would be happy to contribute if this was helpful.

With the Ocean editor, I could not see a way to easily nest an archetype within another e.g. I was constructing a BMI archetype which I wished to base on 2 existing archetypes, one for height, one for weight - I have looked at your definitions page screenshot but cannot see which Add button option could be used.

Ian

hello johan,

i'm a student at technikum wien in vienna. i'm in a group of students who started to learn more about the concept behind CEN 13606 and the archetypes. We are just started our study in this field.

I started to read the openEHR documents and looked at the eiffel and java version of the adl parser, but eiffel is not so easy and the last java version is a little bit buggy.

Is it possible to test your editor? And is it possible to get the source, so I could see how the concepts of openEHR are made to real code?

thanks in advance and greetings

markus koller

sorry for my english :frowning:

Johan Hjalmarsson schrieb:

Hi Markus,

I'm glad to hear that you have interest in our editor, however the source code will not be released until we are done with our work, sorry. This is to avoid comments about bugs and lack of functionality that we already are aware of.

We base our editor completely on the java ADL parser and kernel. If you would like to know more about how the concepts of openEHR are transformed into real code, then look at the adl.jj source in the src/javacc package of the ADLparser and also in the minimal unit tests of ADLOutputter.java in the src/test/../outputter package of the java kernel.

Try to parse an archetype with the java parser and then read the API in order to know how to output some data, it should explain quite a lot. Also check out the Archetype.java in src/java/../archetype package to know how to create archetypes.

Regards,

Johan and Mattias

Markus Koller wrote:

Ian McNicoll MMS wrote:

Dear All,

As some of you might know, we are a couple of master's thesis students at Linköping University in Sweden that will be finished with our work of developing an archetype editor in the near future. The application is developed entirely in java and the source code is to be published as open source when our work with it is done. The URL below shows a couple of screenshots of the java archetype editor based on the Acode implementation of the openEHR reference model.

http://www.cyd.liu.se/users/~johhj833/openehr/

Hi Johan,

This looks very good indeed. I am starting to play around with archetype design, based in Scotland ,UK and would be very interested to try out your editor when you feel it is ready for public consumption (or testing). I am an ex-doctor and experienced programmer, though in Delphi rather than Java, and would be happy to contribute if this was helpful.

With the Ocean editor, I could not see a way to easily nest an archetype within another e.g. I was constructing a BMI archetype which I wished to base on 2 existing archetypes, one for height, one for weight - I have looked at your definitions page screenshot but cannot see which Add button option could be used.

Ian

Hi Ian,

Thanks.

We think this problem resembles what is done when two section archetypes are combined into a composition with Oceans archetype editor. This requires to create two different section archetypes that contain the weight and height archetypes. These should the be included in a composition archetype. However, if you'd like to create an archetype that is, say an evaluation archetype which is based on the two other archetypes, then you want to be able to insert so-called archetype slots in the (BMI) evaluation. Then you could also add invariants that states the relation between the two archetypes e.g. weight/height^2. We would like to see this functionality in our editor, but at the moment none of it is supported.

Regards,

Johan & Mattias

Hi Johan, Mattias,

Congratulations on your excellent work on the Archetype Editor!!

Well done! :slight_smile:

Rong

Johan Hjalmarsson wrote:

In fact, all archetype compositional structuring is done with "Slots" (via the use_archetype keyword). The question is just how to clearly represent the slot idea on the screen. The Ocean editor uses some funny shapes a bit like the idea of keys (i.e. then you indicate what things can fit in the slot), but I am sure the graphics wizzkids from Linköping will leave our efforts in the dust;-)

- thomas beale

Johan Hjalmarsson wrote:

And I meant to say, excellent effort. One thing for everyone to beware of: ADL is moving to 2.0 in Release 1.0. There will be a bit of pain for all us parser writers, and also for people who have archetypes in previous versions of ADL. But once ADL 2.0 is implemented, we are safe (since ADL 2.0 makes the whole archetype a dADL text, so later changes don't change the syntax).

- thomas beale

Johan Hjalmarsson wrote: