**Author:** [@henrydwright](https://discourse.openehr.org/u/henrydwright)\
**Replies:** 2\
**Last updated:** [8 June 2026 13:44 UTC](https://discourse.openehr.org/t/is-task-planning-proc-retired-or-not/16969 "2026-06-08T13:44:55Z")
It’s not visible on the specifications website, but I see parts of it in the archetype designer (the Better one) and this website says not openEHR Task Planning v BPMN - Woland's CatWoland's Cat. What’s the truth - is i…
---
## [AI support on specifications.openehr.org](https://discourse.openehr.org/t/ai-support-on-specifications-openehr-org/11967)
**Author:** [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Replies:** 5\
**Last updated:** [5 June 2026 13:31 UTC](https://discourse.openehr.org/t/ai-support-on-specifications-openehr-org/11967 "2026-06-05T13:31:08Z")
Hi all, Over the past weeks I’ve been working on a set of changes to specifications.openehr.org aimed at making the openEHR specifications easier for LLMs, AI assistants, and agent-based tools to read, cite, and reason …
---
## [Interpretation of mandatory ACTION.time when using current\_state instead of ism\_transition](https://discourse.openehr.org/t/interpretation-of-mandatory-action-time-when-using-current-state-instead-of-ism-transition/16911)
**Author:** [@jkrafft](https://discourse.openehr.org/u/jkrafft)\
**Replies:** 2\
**Last updated:** [1 June 2026 16:12 UTC](https://discourse.openehr.org/t/interpretation-of-mandatory-action-time-when-using-current-state-instead-of-ism-transition/16911 "2026-06-01T16:12:31Z")
I’m trying to better understand the relationship between the mandatory RM attribute ACTION.time and workflow/state modelling in openEHR. In the CKM, for the Procedure archetype, the RM attribute “Date and time Action ste…
---
## [Clarifying semantics of Value-set constrained types](https://discourse.openehr.org/t/clarifying-semantics-of-value-set-constrained-types/16830)
**Author:** [@Mohammad\_Zawahreh](https://discourse.openehr.org/u/Mohammad_Zawahreh)\
**Replies:** 1\
**Last updated:** [18 May 2026 12:21 UTC](https://discourse.openehr.org/t/clarifying-semantics-of-value-set-constrained-types/16830 "2026-05-18T12:21:02Z")
Hi everyone, I’ve got some questions regarding the semantics of Range-Constrained (Section 7.4). Specifically, when a type usage is qualified with a BMM\_VALUE\_SET\_SPEC (e.g., CodedText \<\\>), I’d like to c…
---
## [Attestation 'Request'](https://discourse.openehr.org/t/attestation-request/1391)
**Author:** [@VeraPrinsen](https://discourse.openehr.org/u/VeraPrinsen)\
**Replies:** 9\
**Last updated:** [12 May 2026 12:26 UTC](https://discourse.openehr.org/t/attestation-request/1391 "2026-05-12T12:26:46Z")
Hi! We are looking at using Attestations and have a question about the following: When an attestation is required, the most common scenario will be that a Composition Version will be committed with a commit\_audit of …
---
## [Looking ahead to openEHRv2](https://discourse.openehr.org/t/looking-ahead-to-openehrv2/11448)
**Author:** [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Replies:** 27\
**Last updated:** [11 May 2026 08:40 UTC](https://discourse.openehr.org/t/looking-ahead-to-openehrv2/11448 "2026-05-11T08:40:14Z")
There has been recent discussion touching on the question of what an openEHRv2 would look like, and whether breaking changes to the RM are worth the trouble. While in the US, I and my team (including @borut.jures , who …
---
## [Working for a new openEHR specifications website with Antora](https://discourse.openehr.org/t/working-for-a-new-openehr-specifications-website-with-antora/11694)
**Author:** [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Replies:** 2\
**Last updated:** [8 May 2026 08:22 UTC](https://discourse.openehr.org/t/working-for-a-new-openehr-specifications-website-with-antora/11694 "2026-05-08T08:22:04Z")
Hello everyone, I’d like to share an update on ongoing work on a new openEHR specification website, built and rendered using Antora. This effort has been a fairly complex one, the topic was discussed in SEC (Specificat…
---
## [Agreeing on optional user interface hints in templates](https://discourse.openehr.org/t/agreeing-on-optional-user-interface-hints-in-templates/2406)
**Author:** [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)\
**Replies:** 53\
**Last updated:** [29 April 2026 04:41 UTC](https://discourse.openehr.org/t/agreeing-on-optional-user-interface-hints-in-templates/2406 "2026-04-29T04:41:01Z")
In short: Let’s start experimenting with adding vendor neutral hints (e.g. in templates) that can help both automated user interface generators and “manual” form editors create forms with more logic. Details follow. Cur…
---
## [RM Mappings - DV\_CODED\_TEXT preferred\_term missing](https://discourse.openehr.org/t/rm-mappings-dv-coded-text-preferred-term-missing/11780)
**Author:** [@jbuch](https://discourse.openehr.org/u/jbuch)\
**Replies:** 8\
**Last updated:** [28 April 2026 11:22 UTC](https://discourse.openehr.org/t/rm-mappings-dv-coded-text-preferred-term-missing/11780 "2026-04-28T11:22:19Z")
When trying to POST a FLAT Composition on EHRBase, I noticed that I wasn’t able to save a DV\_CODED\_TEXT with a preferred\_term, and neither is it retained after saving it using a RAW/JSON Composition and then loaded in FL…
---
## [Simple-to-Generic type conformance](https://discourse.openehr.org/t/simple-to-generic-type-conformance/11940)
**Author:** [@Mohammad\_Zawahreh](https://discourse.openehr.org/u/Mohammad_Zawahreh)\
**Replies:** 12\
**Last updated:** [23 April 2026 13:25 UTC](https://discourse.openehr.org/t/simple-to-generic-type-conformance/11940 "2026-04-23T13:25:45Z")
Hi everyone, I came across type conformance in BMM. In simple type, rules for conformance of simple to simple are specified, but I could’t find the description for simple-to-generic conformance. for example Multiplicity…
---
## [Representing event timelines using the history package](https://discourse.openehr.org/t/representing-event-timelines-using-the-history-package/11876)
**Author:** [@paul.behrend](https://discourse.openehr.org/u/paul.behrend)\
**Replies:** 11\
**Last updated:** [2 April 2026 10:14 UTC](https://discourse.openehr.org/t/representing-event-timelines-using-the-history-package/11876 "2026-04-02T10:14:09Z")
I’m trying to represent a timeline of past states (values of some attribute with validity time spans) within a composition. The RM spec contains a section on the history package containing classes that I believe match th…
---
## [Missing attestation headers for the REST API](https://discourse.openehr.org/t/missing-attestation-headers-for-the-rest-api/5947)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\
**Replies:** 2\
**Last updated:** [21 March 2026 18:57 UTC](https://discourse.openehr.org/t/missing-attestation-headers-for-the-rest-api/5947 "2026-03-21T18:57:05Z")
I was reviewing the REST and common-change control specs, and found there is missing information about how to do an attestation through the REST API. For instance, a POST to …/composition needs some extra headers so the…
---
## [Questions regarding snomed CT-mapping](https://discourse.openehr.org/t/questions-regarding-snomed-ct-mapping/11767)
**Author:** [@OscarKarlsson](https://discourse.openehr.org/u/OscarKarlsson)\
**Replies:** 5\
**Last updated:** [12 March 2026 15:29 UTC](https://discourse.openehr.org/t/questions-regarding-snomed-ct-mapping/11767 "2026-03-12T15:29:12Z")
I am wondering how to handle mapping to SNOMED CT when importing data from a source system into our CDR. More specifically how and where to store: The original value from the source system The SNOMED CT code Potential…
---
## [time asserted already implemented in EVALUATION RM](https://discourse.openehr.org/t/time-asserted-already-implemented-in-evaluation-rm/11799)
**Author:** [@tarabonet](https://discourse.openehr.org/u/tarabonet)\
**Replies:** 7\
**Last updated:** [6 March 2026 20:16 UTC](https://discourse.openehr.org/t/time-asserted-already-implemented-in-evaluation-rm/11799 "2026-03-06T20:16:09Z")
Hi all, We have noticed that when persisting archetypes of type EVALUATION, there is an option to persist an attribute called ‘time asserted’. We know that some time ago there was a request to include this attribute as…
---
## [Allowing open name constraint to support formal FOLDER models, why not?](https://discourse.openehr.org/t/allowing-open-name-constraint-to-support-formal-folder-models-why-not/11804)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\
**Replies:** 4\
**Last updated:** [5 March 2026 18:14 UTC](https://discourse.openehr.org/t/allowing-open-name-constraint-to-support-formal-folder-models-why-not/11804 "2026-03-05T18:14:07Z")
Current modeling tools don’t allow to add constraints to the name field like we can add constraints to any other field on a LOCATABLE subclass. Names are special. Most of the time those just have an implicit constraint i…
---
## [Deprecated languages in openEHR external terminologies file](https://discourse.openehr.org/t/deprecated-languages-in-openehr-external-terminologies-file/11646)
**Author:** [@vanessap](https://discourse.openehr.org/u/vanessap)\
**Replies:** 14\
**Last updated:** [4 March 2026 09:37 UTC](https://discourse.openehr.org/t/deprecated-languages-in-openehr-external-terminologies-file/11646 "2026-03-04T09:37:29Z")
Hi! Over the last few weeks, I have been demonstrating how to create translations of Archetypes using the CKM and ADL Designer. In this case, the focus is on European Portuguese (pt-PT) and Brazilian Portuguese (pt-BR),…
---
## [Flat path «|other» missing in simplified format for DV\_CODED\_TEXT](https://discourse.openehr.org/t/flat-path-other-missing-in-simplified-format-for-dv-coded-text/11790)
**Author:** [@emmanuel.eschmann](https://discourse.openehr.org/u/emmanuel.eschmann)\
**Replies:** 1\
**Last updated:** [4 March 2026 09:29 UTC](https://discourse.openehr.org/t/flat-path-other-missing-in-simplified-format-for-dv-coded-text/11790 "2026-03-04T09:29:13Z")
The simplified format for DV\_CODED\_TEXT (see https://specifications.openehr.org/releases/ITS-REST/development/simplified\_formats.html#DV\_CODED\_TEXT) does not mention the flat path “|other”. However, some CDRs — for examp…
---
## [DV\_URI vs DV\_IDENTIFIER for non-locator URIs](https://discourse.openehr.org/t/dv-uri-vs-dv-identifier-for-non-locator-uris/11750)
**Author:** [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Replies:** 5\
**Last updated:** [17 February 2026 13:30 UTC](https://discourse.openehr.org/t/dv-uri-vs-dv-identifier-for-non-locator-uris/11750 "2026-02-17T13:30:53Z")
According to RFC 3986, a URI can be an identifier without having to also be a locator. Is this also the intent for the DV\_URI data type? If so, how does this mesh with DV\_IDENTIFIER?
---
## [REST API: DELETE /composition have response codes 409 Conflict though 412 Precondition Failed seems more appropriate](https://discourse.openehr.org/t/rest-api-delete-composition-have-response-codes-409-conflict-though-412-precondition-failed-seems-more-appropriate/11747)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\
**Replies:** 0\
**Last updated:** [10 February 2026 16:03 UTC](https://discourse.openehr.org/t/rest-api-delete-composition-have-response-codes-409-conflict-though-412-precondition-failed-seems-more-appropriate/11747 "2026-02-10T16:03:28Z")
Quick question: when the previous version of the object (e.g. COMPOSITION) is not the last, we have a 409 Conflict in the spec, though that doesn’t seems to be conflict but a precondition for the operation for deleting a…
---
## [Why does the Terminology id table has no version instead this Stringbuild logic](https://discourse.openehr.org/t/why-does-the-terminology-id-table-has-no-version-instead-this-stringbuild-logic/11707)
**Author:** [@SevKohler](https://discourse.openehr.org/u/SevKohler)\
**Replies:** 2\
**Last updated:** [29 January 2026 13:24 UTC](https://discourse.openehr.org/t/why-does-the-terminology-id-table-has-no-version-instead-this-stringbuild-logic/11707 "2026-01-29T13:24:48Z")
Shouldnt the RM have a dedicated version field also for query stability? SNOMED-CT (VERSION) is what is currently in the spec. That makes AQLs frankly quite annoying. Also SNOMED has modules and versions would be good…
---
## [Multilingual templates and templated value sets](https://discourse.openehr.org/t/multilingual-templates-and-templated-value-sets/4118)
**Author:** [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Replies:** 16\
**Last updated:** [27 January 2026 08:10 UTC](https://discourse.openehr.org/t/multilingual-templates-and-templated-value-sets/4118 "2026-01-27T08:10:53Z")
Hi all! When creating multilingual templates with templated value sets (ie value sets for text elements where the values are included in the template and not the archetype), it seems like there’s a limitation that preve…
---
## [What is a query on VERSION v returning ?](https://discourse.openehr.org/t/what-is-a-query-on-version-v-returning/11651)
**Author:** [@SevKohler](https://discourse.openehr.org/u/SevKohler)\
**Replies:** 19\
**Last updated:** [15 January 2026 10:04 UTC](https://discourse.openehr.org/t/what-is-a-query-on-version-v-returning/11651 "2026-01-15T10:04:40Z")
If no predicate for VERSION is used, are all versions or only the latest returned ? SELECT e/ehr\_id/value, v/commit\_audit/time\_committed/value from EHR e CONTAINS VERSION v CONTAINS COMPOSITION c ORDER BY vo/commit\_au…
---
## [Archetype 'comments'.](https://discourse.openehr.org/t/archetype-comments/11660)
**Author:** [@joostholslag](https://discourse.openehr.org/u/joostholslag)\
**Replies:** 2\
**Last updated:** [29 December 2025 14:25 UTC](https://discourse.openehr.org/t/archetype-comments/11660 "2025-12-29T14:25:57Z")
Archetypes can contain comments in different forms. Which is confusing. One is inline comments in a raw ADL, after a special character ‘–’which is ignored by most software tools. Archetype Definition Language 2 (ADL2) S…
---
## [Cloning repeatable elements or clusters in archetype specialisations?](https://discourse.openehr.org/t/cloning-repeatable-elements-or-clusters-in-archetype-specialisations/11616)
**Author:** [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Replies:** 13\
**Last updated:** [15 December 2025 10:26 UTC](https://discourse.openehr.org/t/cloning-repeatable-elements-or-clusters-in-archetype-specialisations/11616 "2025-12-15T10:26:20Z")
When modelling templates, a repeating element or cluster can be explicitly cloned and further constrained from the original archetype, like the way the “Atypical finding” cluster is cloned in this screenshot: This do…
---
## [Terse/compact serialisation of openEHR leaf nodes, like ECISFLAT values?](https://discourse.openehr.org/t/terse-compact-serialisation-of-openehr-leaf-nodes-like-ecisflat-values/11649)
**Author:** [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)\
**Replies:** 5\
**Last updated:** [11 December 2025 07:03 UTC](https://discourse.openehr.org/t/terse-compact-serialisation-of-openehr-leaf-nodes-like-ecisflat-values/11649 "2025-12-11T07:03:39Z")
Hi! The value encoding in the wonderfully ingenious (now possibly deprecated?) ECISFLAT format (likely created by @chevalleyc) is described in ethercis/doc/flat json.md at master · ethercis/ethercis · GitHub There is a…
---
## [Really good openEHR technical documentation (from FHIR)](https://discourse.openehr.org/t/really-good-openehr-technical-documentation-from-fhir/11622)
**Author:** [@pablo](https://discourse.openehr.org/u/pablo)\
**Replies:** 4\
**Last updated:** [3 December 2025 14:50 UTC](https://discourse.openehr.org/t/really-good-openehr-technical-documentation-from-fhir/11622 "2025-12-03T14:50:46Z")
Just check this page Artifacts Summary - OpenEHR Base package v0.1.0
---
## [normal\_status terminology missing description](https://discourse.openehr.org/t/normal-status-terminology-missing-description/11623)
**Author:** [@SevKohler](https://discourse.openehr.org/u/SevKohler)\
**Replies:** 5\
**Last updated:** [1 December 2025 13:17 UTC](https://discourse.openehr.org/t/normal-status-terminology-missing-description/11623 "2025-12-01T13:17:13Z")
Hey, the HL7 specification linked contains only H and HH. Our spec does not explain what these values mean. If yes where are these values meaning documented ?
---
## [Storing and reading attestations](https://discourse.openehr.org/t/storing-and-reading-attestations/11559)
**Author:** [@emmanuel.eschmann](https://discourse.openehr.org/u/emmanuel.eschmann)\
**Replies:** 6\
**Last updated:** [27 November 2025 18:28 UTC](https://discourse.openehr.org/t/storing-and-reading-attestations/11559 "2025-11-27T18:28:21Z")
We want healthcare personnel to be able to sign reports, approve prescriptions or acknowledge laboratory results. Attestations seem to us to be a suitable way of recording this signing ( Common Information Model ; Common…
---
## [The good, the bad and the "Wat?" of current simplified FLAT/SimSDT openEHR exchange format](https://discourse.openehr.org/t/the-good-the-bad-and-the-wat-of-current-simplified-flat-simsdt-openehr-exchange-format/3819)
**Author:** [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)\
**Replies:** 45\
**Last updated:** [26 November 2025 18:42 UTC](https://discourse.openehr.org/t/the-good-the-bad-and-the-wat-of-current-simplified-flat-simsdt-openehr-exchange-format/3819 "2025-11-26T18:42:55Z")
Hi! At Karolinska we are a bit confused about how to format/use some things in different forms of the FLAT/SimSDT format. We are testing at least three CDR products that are supposed to support it and at least two (non-…
---
## [Element not allowed units\_system in element list](https://discourse.openehr.org/t/element-not-allowed-units-system-in-element-list/11467)
**Author:** [@Yasitha\_Thilantha](https://discourse.openehr.org/u/Yasitha_Thilantha)\
**Replies:** 9\
**Last updated:** [10 November 2025 12:23 UTC](https://discourse.openehr.org/t/element-not-allowed-units-system-in-element-list/11467 "2025-11-10T12:23:23Z")
I created an archetype with the RM type C\_DV\_QUANTITY using the Better Archetype Designer tool. Then I created a template based on the above archetype and tried to validate it using the ehrbase-openehr-sdk Java library.…
[Previous page](https://discourse.openehr.org/c/specifications/6.md)
[Next page](https://discourse.openehr.org/c/specifications/6.md?page=2)