New alpha of release 1.0 archetype editor

Technical (archive)
1

Hi Everyone

I have posted a new exe of the release 1.0 archetype editor on the Ocean site with sample archetypes…a little more to do but it is getting very close. I would appreciate testing and comments back via the reporting menu item on the editor.

Cheers, Sam

2

Hi Sam,

I’ve been looking at the openEHR archetype profile specification and I can see that for the C_DV_QUANTITY class the property attribute should be a data type called DV_CODED_TEXT. However, I haven’t seen the [terminology::code] representation of a coded text in the archetypes that are packed with the latest version of the archetype edtior on the Ocean site. Also, I haven’t found a version called 1.0 that you say, the latest I could find is 0.99.5b.

Instead of the [terminology::code] representation I have seen a string representation of the property e.g. “pressure”. I think it would be good if the properties are coded according to the openEHR support terminology (http://svn.openehr.org/specification/TAGS/Release-1.0/publishing/architecture/computable/terminology/terminology.html ) so that they become more language independent.

Hope you can give me some clarity in this issue.

Cheers,

Mattias

3

Mattias Forss wrote:

Hi Sam,

I've been looking at the openEHR archetype profile specification and I can see that for the C_DV_QUANTITY class the property attribute should be a data type called DV_CODED_TEXT. However, I haven't seen the [terminology::code] representation of a coded text in the archetypes that are packed with the latest version of the archetype edtior on the Ocean site. Also, I haven't found a version called 1.0 that you say, the latest I could find is 0.99.5b.

Instead of the [terminology::code] representation I have seen a string representation of the property e.g. "pressure". I think it would be good if the properties are coded according to the openEHR support terminology (http://svn.openehr.org/specification/TAGS/Release-1.0/publishing/architecture/computable/terminology/terminology.html) so that they become more language independent.

you are indeed correct Mattias - these properties have to be fixed...

- thomas beale

4

This will be fixed before we release 1.0 candidate editor, Sam

Thomas Beale wrote: