Adl 2 support in Archetype Designer?

Tool Support Archetype Designer
1

Hi,

This message suggests that archetype designer supports adl2: Export Template in ADL2 format - #29 by borut.fabjan

I cannot find that dropbox that allows selecting the adl version anymore. The menu at the top of the screen has fewer items too (CDR, Libraries do not exist in the UI I’m looking at). I created a brand new github account , wired that to AD, no luck.

I could only make this work by exporting a template as adls, then importing it back into the repo, but then I’m left with the mystery of attempting to produce an opt (based on 2.X).

As you can see, I’m a bit lost here. Could clinical modelling practitioners give me a helping help here? What’s the state of ADL 2.X support in AD? How do you do things, what things you’re doing ? :slight_smile:

2

ADL2 is only supported for archetypes, not templates, although the ‘native json’ format is pretty close to an adls for templates - uses overlays etc.

1 Like
3

Thanks @ian.mcnicoll , supported how is my question I guess :slight_smile: Do I need to do export as adls, import again ritual? The screenshot that was shared in that message has adl2 as an option, that’s gone now apparently.

4

Are you sure? I’m pretty sure I’ve managed to create templates in ADL2, and exporting them using ADL2. They don’t use ADL2 as the expression language though, which I now realise may be what you meant?

  • .t.json: "adlVersion": "2.0.6",
  • .opt: <archetype rm_release="1.1.0" is_generated="true" is_differential="false" adl_version="2.0.6" xmlns:ns2="``http://schemas.openehr.org/v1``">
2 Likes
5

I asked @pieterbos (the ADL2 expert!) to look at 'Better’s native.json, and he says that although it is close to official ADL2 (in json format) it is not valid. I think @borut.fabjan told us this was because there were a few issues in ADL2 at that time which made it difficult to follow 100%. I suspect (hope) those gaps are now closed, so it would be really helpful to have a formal ADL2 template export now.

2 Likes
6

So my understanding is that even though the topic was about exporting ADL2 templates, the screenshot that @borut.fabjan posted relates only to creating a new ADL2 archetype, not a template.

ADL2 is just not supported for templates AFAIK, neither .adlt or .opt2

7

Thanks @siljelb I’m properly confused now :slight_smile: How did you get to that .opt file?

I do export to .adls → import for an archetype, then I have an adl2 archetype. I cannot create a temlate from that though, because new template dialog only recognises adl1.4 archetypes.

If I export the adls (adl 2.x) archetype as an opt, the output does not have the adl_version.. you have. Neither does the file set export.

8

that’s not possible anymore though, which was part of my question. The topic is about what is actually possible in the tool at the moment because I’m having difficulty figuring that out.

9

image
image1221×634 26.8 KB

10

I stand completly corrected :smiling_face: . Never, ever noticed!

11

@siljelb this is what I have. Having a real what the heck moment here:

image
image903×476 16.7 KB

My Root Archetype Id dropdown won’t display any .adls files either. I’m using Archetype Designer (just to check)

12

Do you have this?

image
image1222×1189 63.8 KB

4 Likes
13

and the .opt that is generated does indeed look like .opt2.

What is missing as an export is ADLT i.e the diff equivalent of .oet, though we know that ‘nativ’e is close.

14

of course not! Thanks a million @siljelb .

For anyone else ending up here: click on your user name on the top right, click on settings, then enable adl2 support.

Then you’ll have adl version appearing at various steps during your use.

4 Likes
15

Thank you @Seref and @siljelb ! And Better too! I have a renewed hope of OPT2 :blush:

The exported OPT is XML not ADL2. Did you mean that OPT XML looks like OPT2 ADL?

16

This was quite a while ago. I did a quick check in the current version. With the instructions provided by Silje it exports ADL 2 archetypes. I have not checked how well it works, especially with specialization.

It does not export ADL source templates, or ADL OPT files. But it does export a json serialization of an ADL 2 template (equivalent to OET, not OPT). If this format and the contents are correct, you can generate ADL 2 in template or OPT format using Archie, with the archetypes and template as input. I have not tested that. You need to write some kind of script, because the visual studio code extension does not currently parse this json format.

It also exports an OPT xml file that looks a bit like ADL 2 OPT, but with some oddities, such as mixed naming styles: <componentTerminologies/> , but <term_definitions , for example. Note the difference between the capital T and the _d. This would at least require a custom parser, some preprocessor or some adaptations to an existing one to parse.

3 Likes