2025-10-14 SEC Face2face Meeting Barcelona

• @Sebastian Iancu

• @Rong Chen

• @Thomas Beale (15th only)

• @Sebastian Garde

• @Bostjan Lah

• @Matija Polajnar

• @Severin Kohler (15th only)

• @Seref Arikan

• @Ian McNicoll

• @Diego Bosca

• @Mattijs Kuhlmann

• @Jelte Zeilstra

• @Erik Sundvall

• @Joost Holslag

@Borut Jures

Oct 14, 2025

Opening & Agenda

ALL

• SEC Jira board.

• New members / Resignations

• https://docs.google.com/spreadsheets/d/1T8uyOLEWgewofNMy0jNbFmYLb-nRSNNt/edit?gid=2110295167#gid=2110295167

• On the question of openEHR Foundation Board on advise on re-license the Paused specifications, the SEC recommends CC-BY; there are no concerns about future impact on a potential fork of openEHR specifications. https://creativecommons.org/licenses/by/4.0/

• No suggestions for new members or resignations yet.

• Suggestion to change/amend the SEC-ToR to suggest to SEC (voting) members that are inactive for more then 6 months to invite them to become SEC Experts thus without voting rights, or to resign.

• added one more risk on risk register - see no. 38

• suggestion (S.A.) “The outcomes of the activities of a WG may result in additions to openEHR specifications, subject to the explicit approval of SEC.”

AQL WG

@Sebastian Iancu

• Federated AQL Proposal

• (re)Start WG in Nov/Dec 2025

reviewing Fed AQL proposal:

• concerns about loosing portability of AQLs if we add the endpoint aware aspects (ENDPOINT)

• suggestion to consider http/rest layer instead of extra lexer additions to AQL; also if added it needs to be supported by the RM (what is an endpoint?), but that is not quite possible

• access control is out of scope, even though this is about fed-spec

• need more info about the problem that this Fed-AQL is solving; as well as use-case

• agreement that:

  • high-level scope

  • AQL syntax should remain unchanged

  • resultset should include endpoint metadata; extra column with endpoint_id may/should be included by the fed-layer

  • the REST layer can capture options to limit the endpoints via header params (so instead of AQL lexer we should use http-headers

  • adopt current proposal as development

• feedback should be given to the Fed-AQL (task @Sebastian Iancu), and discuss follow up steps

AQL WG (re)start:

• semantic of AQL

• bugs

• links and references

Suggestion to read/investigate GQL
(ISO/IEC 39075:2024 - Information technology — Database languages — GQL)

(Graph Query Language GQL)

Noted use cases

Federated queries to include endpoints node_ids

1. Use case 1: instead of querying the whole region

2. Use case 2: diff quality, templates 

3. Use case 3: GP, oncology etc

4. Use case 4: single patient, or group, Erik: take ideas from messaging systems

5. paring rules, patient data from which endpoint cdr

6. Works in single node or federated environment

7. Different nodes returning different resultsets

8. keep these outside queries, for federated systems the result needs to include extra information about nodes

CDS WG

@Rong Chen

• CDS WG progress report, aim to vote on GDL 2.1 changes

(started at 15:45)

Presentation about:

• upcoming GDL 2.1

• REST API CDS

• long term plan for GDL/CDS/PRO order-sets

Break

REST WG

@Sebastian Iancu

• status on upcoming Release 1.1.0

• SMART as TRIAL

• cleanup Simplified DT

• decouple from SM

• https://discourse.openehr.org/t/element-not-allowed-units-system-in-element-list/11467

moved to Oct 15, 2025

• presented current status

• aim to release 1.1.0 nov-dec 2025

• SDT at least TRAIL, SMART to TRIAL

• move ITS page instead of ITS component; retire the ITS component

• need to update also the XML schema, as well as JSON schema, potentially let it be generated by BMM

Term

@Severin Kohler

https://github.com/SevKohler/Terminologies

moved to Oct 15, 2025

• need to add more background info and details on the table

• suggest to add it to the TERM component specifications

• @Erik Sundvall template uris

• ADL2 requires URLs in term_bindings - that’s not aligned with this specs; suggestion is to change ADL2, @Jelte Zeilstra @Severin Kohler will make proposal for that

ADL WG

ADL2.4, RM 1.2, BASE 1.3

moved to Oct 15, 2025

• adopt new format (HRID) in template_id specs; need to update REST API

• changes to RM and BASE specs to align it with AM 2.4 requirements

• MagicDraw license is not available anymore, we will have to

Ending

Oct 15, 2025

BMM

@Sebastian Iancu

BMM v3? LANG v?

• not discussed

Website

@Sebastian Iancu

• Asciidoc → Antora, UML → BMM

• Paused specs

• The SEC is ok with Antora style of sections becoming pages

• Old URL should be supported via routing or landing pages

• PDFs will not be supported for now

REST

@Severin Kohler

EHDS the openEHR extracts and import export in general

• need to demonstrate that openEHR can have EHR extracts “compatible” with EHDS

• will review in a WG lead by @Severin Kohler if the EHR_Extract in RM is sufficient to support such extracts; then we’ll propose required changes to REST WG and to the SEC (in relation with RM changes) to support this functionality

@Ian McNicoll

Update on Encounter/ Episode of Care
Query over Links/References

not discussed

Break

@Ian McNicoll @Joost Holslag

‘DOSSIER' object (EHR without being patient-centric) from Public Health requirements

not discussed

dependencies

todo: package and rm dependenciess specifications

not discussed

Lunch

CPB & SEC joint meeting