2022-01-10 SEC Call notes

5 min

Opening

USEFUL Jira RESOURCE: CRs I have not accepted.

• next meeting in January 10th

• we keep by-weekly meetings over 2022

15 min

Conformance progress report

@Thomas Beale

See Discourse.

• Various PRs relating to conformance - See Pablo’s list on Discourse

• see https://specifications.openehr.org/releases/CNF/latest

• todo: consider to use Registry Instead of Demographics in CNF, SM and ITS (ITS-REST)

15 min

standards for Forms

@Erik Sundvall

@Diego Bosca : https://lhcforms.nlm.nih.gov/lhcforms

@Erik Sundvall :

• Current need in multi-openEHR-vendor projects (in Sweden) where we would like at least some GUI/form logic to be authored once and then reused in several different vendor solutions (Cambio, Tieto/Better, SECTRA structured forms, perhaps NeoEHR?)

• Previous mail list discussions (2008) regarding GUI-hints in openEHR templates. Some highlights:

  • Initial:

  • https://www.mail-archive.com/openehr-technical@lists.openehr.org/msg03881.html

  • Summary:

• Suggestion

  • Start some experiments with template annotations reusing most of the design patterns of “EnableWhen” in FHIR Questionnaires that could optionally be used by form building tools as input for creating (possibly vendor specific) conditional logic in forms (like now available in e.g. Better’s and Cambio’s tools)

  • Maybe later look at

    • “Presentation mode visibility” annotations - see option in Better’s EHR studio

    • “Hide on form” - e.g. useful for marking medium level branch levels that are needed for logic storage structure but not contributing to understanding at a GUI-level in the template-specific use case.

    • LOD - level of detail annotations - subtrees/parts that can be initially collapsed/hidden when screen space (or attention span) is limited. (Like the “More…”-buttons in Clinergy/PEN&PAD)

    • SelectWhen - Select a multiple choice when a condition is met

    • Copy data between fields (and possibly discuss the Pandora’s box of “simple” calculations)

Discussions (all):

• considers rules from ADL - (Definitely useful within an archetype - with ADL2 possibly also in templates across data from different archetypes?)

• Nedap is using these rules, need to ask @Pieter Bos for feedback.

• Edit: In Slack Pieter later wrote:

  • Regarding the rules: the implementation is open source in Archie. It outputs things such as 'set the value at this path to this', and 'this part of the data must exist (is mandatory)'.If anyone would like to try, there's an imementation running at archetype-editor.nedap.healthcare. sign up and login, create a repository. Using the basic editor you can only define sums and averages. If you click 'advanced editor' at the bottom, you can see and edit the rules to achieve quite a lot more, and there's a form implementation that executes them as well. Note that this form only does compositions, observations and evaluations. (edited) 

    Oh it also outputs a copy of the object provided as input, modified by the rule evaluation, plus whatever assertions failed and succeeded, of course

    For editing the rules by hand, I would recommend the visual studio code extension, but it cannot execute them on data

• need to ask @Matija Polajnar about Better’s form-builder

•  

Next SEC call

Agenda items for next call, Jan 24:

• elections etc

• @Matija Polajnar endpoint for committing persistent composition

• Borut Jures (neoEHR) will join the meeting. The initial thought some weeks ago was to discuss how the generated UML diagram approach works and how it could be used in the specification web site (and spec. documents). Now he has already done a lot more regarding Code generation etc, so the discussion could broaden to more topics depending on participants' interests.

Outstanding topics: