Place and Date
Chausseestraße 86 | 10115 Berlin (Mitte)
Room: “Work” (https://meeet.de/raum/berlin-mitte/work-arbeitsraum/)
Participants
SEC Physical | SEC Remote | Guests | Won’t attend |
---|---|---|---|
Goals
Agree Conformance roadmap
Roadmap to ADL2 - concrete progress?
Possible Agenda items
Major directions
conformance roadmap
service architecture roadmap
see e.g. CatSalut plan
questions:
terminology service
demographic service approaches
ID/access management; RBAC / ABAC etc
consent
secure EHRs and EHR id / subject id xref service
subject proxy service
ECA triggers - Erik Sundvall - have a think about standardised approach to triggers on commit; for notifications, CDS calls etc; in an ECA model: what can be in the Condition? E.g. archetype/template ids, has path = xyz etc; AQL result = xxx;
‘Ideal’ clinical data platform concept
ADL2 roadmap
tools, resources, open source
Detailed ongoing work
?view Entries & managed lists
Agenda
Time | Item | Todo | Notes |
---|---|---|---|
09:00 - 09:30 | Agenda setting | ||
09:45 - 10:45 | JSON WT Flat format |
| Erik Sundvall : should we name it webtemplate instead of ehrscape in the spec? Birger Haarbrandt : ethercis format is not used Flat and WebTemplate implementation in openEHR SDK: https://github.com/ehrbase/openEHR_SDK Matija Polajnar : Better published on github web-template implementation and unit tests Group: initial rewrite of SDF spec:
Ian McNicoll potential need to escape out of flat format - use raw canonical within JSON flat. NEED EXAMPLE Check with Solit-clouds on their implementation of this. Include links to Better OS code, EhrBase openEHR SDK(?) and also Archie (near future) flat format generation. |
| see list on https://www.hl7.org/fhir/terminologies-systems.html Document in WTF spec? ADL2 - currently only URIs in bindings? | ||
11:00 - 11:15 ~~~~ caffeine ~~~~ | |||
11:15 - 11:30 |
| Status: Code24 version not completely validating; Archie has a JSON-schema machine generated from RM BMM files. Archie version addresses the polymorphic question. Sebastian Iancu - schema naming - need to follow this URL structure - https://specifications.openehr.org/releases/ITS-JSON/latest/components/RM/Release-1.1.0/Data_types | |
11:30 - 12:45 | REST |
| Sebastian Iancu - EHR_ACCESS & ACCESS_CONTROL_SETTINGS. Implement ‘/ehr_access' dedicated REST end-point; in REST return empty JSON '{}’ ?or locally available ACL object. May need controlled visibility. Do we support definitions API upload of archetypes? Probably useful eventually but not a priority now. Support terminology value sets in REST API? → for now, now; stick to direct use of FHIR terminology services. Ian McNicoll - should discontinue openEHR demographics model. Sebastian Iancu - want to improve implementation and extend to REST API Seref Arikan - used in Ocean (might be phased out) Thomas Beale - if further development, consider Accountability changes. Matija Polajnar - not intending to support demographics. Conformance: can include demographics but as optional component. Erik Sundvall - problem of patient data creep into EHR Thomas Beale - professional demographics requirements getting more complex and getting toward demographic model structure? Discourse discussion. Seref Arikan allow different categories of spec - some more industry-led; treat demographics like this. Erik Sundvall - need to have innovative specs to push the boundary Idea to investigate: mark specs as being in certain product categories; could then filter in specifications main page according to product profile keywords. Ian McNicoll and Bjørn Næss - make REST APIs for e.g. demographics and Task Planning etc a separate spec. Need to focus time better, also not create dependencies between e.g. EHR and demographics or TP. Erik Sundvall - suggest making separate initially, then integrate. |
~~~~ L U N C H ~~~~ (We got some mixed bagels provided by the venue) | |||
13:30 - 14:00 | REST contd | Admin REST calls, incuding Delete
Definitions
EHR export / import functions - GDPR requirement for export (i.e. patient requests own EHRs). - EHR export needs OPTs to be exported out. Bjørn Næss national archive example. Potential need to be able to annotate post-export data. Will need AQL to do any kind of filtering. What is dump format - JSON; treat zip etc as second phase. System log: Discussion needed on semantics of what might need to be stored in e.g. ATNA log. REST endpoint(s) for audit log access needed, but not in this version; possibly treat as own API. Check with Rong Chen re: CDS hooks in REST API. | |
14:30 - 15:00 | Moving openEHR to ADL2 |
| Work items
Backward compatible code rules ADL1.4-related problems and errors Seref Arikan (and others) - what is the is the list of benefits for CDR systems to move to ADL2. |
13:45 - 14:30 | Conformance roadmap TB, PP, BH |
| |
14:30 - 15:30 | Ian’s list - terminology, querying, … |
| |
~~~~ caffeine ~~~~ | |||
15:30 - 16:00 | next RM release CRs | : https://specifications.openehr.org/releases/RM/crs TERM: Sebastian Iancu just checking if agree on SPECPR-367 | |
16:00 - | next steps AQL |
| |
~~~~ bier ~~~~ |
Useful information
-We booked a streaming setup for a hybrid event. Should hopefully allow us to have a high quality remote event
-There is beverages and snacks included
Action items
- Thomas Beale WebTemplate format: issue v1.0 of spec with wt.flat only documented. First draft mid Dec 2021?
- TERMINOLOGY: Establish namespace x URI xref mapping to map ‘snomed-ct’ + variations to http://snomed.info etc. Use FHIR list.
- Pieter Bos - modify Archie JSON schema file naming - change version to 2.0 + status = TRIAL; Pieter will generate out per-class files for web, also combined file for development. Sebastian Iancu check on web rendering etc.
- Develop a list of benefits for CDR systems to move to ADL2, versus costs & risks.