2025-04-28 SEC Call notes

Date

Mar 31, 2025

Call Link

Discourse SEC calls

Participants

  • @Borut Jures

  • @Sebastian Garde

  • @Seref Arikan

  • @Joost Holslag

  • @Ian McNicoll

  • @Shinji Kobayashi

  • @Erik Sundvall

  • @Bostjan Lah

  • @Rong Chen

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ā€

  • @Rong Chen CDS WG update

    • settled for Tuesday afternoon for bi-weekly meeting

    • ongoing work on REST APIs for definition/execution of GDL2 guidelines

    • scope:

      • short-term: GDL2.1, rest api for GDL

      • long-term: machine learning, care plans, task generation, personalized care plan

Ā 

Ā 

@Sebastian Iancu

info:

todo:

  • AUTHORED_RESOURCE for templates, FHIR connect (mappings), queries, guidelines

  • Not yet used in the definition API

  • original language is a mandatory attribute

  • Rong/Joost organize related issues for next call

  • Common already supported by tooling (CKM/template designer), better to be a formal attribute (reserved name)

    • Ian to raise CR on this

  • Ian to raise PR to work on the language support for annotations

Ā 

Archived spec status

@Sebastian Iancu

New "Paused" Specification Lifecycle State

  • agree with Paused, need more acceptance on the wiki-page

  • what happened to license after specs paused

  • from SEC to international board to suggest the license change, allowing cloning/forking with creative commons condition without openEHR label (Rong to draft something on this)

Ā 

Ā 

Ā 

@Severin Kohler

INTG component

  • recommend to use AUTHORED_RESOURCE

Ā 

Term Binding strengt

@Ian McNicoll

https://openehr.atlassian.net/browse/SPECPR-439

  • the question is if we want to proceed on this ticket with CRs

    • the SEC agrees that it makes sense to analyze this and come up with CR proposals

    • todo: SEC members should comment on the tickets

    • @Borut Jures there is a ā€˜value_constraint’ field for this in BMM, e.g.

      • ["Multimedia"] = < name = <"Multimedia"> ancestors = <"Encapsulated"> properties = < ["alternate_text"] = (P_BMM_SINGLE_PROPERTY) < name = <"alternate_text"> type = <"String"> > ["data"] = (P_BMM_CONTAINER_PROPERTY) < name = <"data"> type_def = < container_type = <"Array"> type = <"Byte"> > cardinality = <|>=0|> > ["media_type"] = (P_BMM_SINGLE_PROPERTY) < name = <"media_type"> type_ref = < type = <"Terminology_code"> value_constraint = <"iana_media-types"> > is_mandatory = <True> >

  • @Ian McNicoll suggestion to relax RM invariants, except for strength is ā€œrequiredā€

  • Ian to create PR on this

Ā 

YAML

@Matija Polajnar @Sebastian Iancu

https://discourse.openehr.org/t/yaml-canonical-compositions/6606

https://discourse.openehr.org/t/bmm-as-yaml/5721

Archetypes in YAML

YAML for data instances, no need to continue on this topic.
No point to progress on BMM/YAML discussion.

Ā 

Conformance testing?

Ian’s update on postman tests

Ā 

Ā 

Ā 

Action items

start discourse page then meeting for packaging @Sebastian Iancu

Ā 

Ā 

Ā 

Looking for labels? They can now be found in the details panel on the floating action bar.

Related content