Tag Archives: openEHR
FHIR v openEHR – concreta
Some readers may have read my previous post FHIR compared to openEHR. If not, I recommend you do, it is available in Spanish, Japanese and Chinese as well as English. Here I aim to clarify some of the concrete differences … Continue reading
Why the platform will replace today’s interoperability standards in healthcare
For decades, most of us working in health informatics and e-health have lived on the assumption that ‘interoperability’ is one of the main things we are trying to achieve, and that it is the most important because the lack of … Continue reading
openEHR Basic Meta-Model (BMM) and syntax major upgrade
The openEHR Basic Meta-Model (BMM) that has been in use in some form for nearly 10 years now was recently upgraded to version 3.0.0 (from 2.x), with the persistence format (now called P_BMM) being backwards-compatibly upgraded to version 2.3. The … Continue reading
Major German research project chooses openEHR
I just returned from Heidelberg, where another very successful ‘openEHR day’ was held, this time by the HiGHmed research consortium, with 100 attendees. HiGHmed is funded with 20m€ by the German Federal Ministry of Education and Research (BMBF) under the … Continue reading
openEHR REST API 0.9.0 out for comment
The REST API Team (Bostjan Lah, Erik Sundvall, Sebastian Iancu, Heath Frankel, Pablo Pazos, and others on the openEHR SEC and elsewhere) have made a 0.9.0 Release of the openEHR ITS (Implementation Technology Specifications) component, in order to make a pre-1.0.0 release … Continue reading
The open e-health platform, coming to an economy near you
I’ve been silent for a while, but luckily an excellent paper on one of my favourite topics – the open platform for e-health has appeared. It comes from the Apperta Foundation, and is called “Defining an Open Platform”; you can get … Continue reading
openEHR Task Planning – progress update
In openEHR, we’ve neatly sidestepped the issue of ‘workflow’ by using the term task planning, which I think better corresponds to the scope we think we can manage. If we were to say we were writing a specification for workflow, … Continue reading
wolandscat