Colleagues in e-health often say to me: why don’t you make openEHR easier to map to <insert popular interop standard> (used to be HL7v3, then HL7 CDA, now, HL7 FHIR… DSTU2/3/4/5?). To which I usually reply: if you are implying …
Despite using the same underlying tool, not all CKMs are equal. Rather than ‘one CKM to rule them all’, each CKM exists for a specific reason – for example intent, geographical domain, servicing a common community. This allows countries, organisations or programs to operate autonomously from each other when they need to. All CKMs operate independently of each other, with their own Editors and Administrators.
Now for a blog version of my celebrating the achievements of the international openEHR Clinical Modelling Program, its' Editors, & its' community of volunteer reviewers. I'm so proud of these people, these models. Together we've achieved something truly unique & groundbreaking ????????????????????
The openEHR Clinical Modelling Program commenced life as the Archetype Editorial Group and ‘operated’ between 2007 and 2012-ish. The in 2007 described it as the lead group for archetype authoring. Comprising a group of doctors influential in health IT and friendly to the openEHR approach selected by Sam Heard (Ocean, AU) in the first instance, the announcement also states the intent to develop a nursing group would be convened soon after.
As I leave my leadership role in the Clinical Modelling Program, let me start by sharing with you some facts and insights…
As of 2 November 2021, from :
This is part 2 of a series of posts discussing the particulars and as the title says, confusing bits of AQL. Part 1 is here. I’m hoping to discuss what choices implementers of clinical data query language designers have and the implications of such choices. AND operator takes the stage So let’s talk a bit […]
AQL is one of the most clever things openEHR offers: a query language that allows users to access data they’re interested in, using the elements of openEHR reference model. Its primary author is Chunlan Ma, a real veteran of health IT, who has been a cornerstone of Ocean Informatics (Ocean Health Systems) for many years […]
Following on from various posts in the past, including my 2014 post What is an open platform?, I thought it might be time to post a succinct (as possible) definition of the platform idea, for e-health. As stated in that …
There are some rather obscure definitions of health IT’s favourite term interoperability floating around, for example: Wikipedia: Interoperability is a characteristic of a product or system, whose interfaces are completely understood, to work with other products or systems, at present …