# Annotations in ADL1.4-\>2

**URL:** <https://discourse.openehr.org/t/annotations-in-adl1-4-2/6165>\
**Category:** ADL\
**Tags:** archetype, template\
**Created:** [13 January 2025 14:34 UTC](https://discourse.openehr.org/t/annotations-in-adl1-4-2/6165 "2025-01-13T14:34:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [13 January 2025 14:34 UTC](https://discourse.openehr.org/t/annotations-in-adl1-4-2/6165/1 "2025-01-13T14:34:34Z")

</div>

At the last SEC meeting, I raised some issues about Annotations that I’ve tried pull together at this [Confluence page](https://openehr.atlassian.net/wiki/spaces/spec/pages/2728755245/ADL1.4+2+Annotations)

There are some potential non-breaking changes to ADL/AOM documentation and potentially spec but they relate only to tooling, and not to CDRs, However they are causing issues for clinical modelling esp loss of support for multi-lingual annotations, which is problematic for some PROMS scores.

There are probably some easy-ish tooling / .opt / web template generation fixes in the short term.

@borut.fabjan @sebastian.garde @joostholslag @birger.haarbrandt

I have already put in a CR for web template multi-lingual annotation handling.

Comments welcome.

---

<div class="post-metadata">

**Author:** ![yampeku](https://discourse.openehr.org/user_avatar/discourse.openehr.org/yampeku/32/25_2.png) [@yampeku](https://discourse.openehr.org/u/yampeku)\
**Post date:** [13 January 2025 14:49 UTC](https://discourse.openehr.org/t/annotations-in-adl1-4-2/6165/2 "2025-01-13T14:49:55Z")

</div>

It’s a pity I couldn’t attend to last SEC meeting, thanks for the clear summary. We are experiencing these tooling issues in CatSalut project

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [13 January 2025 14:54 UTC](https://discourse.openehr.org/t/annotations-in-adl1-4-2/6165/3 "2025-01-13T14:54:30Z")

</div>

I now realise that some of the design decisions in AD’s way of handling annotations in .opt is a consequence of trying to move to ADL2 path-based annotations but in doing so, running into 14 opt constraints.

The changes in AD that I think would fix this and give a more tolerable transition path are

1. Retain terminology-based annotations in .opt1.4 (remove in .opt2)
2. Support multilingual annotations in web templates

I don’t think either have an immediate impact on CKM .opt generation