2025-08-18 SEC Call notes

2025-08-18 SEC Call notes

Date

Jul 21, 2025

Call Link

Discourse SEC calls

Participants

  • @Sebastian Iancu

  • @Ian McNicoll

  • @Birger Haarbrandt

  • @Seref Arikan

  • @Sebastian Garde

  • @Erik Sundvall

  • @Shinji Kobayashi

  • @Mattijs Kuhlmann

  • @Alex Vidrean

  • @Pablo Pazos

  • @Joost Holslag

Goals

Discussion topics

 

Item

Presenter / Suggested by

Issue

Notes

 

Item

Presenter / Suggested by

Issue

Notes

Main Agenda

10 min

Opening,

Various aspects

ALL

SEC Jira board.

  • SEC meeting face2face 2025, Barcelona in Oct 16-17, 15 full-day for SEC meeting?

  • “Adopt your ticket”

 

 

 

TEMPLATE_ID

 

 

 

All

Idea of OpenEHR Labs proposed by TB

  • @Ian McNicoll there is value in some aspects of the proposal, however there might be issue on to label “openEHR” without making it responsibility of SEC

  • @Erik Sundvall WG is partially already facilitating that workspace; external persons can jon WG.

  • @Sebastian Iancu concerns about consistency between various specification

  • @Birger Haarbrandt it should be clear what would be official SEC specification and what is Lab, so that consumers are not confused or mislead

  • @Pablo Pazos what happens when there are not enough members for a WG?

  • @Seref Arikan we will have to think about when can we state that a specification should be label as openEHR

  • @Erik Sundvall we have to think about how to foster innovation, and not block great ideas by majority

  • @Seref Arikan yes, lets innovate, but keep short feedback loops

  • @Birger Haarbrandt if we look to how Severin managed to develop the FHIRConnect specification, then we can conclude that is possible to work on new specification, have the community adopting it, without having the need put it in the Lab

  • The issue regarding restarting task planning is deferred to CDS WG to be analyzed and prioritized first

 

Governanace

@Severin Kohler

Propose to add branch policies on github, add PullRequest requirements

  • @Joost Holslag the PR should have one reviewer instead of two

 

BMM

@Sebastian Iancu

  • YAML looks a much more suitable format for edit

 

 

 

 

 

 

 

 

 

 

 

Action items

start discourse page then meeting for packaging @Sebastian Iancu