Report of openEHR events in Kyoto, January 2016

Community documentation

h1. The openEHR clinical modeling tutorial and unconference in Japan

We had launched NPO(Non-Profit organisation) Japan openEHR association in December, 2016. In order to remark openEHR activity in Japan, we settled memorial events, clinical modeling tutorial and unconference from the 20th to 23th January 206 in Kyoto, Japan.

h2. Clinical modeling tutorial by openEHR

Clinical modeling is one of the most important deficit of medical informatics in Japan. We have held clinical modeling tutorials by openEHR in these years, but they were just the introduction of openEHR archetype models in a half or one day course.
This is our first time to have two-days tutorial course with the supports of Drs Hugh and Heather Leslie. The regimen of the tutorials were shown bellow.

  • What the openEHR is.
  • What the archetype is.
  • Designing clinical model for tobacco smoking by mindmap
  • Hands on/off template designer, archetype editor ** Building a template for admission note by a given scenario

The gathered 10 audiences were consisted with engineers, a cardiologist and students. For the most of them, this tutorial seminar was the first exposure to openEHR, but they understood archetype and template mechanism.
The discussion continued very actively to the consequential unconference.

h2. The openEHR unconference in Kyoto

Unconference is a participant driven meeting that try to avoid top-down origanisation to catch wide-range gathering. At first, I had taken much efforts to make a memorial meeting for the launch of NPO openEHR association, but I decided to make it unorginised in conclusion. I thought we would need to talk about what we need by ourselves, not by only me. Because openEHR is opened society, we have to work on voluntary basis, and only accepting the fixed schema is not our way. Especially, the launching participants should not wait someone filling food into their stomach with only opening their mouths, but make foods and share dishes with ourselves. Eventually I settled the unconference in Kyoto at the 22nd January 2016 for the first meeting of NPO openEHR association.

26 participants gathered to this unconference, most of them were engineers and researchers, and involved three openEHR colleagues from Austraria and China.
At first, I talked about the unconference style and why I unorginised this meeting. And then, we talked about what we should talk for the mission of openEHR (in Japan).

A symbolic conversation was shown bellow

Q: What is the missing of openEHR? That is the most important. I would like to know that.
A: Your contribution is.

After 30 minutes discussion, we determined the sessions in the afternoon. The topics were these.

  • What the openEHR is
  • openEHR Localisation, Japan and Asia.
  • Case study.

Participants were separated to these three topic groups, and they talked about the contents of the sessions.

In the afternoon, the sessions started with active discussion.

h3. What the openEHR is

Dr Hugh and Heather Leslies gave us presentation again. Their slides were involved the discussion in the morning.

h3. Localisation of openEHR

I talked about this localisation issue with industry persons and Dr Lu from China. The slides were shown "here":
To involve industry, openEHR labeling could be an incentive to pay the membership fee and NPO openEHR Japan will have to obtain and manage openEHR Trademark with support of openEHR foundation.

h3. Case study.

Two cases were presented. The "one case": was reported by Dr Lu from China. It was very interesting case report that they built a clinical data repository by openEHR architecture.
The other one was reported by Dr Kume. He mentioned about ongoing project of nation-wide EHR system by openEHR archetype in Japan.

h3. Reception

After our exciting discussion, we enjoyed shabu-shabu and continued discussion. We all were delighted that the successful tutorial and unconference and started making ourselves to the next missions. The photos are uploaded onto facebook pages "[1}": , "[2]": .