...
Goals
previous meeting:
Discussion topics
Item | Presenter/Suggested by | Issue | Notes | |
---|---|---|---|---|
Meta | ||||
5 min | Opening | USEFUL Jira RESOURCE: CRs I have not accepted. | ||
5 min | New website - see SEC and other areas. | |||
Main Agenda | ||||
15 min | AQL | picking Picking up data from specialised archetypes. See latter part of Discourse discussion. Seref Arikan (Personal) - detailed analysis of AQL query results across system boundaries - pick up again next call. |
| |
10 min(?) | Computable references | How to improve the referencing mechanism(s) of openEHR. | Index compositions (of sorts) are used in practice and is likely to be required even more. Ideally we should identify the requirements for these, come up with a roadmap for specifying them and discuss in details. Example: how to avoid dangling references (both at creation and at updates)? What would it mean for implementations. Benefits/Costs. Optional Can-of-worms aspect: can we use this to improve RM based mock-demographic implementations out there? by adding more semantics to references? In the same way graphs having well typed edges/relations. MAIN Q: are openEHR implems checking link targets existing (recursively!) before commit? Commit should fail if any links not resolvable. Question: granularity of link targets? What about targets of more specialised RM types? Pieter Bos : similar logic to DB cascade delete Diego Bosca : FHIR FHIR references page: “References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (given that access control works, there is no temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL (see below) and looking it up in a local registry/repository” Q: access control may block ref being resolved, even if it is there. Archetype ref constraint: possibly should be able to point to target of type ‘Patient’ in a on-openEHR server. | |
15 min | REST ApiSebastian Iancu |
| Update:
| |
15 min | New Registry model - and back-port to demographics | Define new model? Back-port features to demographics | ||
Tips and Tricks | ||||
Hackers' Corner | ||||
Next SEC call | ||||
Outstanding topics: Agenda items: |
...
ALL - nominate in-house experts from your org for addition to SEC Expert Panel
ASK all vendors whether AQL do subsumption based retrieval or not