2025-01-06 SEC Call notes

10 min

Opening,

Various aspects

ALL

SEC Jira board.

• 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

• see previous comments on this in dec 2024

• see @Sebastian Garde comment on https://openehr.atlassian.net/browse/SPECBASE-39

@Joost Holslag

DV_ORDINAL

• see previous comments on this in dec 2024

• @Joost Holslag reach out to clinical, Rachel will organize a strategic meeting after 21 January

• discussion about DV_ORDINAL should we moved to one of a separate (“hands-on”) meeting (SEC meeting) after 21 January

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

@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

https://specifications.openehr.org/releases/AM/latest/ADL2.html#_annotations_section

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

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