Intro - scene setting

Meeting goals

Priorities

2 mins from anyone on the floor

facilitator: T Beale

TB opening remarks slides PDF.

Original TB blog post on key criteria.

Priorities mentioned during introductions:

• Entry level openEHR - getting started is too hard
• Deal with licensing FUD
• Support for localisation, affiliate groups

Ian McNicoll
Tomaz Gornik 

Ian McNicoll presentation on new board structure.

Questions raised:

• articles of association / statutes / by-laws - where defined? Gunnar Klein
• registering trademark outside of Europe
• what is UCL's role? Why not independently registered as a company? Does UCL need to be involved?
• Erik Sundvall: need to be able to fork specifications; requires different license.

Actions:

• Gunnar K offered to help with draft & review of statutes etc
• Text of membership page needs to be changed to reflect 15€ membership idea. Ian M / Adriana
• General feeling is to change org diagram so that 'second board' is a management committee including program leads

HANDI / NHS

Ian McNicoll presentation on HANDI-HOPD

Demo platform being managed by HANDI, not NHS

Already involving some European companies

Questions:

• How do we make the openEHR engagement more active and visible?

Conformance, APIs

openEHR inVivo

Decisions needed:

• rough definition of conformance specifications to create

Tomaz intro:

• IHE approach - publicly announce compliance profiles; required to go to connectathon and demonstrate interop with 2 or more other products; monitors give certification.

detailed notes here.

Decisions needed:

• conversion of specifications from FrameMaker to alternative format, e.g. AsciiDoc, DITA...
• agree lightweight change process

TB explained current status quo of releases and tooling.

Actions:

• review specifications governance - TB, Erik Sundvall, Gunnar Klein
• agreed Asciidoc as candidate new doc toolchain - Bostjan, Fabio, TB
• provide a tooling and specifications roadmap overview (S From, DIPS)

Questions:

• how to move to tool-based UML, integrated with documentation?
• tool-based class definition tables? Obtainable from UML tool?

Decisions needed:

• GDL needs to become a proper specification

Archetype tooling and ADL 1.5

• Archetype editor, Template designer
• EhrExplorer

Archetype tooling and ADL 1.5

• Archetype editor, Template designer
• EhrExplorer

T Beale
Borut Fabjan
Rong
... 

Decisions needed:

• what version to rename ADL 1.5 to, since it is now no longer directly compatible with ADL 1.4
• what approach to migrating from ADL 1.4 to ADL 1.x .... 2.*

Actions:

• agreed to rename current ADL 1.5 spec to 2.x
• agreed in principle on a community tooling project in Java / js / web UI

Clinical modelling

• development sprint
• editorial team
• model of sharing, versioning

fac: Ian

Heather

Tomaz

Decisions needed:

• agreement on mode of action on 'industry sprint'

See this wiki page for main description.

Candidate archetype list.

Heather:

• about 30 / 30 / 30% easy / medium / hard
• need to have industry partners involvement to the extent of reviewing to-be-published archetypes for their use (i.e. for implementation).
• publishing - important PR exercise

Agreements

• It was agreed that some new editors will come on board for the sprint.
• It was stated that full terminology bindings would be developed in a following phase; however epSOS terminology coverage will be reviewed during the exercise.
• need to include some example data for each? archetype

Main terminology bindings would better be done by IHTSDO involvement with CIMI. Potential contacts - Daniel Karlsson, Linda Bird.

Possible synchronisation with Norway archetype development; contact Silje

Clinical model sharing issues across CKMs

openEHR CKM status

fac: Ian

Erik/ Ian M: we can potentially use Git-style methods to mechanically implement the fork / pull request lifecycle.

Heather: right now, Change Request mechanism being added to CKM in next release.

Question: how to submit a new archetype from a national program that doesn't exist in CKM yet.

Martin vd Meer: need better documentation on how to do clinical modelling.

Ian: could even use Stackoverflow.

National openEHR updates

• Sweden
• Norway experience, methodology
• Japan
• Spain / 13606
• Australia
• Slovenia
• UK - NHS/FHIR

Erik S

Silje

Shinji

David Moner

Hugh Leslie

Ian

Details on this page.

Decisions needed:

• need to fund dedicated openEHR.org server, allowing multiple sub-domain websites, Jira, etc
• need to agree on sysadmin responsibility

Decisions:

• move to new Linux server at Hetzner
• sysadmin human resource from Ocean, Marand, DIPS, Code24

Web / e-presence

• solicit requirements
• web site ideas
• educational materials
• entry points

fac: TB

Heather

Adriana Danilakova

all

National openEHR updates

• Sweden
• Norway experience, methodology
• Japan
• Spain / 13606
• Australia
• Slovenia
• UK - NHS/FHIR

Erik S

Silje

Shinji

David Moner

Hugh Leslie

Ian

Details on this page.

Decisions needed:

• need to fund dedicated openEHR.org server, allowing multiple sub-domain websites, Jira, etc
• need to agree on sysadmin responsibility

Decisions:

• move to new Linux server at Hetzner
• sysadmin human resource from Ocean, Marand, DIPS, Code24

Web / e-presence

• solicit requirements
• web site ideas
• educational materials
• entry points

fac: TB

Heather

Adriana Danilakova

all

Problems noted:

• newcomers versus 'congregation' balance needs to be better
• need to address: privacy, accessibility, cookies
• mobile version of website
• remove / redirect openehrfoundation website
  
  

Suggestions:

• very visible demo links
• make link to CKM more obvious
• blog syndication, esp in program pages
• outgoing links to stackoverflow openEHR references
• news for each program
• events news should only be future events (past events on another page)
• get subdomains versus /xxx rationalised
• 'why openehr' needs to be addressed on home page; e.g. Seref's blog post
  • basic block approach: 'how to store data', 'how to define content', .....
  • Marand site content
• newcomers: top half of home page
• connect to LinkedIn discussions (how?)
• endorsements by using orgs visible on home page
• consider 'portal's approach i.e. home page for devs, clinicians etc

Decisions:

• connect members.openehr.org to main site
• curate members.openehr.org
• move website and mailing lists to new Hetzner server
• put together a requirements statement
• method of usability testing
• web content committee
• mailing lists on new server + mhonarc for mailing list archive
• ensure news authors have login

FHIR + SMART, IHE - technical, EN ISO 13606

• DIPS & FHIR 10 mins
• Marand update 10 mins
• IHE - Marand
• T Beale - archetype-based approach 10 mins

T Beale
Borut Fabjan
DIPS 

Decisions needed:

• openEHR approach to FHIR
• openEHR and IHE
• openEHR and EN ISO 13606

Borut Fabjan openEHR / IHE / FHIR presentation.

Room agreed that

• we need to create an openEHR technical position on IHE and FHIR
• model-based approach to FHIR makes more sense than manually built resources

fac: Ian M

Shinji

Agreed on call among key implementers to build a description of a tool, and rough project definition:

• Ocean - TB, Seref Arikan, Sebastian
• Marand - Bostjan, Borut, Marko
• Code24 - Sebastian Iancu
• DIPS - TBD (contact Bjorn Naess)