Page Comparison

...

• AQL

  • AQL Functions;

  • distributed queries

  • AQL & Demographic

  • AQL FOLDERs and Refs

• Report/status on usage of archetypes - in an vendor independent way be able to get usage of archetypes and perhaps elements. The intention is to provide better governance of openEHR clinical models.

• Task planning (Bjørn Næss )

  • REST / Service API for Task Planning - to make it real vendor independent.

  • Plans for next version and the work to be done during 2019

• Expression Language (Bjørn Næss

  • I.e this script is used as expression logic form HCM_SCD_Risk_Calculator_1.1.13.zip to create the following RISK calculator (http://www.doc2do.com/hcm/webHCM.html), how to use openEHR Expression Language for this kind of use-cases?

    • Björn, here is an example of GDL implementation of QRISK2 algorithm, which has similar complexity level as SCD risk calculator, https://github.com/gdl-lang/common-clinical-models/blob/master/guidelines/QRISK2-2015_risk_calculation.v1.gdl (Rong Chen )

  • CDC/NHSN Surveillance Definitions for Specific Types of Infections - do we have the tools (TaskPlaning/Expression Language) to model this?

• add any burning item here, please include your name / user id as well

  • JSON schema - Sebastian Iancu

  • TEMPLATE ids in data spec - Sebastian Iancu

  • OPTs can contain same archetype id but different content, e.g. different minor versions - how to detect Birger Haarbrandt ; also archetype packaging; signing Bjørn Næss ; approach to archetype packaging

  • querying v version state (INCOMPLETE / COMPLETE / DELETED); also does INCOMPLETE need to be archetype-valid content (mainly mandatory sections might be empty); also relates to GDPR right-to-be-forgotten; meaning of ‘final’;

  • Define flat-form json format and template extract algorithm, add to REST API; See https://github.com/openEHR/specifications-ITS/issues/56 and https://github.com/ethercis/ethercis/blob/master/doc/flat json.md. Bjørn Næss Former user (Deleted)

  • A burning issue for Sebastian GardeHeath Frankel (Unlicensed):

    Jira Legacy
    server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECPR-279

• TAGS:

  • Jira Legacy
    server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7788407e-95fd-3d19-96c6-946a2bd486dc key SPECPR-265

  • Requirements:

    • user tags

    • tags to make queries easier

    • tags to record form ids (Marand)

  • tags purely local? I.e. part of / not part of the data

  • Marand / DIPS /Code24 - stored outside system with references; Code24 ref point just to VERSIONED_OBJECTs

  • do tags point to specific versions? Probably 2 types

  • what do tags look like in AQL? Or as execution parameter to an AQL?

  • standardise the structure for access by AQL, REST API - potentially define classes representing ‘tags table’.

  • key/value representation?

...

...

•  DIPS/Marand: publish ‘flat form template’ - into ITS
•  sign-off ITS REST spec - https://openehr.atlassian.net/browse/SPECITS-11
•  Split ITS repo

Decisions

• (provisional) merge date/time class triples into one class each ; stick with ‘Date’ etc?
• Separate out ODIN, BMM, EL to a new component.
• Separate adl1.4 and adl2 end-point paths in REST API.
• Publish work definition for BMM extractor.
• Publish JSON schema from Code24
• Decision Support / Logic / GDL workshop in 2019 - Stockholm/Cambio?