2024-09-16 SEC Call notes

10 min

Opening,

Various aspects

ALL

SEC Jira board.

• Conference UK Nov 2024 Connectathon

• SEC Expert - Renaud Subigre

• Risk register

• “Adopt your ticket”

• emails @openehr.org

• ok to remove all old mail forwards of specifications@openehr.org

15 min

Specifications Website

@Sebastian Iancu

• Direct links on first page?? @Ian McNicoll

  • suggestion to show an overview (of release) baseline on the first page and cut down the text to minimal

• UML / BMM / asciidoctor specs

• the release baseline should be on the first page

• “if you are a developer, please don’t build your own platform”

• better add a FAQ section (@Seref Arikan) todo @Sebastian Iancu create a FAQ wiki

• Eclipse Modeling Project | The Eclipse Foundation

• need experiments with BMMs in yaml

• SEC group agrees to explore BMM as the single source of truth for openEHR specs

• that also means that Archie becomes more important in the future (as it will be used in various workflow stages)

15 min

Clinical PR

@Ian McNicoll

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

• need more input from modelers/use-case on what to store under other_details

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

• This is only on DV_SCALE

• a data value without a value is a somehow invalid datapoint

• suggestion to consider if changing the type of the DV_SCALE.value from Real to String (so that the key can be used)

• suggestion to modelers to consider to use DV_CODED_TEXT in such situation (when a DV_SCALE has no value, perhaps a set of DV_CODED_TEXT sounds more appropriate) - but this will not work for situation where values are used multiple times

• not discussed too much, need more feedback

• @Sebastian Garde

  • cannot turn the value to String, rather make the value optional

  • consider deprecating DV_ORDINAL class ?

    • it might have huge impact in the future on data instances, and smaller impact on models

AQL WG

• sharable AQLs

• Subject Proxy Population querying - Subject Proxies in AQL

• undocumented functionalities

• new features/formalisms (views, graphQL, etc)

•  

• sharable AQL

  • needs experiments inside REST API WG

  • CKM has a basic support to publish them

  • Better has a way to refer to them in their app-set export

  • @Joost Holslag Resource Model  
    There’s a spec for I think what we might want. 
    I think stored AQL should be ‘authored resources’. Maybe ‘authored query’ like there’s ‘authored archetype’ adds value?

  • @Diego Bosca is this related to the "packages" we discussed some time ago?

•  

OPT 1.4

@Sebastian Iancu

(XSD) Schema not uptodate

• not discussed