2022-05-16 SEC Call notes

5 min

Opening

USEFUL Jira RESOURCE: CRs I have not accepted.

10 min

SEC governance update.

@Thomas Beale @Sebastian Iancu

SEC ToR 2.0.0 is now CIC Board approved

Co-chair election may now take place.

10 min

openEHR.nl - conf openEHR Friday 3rd Jun 2022

SEC meeting 1/2 June - Houten (Utrecht)

@Sebastian Iancu

https://doodle.com/meeting/participate/id/oeEoj0Kb

Attendance - PB, JH, SI, TB?, SG?, DB, ?Birger?

check Rong, Ian?

30 min

Care plans in the real world.

@Joost Holslag

Discourse discussion

@Joost Holslag - Nedap mostly happy with current design based on RM

@Sebastian Iancu - some unmet needs for new versions

@Seref Arikan (Personal) - Ocean has substantial CP product; more ‘hacky’ solutions hard to compete with; access control based - who should have access changes over period of care plan;

@Bjørn Næss - how to handle multi-user access; transactional interface

@Thomas Beale , @Bjørn Næss - API approach worth considering - maps transactional functions to data structures

@Seref Arikan (Personal) - transactional approach challenging x-enterprise etc; RM = ‘leaky abstraction’ in some contexts; bidirectional mappings in and out of FHIR

@Bjørn Næss - 8 Sep Stockholm - Nordic openEHR collaboration - at KI UH.

5 min

ADL 2.3.0 progress

@Pieter Bos @Thomas Beale

Basic EL created; AOM 2.3 updated to integrate.

Working on value set containment.

15 min

openEHR <=> FHIR converter

@Diego Bosca

main mapping direction: openEHR → FHIR (other direction not very coherent)

@Matija Polajnar : Better has their own openEHR<->FHIR mapping capability, one being discarded and one new in development; the idea is to have 2-phase mapping (archetypes<->resources and templates<->profiles/bundles), and to share the first mappings in CKM or alike. Example of first kind of mapping (subject to change!)

Open

5 min

Better feedback from vendors on adoption obstacles

@Seref Arikan (Personal)

See Discourse discussion

Most programming revolves around serialisations of data - methods in openEHR RM not? usually used. App developers don’t go beyond the REST API view of the model.

Devs could look at the RM spec and wonder about methods etc, when these are not needed in the REST API view.

Also to consider: features in new languages (Go, …). Algebraic data types…

Syntaxes that are not industry-standard are problems - e.g. archetypes, expression language, etc.

openEHR Antlr4 grammars now in github/openEHR

@Thomas Beale

A new set of modal grammars for parsing:

• ODIN, ADL2, BMM, BEL, EL, DL, AQL, paths, patterns

Could be merged into Archie

Outstanding topics:

• openEHR / FHIR - what could we standardise on? Mappings etc?

Agenda items:

• openEHR / FHIR mapper presentation