Date
Call Link
Participants
Goals
previous meeting:
Discussion topics
Item | Presenter | Notes | |
---|---|---|---|
Meta | |||
5 min | Opening | USEFUL Jira RESOURCE: CRs I have not accepted. | |
10 min | SEC governance update. | Co-chair election underway. | |
SEC representation challenge, meeting time | EhrBase not currently represented; Cambio? DIPS? Requirements:
Possibilities:
Practical needs:
| ||
Main Agenda | |||
AQL querying - picking up data from specialised archetypes. | See latter part of Discourse discussion. | ||
15 min | openEHRv2 | ||
45 min | Better feedback from vendors on adoption obstacles |
Devs could look at the RM spec and wonder about methods etc, when these are not needed in the REST API view. Also to consider: features in new languages (Go, …). Algebraic data types… Syntaxes that are not industry-standard are problems - e.g. archetypes, expression language, etc. Seref Arikan (Personal) - can we find a more developer-oriented set of models? (GraphQL) - reduce inheritance, generics etc. Heath Frankel (Unlicensed) - many devs only care about OpenAPI or similar level of spec Thomas Beale - consider repurposing e.g. SIM-B spec Pieter Bos - NB: not all code generating tools support all of OpenAPI Heath Frankel (Unlicensed) - FHIR doesn’t ‘do’ OpenAPI directly - devs do it themselves Erik Sundvall - template-specific API v canonical-based Seref Arikan (Personal) What if we had OpenAPI repr. of RM, and archetyping on this? What would we lose? Heath Frankel (Unlicensed) What would we gain? Even FHIR too hard for many devs | |
Next SEC call | |||
Outstanding topics:
Agenda items:
|
Notes
Action items
- EVERYONE: consider new SEC expert panels in your org/company - DISCOURSE
- Thomas Beale - create new SEC task management project (Kanban-style) / discourse
- Diego Bosca - run FHIR/openEHR webinar - could be +EhrBase +Better as well
- Thomas Beale WIKI page: Convert our REST API defs in .apib → OpenAPI format + JSON schemas (develop + link into OpenAPI) ; multi-level approach; different types of developer experience; don’t forget tool devs
- Sebastian Iancu look into .apib REST API format upgrade to OpenAPI