2024-12-09 SEC Call notes

10 min

Opening,

Various aspects

ALL

SEC Jira board.

• Conference UK Nov 2024 Connectathon

• Risk register

• “Adopt your ticket”

•  

@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

• proposal to revert to lifecycle_state to string, how it was in ADL/AOM 1.4

• https://github.com/openEHR/archie/blob/eb7b43d90cc480d83aadb2c91665e88d52df1f42/bmm/src/test/resources/openehr/openEHR_aom_206.bmm#L564

@Joost Holslag

DV_ORDINAL

• with just a symbol

  • suggestion from clinical group to make the value optional field

  • Resistance from the SEC due to data quality concerns. @Seref Arikan will write those out including concrete risks.

• @Sebastian Garde suggestion to make these modifications to DV_SCALE only, but we will need to define the comparable functions

• for more info please read the discourse page https://discourse.openehr.org/t/scores-or-scales-with-mixed-data-types-or-explicit-null-values/4620/39

• null-flavour suggested, but is not accepted by SEC

• other options to consider:

  • add another option/attribute to DV_SCALE

  • or add a new DATA_VALUE class

• SEC values the needs of the clinical group and would like to better understand them. @Joost Holslag and @bostjan.lah @bostjan.lah will promote a joint session.

@Severin Kohler

Constraining and patterns for DV_EHR_URI values

@Severin Kohler shared issues in the openEHR specs while working on FHIR connect mapping. One is the need to be able to constrain the value of DV_EHR_URI. @Joost Holslag supports this need for clinical modelling. Another is to create a terminology at RM level for ‘demographics links’ like PARTY_REF. @Bostjan Lah at better this type of modelling is done by archetyping the other details (which attribute is this exactly @Bostjan Lah?). After releaseing the 1.0 of the FHIR connect Severin would like it to be maintained by the SEC. @Joost Holslag feels it should be part of the openEHR spec. (Or ideally an artefact jointly maintain with HL7)