ART-DECOR® – Release 3.10.4
Release notes 30 October 2026
Introduction
We are happy to announce ART-DECOR® Release 3.10.4. This maintenance and enhancement release completes the work started in 3.10.3 and addresses a total of 15 resolved tickets. These consist of new features, improvements, and bug fixes across the platform.
The highlights of this release are:
- Rich text box support added to the text editor throughout the application
- Local names for dataset containments and inherits (Phase 2)
- Implementation Guide post-processing and publication workflow (frontend)
- Full write support for Obligations and Additional Bindings (frontend)
- Questionnaire creation for transactions without a Transaction Building Block
- ConceptMap list correctly populated for project releases
- FHIR StructureDefinition / shortName cardinality error resolved
- CodeSystem properties now rendered in FHIR R4 RetrieveCodeSystem
- Template editor conformance/cardinality alignment with transaction editor
- Missing descriptions in scenarios.html publication output corrected
- Wrong link to SNOMED CT terminology reference set list corrected
- Dutch translations for SHALL/SHOULD improved in obligation rendering
- Next Generation Publishing: local download links instead of live server calls
NOTE
Release 3.10.4 is a cumulative update and fully replaces 3.10.3. Existing installations should upgrade directly to this version.
Text Editor
Box feature (AD30-2296): The rich text editor used throughout the application now supports a box (panel) element. Authors can surround a block of text with a styled box to visually highlight notes, warnings, or other call-out content inside descriptions, definitions, and similar free-form fields. The feature is available in every part of the application that uses the shared text editor component.
Implementation Guide Publication
Publication workflow (AD30-2305): The frontend now exposes a full post-processing and publication workflow for Implementation Guides. After drafting an IG, editors can initiate the publication step directly from the interface without having to resort to manual backend operations. This closes the authoring cycle for IG production and aligns it with the existing publication workflow for other artefact types.
Next Generation Publishing
Local download links (AD30-2334): The Next Generation Publishing pipeline previously generated download links that called the live server at request time rather than resolving to locally stored files inside the publication package. This created a dependency on the originating server remaining reachable after publication. The pipeline now emits local links so that a publication package is self-contained and can be served from any host without broken downloads.
The Next Generation Publishing pipeline will officially released with 3.11.
Questionnaires
Questionnaire for transaction without TBB (AD30-2396): It is now possible to create a questionnaire for a transaction that does not use a Transaction Building Block (TBB). Previously, the questionnaire creation flow required a TBB to be present. Removing this prerequisite allows projects that model transactions without a TBB to benefit from the questionnaire feature.
Obligations
Write support (AD30-2416): Obligations can now be written – not just read – from the frontend. The obligation authoring panel allows editors to add, modify, and remove obligations on elements directly within the browser. This brings the obligation workflow to parity with the existing read display that was introduced in an earlier release. The backend already supported the obligation data model; this release closes the frontend gap.
Additional Bindings
Write support (AD30-2418): Additional bindings can now be authored and saved from the frontend. The scenario and transaction panel shows the origin of each binding (dataset vs. transaction level) so that editors can distinguish inherited associations from locally created ones. Alongside the write capability, several API-level issues encountered during testing were resolved, including incorrect concept ID construction in the PATCH call body and a spurious DECOR check warning on TBB concepts that carry a terminology association.
Dataset Containments – Local Names (Phase 2)
Local name for contains and inherit (AD30-2434, AD30-2633): Building on the Phase 1 groundwork (AD30-2423), editors can now assign a local display name to a contains or inherit reference in the dataset editor. The local name overrides the target concept's name in the tree and in the concept header without modifying the referenced concept itself. Names are per-language: a language without a local name continues to show the target's name and follows it if the target is ever renamed. Clearing a language removes its local name. The backend PATCH endpoint was extended to accept multi-language local name arrays and to handle zero-entry payloads as a remove operation. DECOR check was correspondingly extended to flag datasets where only some language variants carry a local name.
Figure 1: Example of a dataset (drawn from the xt-EHR specifications for the EHDS) with local names for references to other datasets and data elements.

Bug Fixes
Template Editor – Conformance and Cardinality
Conformance rules aligned with transaction editor (AD30-2549): The template editor now enforces the same conformance and cardinality rules as the transaction editor. The conformance value O (Optional) has been removed from the template editor's dropdown because it was silently rewriting the cardinality to 0..1, which is not the intended behaviour. The conformance value NP no longer rewrites the cardinality. The combination of conformance C with isMandatory=true is now rejected; setting a concept to M stores isMandatory=true without a conformance attribute, matching the transaction editor behaviour. Invalid pairings are surfaced in the editor UI before the save is attempted.
Publication – Missing Scenario Descriptions
Scenario descriptions restored (AD30-2554): Scenario descriptions were missing from scenarios.html in a number of recent Nictiz publications (mp-, hg-, e-overdracht-). The root cause was a missing shortName handling that affected 15 output locations across the publication XSL stylesheets. The fix restores the descriptions in all affected locations. Because the fix is backward-compatible, republication of existing releases is not required, but new publications will include the descriptions.
ConceptMap List for Releases
ConceptMap list fixed for versioned releases (AD30-2614): Calling ProjectIndex or ConceptMapIndex with a release version filter returned an empty ConceptMap section even when ConceptMaps existed in the compiled publication. The fix ensures that the index services correctly locate and return ConceptMaps for versioned project releases. On the decor.nictiz.nl server the affected cached index pages were invalidated and re-warmed after the fix was applied.
FHIR
StructureDefinition shortName cardinality error (AD30-2617): Requesting a StructureDefinition in JSON or XML format for certain transactions failed with a 500 Internal Server Error caused by the utillib:shortName function receiving more arguments than its signature permits (cardinality zero-or-one, got three). The function call site was corrected to pass a single node, and the fix was applied directly to the exist-db-5 branch and to the acceptance server.
CodeSystem properties not rendered in RetrieveCodeSystem (AD30-2624): CodeSystem properties defined on a CodeSystem were not rendered in the RetrieveCodeSystem FHIR R4 response. An XPath type error in the FHIR 4 API – caused by a boolean value being used where a node set was expected – prevented the properties section from being populated. The fix was applied to the FHIR R4 API server module.
CodeSystem Editor
Editor display issue (AD30-2623): The CodeSystem editor occasionally opened to a half-white page with the content shifted below the visible area and the scrollbar non-functional. The issue was intermittent and could not be reproduced consistently after a frontend update was applied on acceptance. It is marked done on the basis that it was no longer reproducible on the current build.
Terminology Browser
Wrong link to SNOMED CT reference set list (AD30-2628): The terminology browser contained an outdated link to the Nictiz SNOMED CT reference set list (terminologie.nictiz.nl/art-decor/snomed-ct). The link has been updated to the current location. The fix was reported by Pim Volkert of DHD.
Dutch Translations for SHALL/SHOULD
Obligation strength labels corrected (AD30-2631): The Dutch rendering of obligation strength values was incorrect: SHOULD was translated as MOETEN, which corresponds to SHALL rather than SHOULD. The translation has been corrected to ZOUDEN MOETEN for SHOULD, making the obligation descriptions accurate in Dutch-language publications. The fix is in the DECOR core translation layer.
Infrastructure and Release
With the completion of the last backend feature branch (AD30-2434), all backend work for release 3.10.4 has been merged into exist-db-5. The backend has been built as a 3.10.4 release package and published to the stable3 repository. The frontend release branch has been merged into master. An acceptance test pass (AD30-2626) verified the combined frontend and backend against the regression test suite. Release notes are tracked under AD30-2625.
Hints for Updating an ART-DECOR® Release for local installations
For all our hosted servers we do planned and announced updates of the server software regarding backend and frontend, comprised of ART-DECOR Vue and ART-DECOR http-proxy.
For cliens that run their own installations, this section includes hints for upgrading your installation.
npm build vulnerabilities (AD30-2454): Critical security vulnerabilities in axios (< 1.15.1) and 10 high-severity module vulnerabilities have been resolved by updating dependencies in both the art-decor and http-proxy packages. For clients that running the vue frontend, please update to our newest vue frontend version.
XSLT Saxon compilation failure (AD30-2421): A critical bug in Saxon 9 caused XSLT transformations to fail with UnsupportedOperationException: Cannot enumerate an infinite set during stylesheet compilation. This affected all sites using Saxon < 12.0, including ADRAM. The recommended fix is to upgrade ADRAM and/or ADAWIB which include the upgraded version Saxon-HE 12.9. Only clients that are running ADRAM, or ADAWIB are effected by this change.
Please Note
When you have a local installation of ART-DECOR and want to update to this release, please consider reading our Updating an ART-DECOR® Release documentation.
Thank you
A BIG thank you!
We are always thankful for any comments and suggestions.
Special thanks for the feedback regarding the Template Viewer and Editor to the colleagues from ELGA (Austria) and HL7 Italy / Ernst&Young (EY) and for Dataset and Questionnaire editor to the Berlin Institute of Health @ Charité team.
Especially in the terminology and questionnaire sector we got great feedback from the Dutch ICT Institute in Health Care (Nictiz). Thanks to Gunter Haroske working for the Deutsche Gesellschaft für Pathologie / German Association of Pathology pointing to shortcomings and missing features in our Questionnaire functions and to the Dutch Uitkomstgerichte Zorg Program for contributions in the same area.
Special thanks also to the mio42 GmbH team, Agence du Numérique en Santé (ANS) and our partners at Kereval / IHE Europe for testing, feature suggestions and bug fix requests.
Please don't hesitate to write us with suggestions for improvements or feature requests to our email address provided for this purpose: feedback@art-decor.org, also easily reachable through the Services Card at our ART-DECOR landing page (the link with the bulb 😃).

Outlook
Current development is heading towards Release 3.10.5 as well as towards 3.11 which focuses on further enhancements and features for Questionnaire Management, including score calculation support. We plan to have intermediate minor releases to tackle remaining improvements appropriately but stepwise. We are also working hard on our new FHIR Profile Editor utilizing FHIR Shorthand (FSH).
At the same time we are currently also working on the ART-DECOR Release 4 series. This will imply a big update on the frontend as we switch to Vue 3.
As you can see: more on that to come. Thank you for your patience. Stay tuned.
