2024-10-14 SEC Call notes

10 min

Opening,

Various aspects

ALL

SEC Jira board.

• Conference UK Nov 2024 Connectathon

• Risk register

• “Adopt your ticket”

•  

• @Mattijs Kuhlmann need progress on SPECRM-121: Add time_asserted property to EVALUATION (or potentially on ENTRY)Open

• @Mattijs Kuhlmann invites Jelte Zeilstra to participate as guest to SEC meeting in UK

• OpenEHR SEC risk register

• https://highmed.universal-berlin.com (31 Jan 2025)

Flat-format

• @Severin Kohler takes on mediating on publishing Flat-format specification, and replacing older specs around this object.

  • The specs should be align with what Better and EHRBase supports

  • First document what exists, improvements may come later

  • according to @Bostjan Lah flat-format implies also discussing about web-template format

  • @Erik Sundvall language localization - how to convert non-ascii chars

  • @Bostjan Lah formats are published on github (open-source)

10 min

UK SEC Meeting Nov 2024

@Sebastian Iancu

Set up Agenda for UK SEC Meeting Nov 2024

• Proposal:

  • ADL v2.4 progress & recap

  • export/import format @Seref Arikan

  • RM 1.2 @Sebastian Iancu

  • @Severin Kohler updates on Demographics WGOMOCL FHIRconnectEU Network

  • @Sebastian Iancu progress on conformance (for @Ian McNicoll)

    • @Pablo Pazos This is the spec and test case implementation in Java for the conformance verification GitHub - ppazos/openehr-conformance-verification: Conformance verification framework or openEHR implementations

  • AQL Federation progress?

  • perhaps

    • Episode @Birger Haarbrandt

    • Action connecting with Instruction @Erik Sundvall

    • AQL WG @Sebastian Iancu

15 min

Clinical PR

@Ian McNicoll

SPECPR-440: Add 'Role/ note' and 'other_details' to PARTY_IDENTIFIEDOpen

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

SPECPR-442: For DV_SCALE /DV_ORDINAL, make value attribute optional not mandatoryOpen

• 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

OPT 1.4

@Sebastian Iancu

(XSD) Schema not uptodate

• not discussed