| | | | |
|---|
|
10 min | Opening | ALL | SEC Jira board. | |
15 min | Various aspects | @Sebastian Iancu | | @Sebastian Iancu will make Jira tickets to execute decision about retirement of some specs as per Berlin’s meeting it will be nice to report on discourse on Berlin’s meeting. SEC accepts Borut Jures as SEC Expert, @Sebastian Iancu should make formaties with Jill propose SEC meeting 4th Nov (conference pre-day), perhaps in London @Sebastian Iancu needs to contact Jill.
and maybe it would be good to invite a few people from the CPB, like Silje, on the first topics. @Joost Holslag |
| Demo/Hackathon/Connectathon for Conference in November | @Sebastian Iancu | The summary of the discussion is below and we would really like your take on this IPS is a major driver - this is something we need a position on and the conference could be used to kick this off - it will also help with the EHDS We felt there was a real SMART on openEHR angle too As a result we felt this was both a connectathon and a hack with 2 streams We felt Better/Cambio/Vita (and others please let us know who) should be approached to provide CDR capability An idea might be showing IPS working across the CDRs and then a challenge to build a SMART on FHIR app over this One of our likely speakers is a patient who has worked on the SMART on FHIR IPS patient app so this would fit in well On the second day of the conference near the end we can have a main stage slot to review the progress
| it will take a lot of SEC members time during conference to fully attend and support a live hackathon, it is a good idea but requires resources, preparations, infrastructure, scenarios - SEC should not be the one responsible SEC would rather support DEMOs instead of a hackathon Suggests also:
|
15 min | ADL Formalism | @Joost Holslag | Could we discuss adl formalisms? Discussionion on discourse has been a bit all over the place. So I hope to focus a bit on the key stakeholders (modellers, CKM, AD and CDRs). | we support to explore a single design time formalism for archetypes and templates YAML representation for design time, including exploring simplifications (special microformats), which should be able to replace ADL when we manage to have such format, we (SEC) would be able to retire cADL, ADL, ODIN, etc. specifications
|
| FHIR collaboration | @Joost Holslag | Other topics of potential interest are FHIR collaboration, my 10 point list on LinkedIn (incl mappings in CKM). | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
The SEC as present today didn’t remember which parts of archetypes are defined by which syntax. I found this one in the adl(2.4)spec:
“ The cADL syntax is used to express the archetype
definitionsection, while the ODIN syntax is used to express data which appears in thelanguage,description, andterminologysections of an ADL archetype. The top-level structure of an ADL archetype is shown in the figure below.”so cADL is definition, odin is the rest.
So @Thomas Beale does support YAML for ‘language’, ‘description’ and ‘terminology’ sections, which allows deprecating ODIN (for ADL). But deprecating/changing the definition section is a separate discussion. Let’s continue to have that discussion on discourse. This reply was just to summarize and inform the minute readers.
And I’d like to reiterate, the SEC as present today not understanding odin vs cADL is a major indication we should move to something standard. Also this argument we could discuss on discourse. I just want it to be recorded since it’s not in the minutes.