2021-09-06 SEC Call notes

Date

Sep 6, 2021

Discourse SEC calls

Participants

  • @Thomas Beale

  • @Seref Arikan

  • @Sebastian Garde

  • @Jake Smolka

  • @Diego Bosca

  • @Sebastian Iancu

  • @Pieter Bos

  • @Rong Chen

  • @Erik Sundvall (@gmail profile)

  • @Pablo Pazos

Goals

  • previous meeting:

Discussion topics

AM Release 2.3.0

 

Item

Presenter

Notes

 

Item

Presenter

Notes

5 min

Opening

 

USEFUL Jira RESOURCE: CRs I have not accepted.

15 min

Archie update.

@Pieter Bos

  • OPT14 → ADL2 template in advanced state; more testing required; generates ADL2 source form template and ADL2 operational template.

  • Default values working as well - question on correct OPT14 form of representation of defaults. EhrBase ‘CompositionTemplate.xsd’ different from 'Template.xsd'

  • XSD at https://github.com/openEHR/specifications-ITS-XML/blob/master/components/AM/Release-1.4/Template.xsd is in the official ITS-XML repository, and appears to be what is most used.

  • We should publish an official OPT14 spec; based on current ITS XSDs created by @Sebastian Iancu

20 min

@Ian McNicoll AQL question

Example:
SELECT el/name/defining_code as someElement
FROM EHR e CONTAINS COMPOSITION c CONTAINS OBSERVATION o CONTAINS ELEMENT el WHERE el/name/value/mapping has 'someSNOMEDcode'

 

Possibly handled by current implems?

@Seref Arikan : question of literal matching v inferencing e.g. subsumption; need a solid real world use case & scope.

Invitation to @Ian McNicoll : please provide more details

Possible consensus: AQL TERMINOLOGY() function can do this? Q of codes in template / archetype v just data.

@Erik Sundvall (@gmail profile) : NB mappings can be in data or not (just in the template).

Confluence Ref. ; https://openehr.atlassian.net/wiki/spaces/spec/pages/68747282
https://openehr.atlassian.net/wiki/spaces/spec/pages/378830853
https://openehr.atlassian.net/wiki/spaces/spec/pages/94210552

20 min

Informational - TS generation from Archie

Making progress on schema generation.

@Seref Arikan

@Seref Arikan End result would ability to build RM objects in a JS/TS environment.

OpenAPI schema JSON schema code generation tool ; tested with TypeScript target. Result is TS pure code objects representing only data view of RM. Current challenge - no tool / code to create RM instances in browser app environment.

Main issue to date: Upper Snake case type names versus ?camelCase converted forms; TS has case sensitive ids. @Pieter Bos Swift generator also needed to be fixed; std generator works well for Java.

5 mins

Conformance update

@Thomas Beale

@Pablo Pazos : Need to harmonise service model with REST API (reverse from REST API);

@Thomas Beale , @Matija Polajnar : concretely conformance has to be against ITS not abstract specs.

Next SEC call

 

Agenda items for next call:

  • @Seref Arikan Archie-based TS generation based on JSON schema.

  • @Ian McNicoll AQL ELEMENT/term matching question - precise use case please

 

Outstanding topics:

Action items

ALL IMPLEMENTERS: please check your OPT14s against ITS XSDs on spec site. E.g. at least report diffs please. NB namepace v1/v2 question & importing (all versions have to be the same in XSD).
@Thomas Beale : create conformance discussion online
@Diego Bosca at some future point, propose some initial OMOP-related mapping resource