2025-03-03 SEC Call notes

10 min

Opening,

Various aspects

ALL

SEC Jira board.

• SEC meeting face2face 2025

• “Adopt your ticket”

•  

@Sebastian Iancu @Joost Holslag

• https://openehr.atlassian.net/browse/SPECTERM-30

• https://openehr.atlassian.net/browse/SPECBASE-39

• https://openehr.atlassian.net/browse/SPECPR-422

• https://openehr.atlassian.net/browse/SPECPR-449

• https://openehr.atlassian.net/browse/SPECAM-90

• todo: https://openehr.atlassian.net/browse/SPECBASE-35

• see https://discourse.openehr.org/t/upcoming-base-1-3-0/6139

• todo: the ADL_CODE_DEFINITION should accept both id-code and at-code values Archetype Object Model 2 (AOM2)

ADL2

@Ian McNicoll

Archetype Definition Language 2 (ADL2)

• @Ian McNicoll todo check conversion algorithm from ADL1.4 to ADL2

• question where do we put multi-languages vs uni-language annotation.

• todo: suggest RESOURCE_ANNOTATION.documentation hash key should support '*' as language agnostic annotation

  todo: a new SPECAM for

  1. Add comment attribute in ARCHETYPE_TERM as formal attribute Archetype Object Model 2 (AOM2)

  2. ADL1.4→2 Annotations

@Mattijs Kuhlmann a better solution would be a whole different section rather then *

@Ian McNicoll the documentation is multi-lingual (this needs to be explained in specs) and for technical we should add a new attribute to Resource Model

technical: Hash<String, Hash<String, String>>

Archived spec status

@Sebastian Iancu

archived rather then retired

see previous meeting notes

https://discourse.openehr.org/t/task-planning-specs/6154

New "Paused" Specification Lifecycle State

todo:

• update doc with feedback; consider “Paused”

• move main website info about change process to specification website

CDS WG

@Rong Chen

• Rong presented plans for the WG

• maintenance and new work

• meet twice a month

Template name/id in RM

@Birger Haarbrandt

@Severin Kohler

• @Ian McNicoll we add v1 to template-name, and v1-alpha in case of development

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> >