| | | | |
---|
|
Nov 15, 2023 Genieten in de Weerd, Arnhem
| 9:00 | | door opens - installing - coffee | |
9:30 | @Sebastian Iancu | Welcome / Agenda | Pieter Bos resigning from SEC, follow up from Nedap is Matijs - no objection from SEC members to accept him as new member. |
9:45 - 10:30 | @Sebastian Iancu | Jira Board | |
10:30 - 11:30 | @Sebastian Iancu | RM 1.2.0 work, tickets, etc | TAGS path refers to AQL path (need to remove mentioning RM paths); positional predicate is not considered to be safe for json serialization/deserialization add invariant that if you use path, the versioned_object should be used improving text because is not clear what is the use case: searching, but also labelling nodes or compositions (@Erik Sundvall) name/coding might be need to transport semantic, key might be not very clear → but suggestion is to use folders for more complex use case where you want to code the tags “looks like annotations” atomic way adding tags to composition in a contribution offtopic: contribution is transaction unit target_path in REST API uri is nasty; it might need to have an id to uniquely identify in the management operations @Pieter Bos we should check also FHIR tags, to see how is dealing with coding see EhrScape yaml
SYSTEM EPISODE Ocean uses workflow_id to “group” compositions as part of an Episode the consensus is that is too early to have such a type, rather use FOLDERs based on a specific (recommended) archetype, and add an implementation guide about use of this archetype+folder, potentially describe use of tags to implement episode context …thus no new type use of episode in a contribution is complex and we will need to define the logic of atomic contribution [Addition by @Erik Sundvall: CONTRIBUTIONs have been implemented as a transactions by all vendors present at this SEC meeting, so that is not the complex thing, but might (according to @Seref Arikan's previous discussions with @Thomas Beale) need to be clarified in the spec anyway. A remaining complexity is how you link/cross-reference between several different new objects in the same CONTRIBUTION API call before the server has given them their permanent IDs. One way of doing that is that the application calling the API assigns temporary strings as IDs for the new objects and uses the same strings in references from other objects sent in the same CONTRIBUTION]
WG episode with clinical modeling to further identify the IG
constraining links (@Joost Holslag ) constrain mappings (@Ian McNicoll) on templates AQL should investigate adding demographic flavored functions like age(), gender(), etc -
|
|
11:45 - 12:30 | @Sebastian Iancu | AQL work, tickets, etc | TAGS FOLDERS SYSTEM EPISODE federative AQL
|
| | | |
|
13:00 - 15:00 | @Bostjan Lah @Pieter Bos | ADL 2/3 | |
|
| 15:20 -17:00 | @Bostjan Lah @Pieter Bos | ADL 2/3 | there is consensus that we are committed to ADL3 need to store full-lineage of archetype specialization, name-spacing in ADL3 archetype/templates dashes does not carry any meaning (same like in v2) - change in BASE model component!? don’t need to do anything particular change after migration to ALD3 if you have archetype_node_id on v1 style, the dashed name we’ll not have any meaning for CDRs implementing ADL v3, store the full semver archetype id in archetype_details, and AQL should do a full pattern based matching - needs further analysis, goes hand in hand with at-codes pattern matching we will need to add a new property to archetype_details to carry on the v2/3 template_id and one new property for the concept (that being the old style of template_id), while the template_id will carry on either the old name or a new name - RM change New behaviour for archetype root nodes LOCATABLE.archetype_node_id will contain: at000x.y LOCATABLE.archetype_details.archetype_id will contain full archetype id with namespace and full semver version Consequence: new synactic sugar needs to be for AQL paths so that you still can use paths like SELECT
a/items[at0001]/value as analyteResult
FROM EHR e
CONTAINS COMPOSITION c
CONTAINS OBSERVATION o[openEHR-EHR-OBSERVATION.laboratory_test_result.v1]
CONTAINS CLUSTER a[openEHR-EHR-CLUSTER.laboratory_test_analyte.v1]
WHERE ...
|
| | | | |
| |
| 18:30 - | Dinner |
|
Nov 16, 2023 Nedap, Groenlo | 07:45 | Gather for the bus, riding 50 minutes to Groenlo |
| todo: @Sebastian Iancu some thoughts to be sorted out / suggestions for agenda: |
09:00 - 12:00 | | ADL2/3 | |
|
|
14:00 - 15:00 | @Sidharth Ramesh | REST, SMART | brief reporting on status |
| | | -profiling for multi-EHR federation Extracts @Erik Sundvall AQL profiling, federated AQL ATNA logging for openEHR (@Seref Arikan ) @Bostjan Lah we already have a XDS metadata cluster archetype, saved in context of composition IHE-UK profiles can might do well work with us is PIX PDQ (@Pablo Pazos ) ISO24305 is creating FHIR profiles for ISO13606 RM classes, can be used as a basis for openEHR profiles
|
| | | |
| | | |
15:00 - 16:00 | | | |
| | | |
16:15 - 17:15 | Bus back to Arnhem |
18:30 - | Speakers Dinner |
| | | | |
| | | | |