2020-12-14 SEC Meeting notes

Date

Dec 14, 2020

Participants

  • @Bjørn Næss

  • @Diego Bosca

  • @Erik Sundvall

  • @Ian McNicoll

  • @Matija Polajnar

  • @Pieter Bos

  • @Rong Chen

  • @Sebastian Iancu

  • @Seref Arikan

  • @Shinji Kobayashi

Goals

Discussion topics

 

Item

Presenter

Goals

Notes

 

Item

Presenter

Goals

Notes

5min

Opening

 

 

 

 

ADL2 / AOM2

@Pieter Bos

not discussed, but we need to review it!

 

AQL

@Sebastian Iancu

  • discussed issues ‘in progress’ and ‘in review’

  • affirmed that we are all ok to go with AQL closer to SQL style languages

  • presented the AQL conformance table form

  • thoughts about JOIN queries (will consider discussing about this in 2.0)

  • discussed briefly about the use of RM Demographics vs FHIR Person Resources; the complex issue of graphs because of party-relationships (SA)

  • aim to release 1.1 after next meeting in January

 

REST

@Sebastian Iancu

REST Release 1.1.0

will start focusing on this as soon as AQL 1.1 is getting ready to be released, hopefully in Jan 2020

 

BASE

@Thomas Beale

not discussed

 

TDD

@Bjørn Næss

  • feels a bit an outdated technique, but still in use (MP)

  • last (beta?) version was in 2015

  • DB: we don't use it

  • SG: not used that much

If time permits

15min

 

 

 

 

Outstanding issues

 

DV_EHR_URI analysis https://openehr.atlassian.net/wiki/spaces/spec/pages/786956289/DV+EHR+URI-related+Issues

 

Serial data formats: https://specifications-test.openehr.org/releases/SM/latest/serial_data_formats.html

 

Integration package link to presentation

 

REST Release 1.1.0

 

View Entries, Problem Lists etc. Initial UML here.

 

Tags (RM 1.2.0)

 

ITS status: XML, JSON, BMM

 

Website: adding examples, type definitions/navigator

 

CDS-hooks

Action items

Decisions:

  • the SEC members are considering aligning AQL closer to SQL style languages

  • considering next AQL version to be 2.0, so that we can introduce potential breaking changes

  • investigate if we could use ‘latest’ term as an alias for latest-published specs, and use another one to indicate beta, next or upcoming for unreleased specs - this will affect all specification URLs

  • next meeting is in Jan 11, 2021